Clarification:  the MICR line prints, just not MICR characters.  The Adobe MICR font we've been using for years is not working.

---

barbarag wrote:

Clarification:  the MICR line prints, just not MICR characters.  The Adobe MICR font we've been using for years is not working.

---

Did you go into Crystal and make sure that the font for the MICR is correct? It sounds like it might have gotten changed to a different font.

That's my goal is to look at the check format,  unfortunately I can't open it yet. 

Getting more interesting.  Crystal 2013 won't open any  rpt files including standard report files!

Correction to above posts,  I'm working with SAP Crystal 2011.

After doing a repair install,  I am getting "could not load keydecoder.dll".

According to Sage, you need to get a .NET compatible, true type MICR font. By the way, this is documented on the KB, #110-9000789.

Looks like they may have given us a new MICR font with this install. 

Discovered the original font I had been using in 4.5 and this new font that I had never seen before.   Swapped it out and away it went.

As far as getting Crystal to run.   I uninstalled and reinstalled making sure UAC was off and doing a run as administrator (even though I was already an administrator).

Now I'm to the point where the system thinks it hasn't printed the checks.   Off to the server I guess.  Hope they release a patch for this one quickly!

Or maybe they didn't give us a new MICR format.   (Was not present on the server when I tried to print the checks from the server so that they would update).

Ended up printing the checks once from my workstation to get the MICR font to display,  then printed again on blank paper from the server so the check register would update.

Also discovered that my a/p checks needed a correction for the MICR font as well  as some work arounds for some formulas that are present in some sort of USTORE dll that did not properly install (even after doing Azalea font install)   Ended up stripping the bogus formulas from the check so I could print.   I'm sure there is a better way to do it, but I didn't have the time.

Sure glad this wasn't a client install!  

So make absolutely sure in your due dilligence testing to test the a/p and p/r checks.

Did you get a MICR font to actually work?  If so, where did you get it?

I reported this issue to Sage before Christmas and i'm still waiting for a fix or eta on a fix.  Now on second client with issue.

I will try what jcnichol suggested since Support hasn't gotten back to me to let me know to try this.