I know this is a very old post but wanted to provide my two cents.
I'm a developer (NAV and .net) and here is what I found.
Version: NAV 2009 R2 Classic on SQL
The user was attempting to print checks and the client uses a secure Troy printer with signature chip and magnetic printing.
Technology services had loaded an updated driver but the printer was configured to use the old driver (probably software underneath) which caused the issue. Once we pointed the printer to the correct driver by choosing the printer driver from the printer properties (right click on the printer) and under the advanced tab choosing the correct driver (administrative rights required) the issue was resolved.
On a side note the local and remote printer names were unchanged and were still called based on printer selections.
So if you run into this make sure you check your printer configuration first. The drivers, setup and everything you can run through on the printer.
Comments
Microsoft Dynamics NAV Developer since 1997
MSDynamics.de - German Microsoft Dynamics Community - member of [clip]
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I'm a developer (NAV and .net) and here is what I found.
Version: NAV 2009 R2 Classic on SQL
The user was attempting to print checks and the client uses a secure Troy printer with signature chip and magnetic printing.
Technology services had loaded an updated driver but the printer was configured to use the old driver (probably software underneath) which caused the issue. Once we pointed the printer to the correct driver by choosing the printer driver from the printer properties (right click on the printer) and under the advanced tab choosing the correct driver (administrative rights required) the issue was resolved.
On a side note the local and remote printer names were unchanged and were still called based on printer selections.
So if you run into this make sure you check your printer configuration first. The drivers, setup and everything you can run through on the printer.
\:D/