Questions Printing a Check with MICR Encoding

Hey Fozzie,

Yep, it sure does.

Checkout this blog post for the details.

Awesome. Thanks for the quick response.

Hi Tim,  Thanks for the Blog post.  It got us close but not all the way.  I have a feeling we missed something in step 5.  The MICR appears nicely in report designer but does not appear when we render the check.  Any thoughts on troubleshooting? 

If it displays within Report Designer, but not when you print the actual check, my first guess would be that the MICR font has been installed on your local machine where you run Report Designer, but not on the IIS Web Server which runs the Acumatica application.

Can you confirm that the MICR font was installed on the IIS Web Server?

We bounced the IIS server and now it works,  thanks for the tip Tim!

Excellent. Glad you got it working.

Some people install the MICR font on every client machine which is a pain to maintain going forward. Getting it working on IIS is more work in the beginning, but it definitely pays off down the road.

HI Tim, Fozzie,

I have a new instance where the Micr font does not seem to be working correctly. (I have several instances where everything is working correctly). Can you share the IIS manager steps you took to add the font package to the Mime Types?

We were eventually able to resolve this by removing the print PDF option in the report designer. However, this has not been an issue in other deployed environments so we are unsure of what the cause of this issue was.

For the IIS steps, check steps 1, 2, and 3 in the blog post above. Those are done on IIS.

But if you are on Acumatica SaaS, they should take care of it for you.

Hi Tim,

Thanks for the response. We are self hosted and manage our own servers so what is outlined in the blog is actually what we had done for all of our deployed instances.

We however have 1 recent instance that is giving us an issue with this methodology. If we set the common behavior:"View PDF" =True  we have a font failure. If we set it to False then we do not. There are several benefits to setting to view in PDF vs. not as you mentioned in your blog post - it makes the print much more stable and reliable in terms of spacing and formatting.

We are working with the common setting: View PDF = False for now, but it is certainly not ideal for all of the aforementioned reasons.

Any insight you might be able to offer is much appreciated.

Interesting "print much more stable and reliable" point. I did not realize that.

So it's the same server and same IIS engine, just a different Acumatica Instance? Are you running each Instance under a separate Application Pool? I personally don't know a ton about IIS (especially the mysterious caching that happens), but I know that multiple Instances can share settings in an Application Pool.

For anyone else who has had issues with getting this to work even after following the IIS instructions above:

We noticed that we didn't have an option to "Unblock" the font (newer version of Windows Server, we assume).

We decided that when we installed the font, we would try right-clicking, and to choose "install for all users."

 After restarting (important step!) it worked without having the font installed on the client machine.