I am working on a Named Printers issue at the moment and thought it would be a good opportunity to put some standard troubleshooting steps on the blog.
Quick history: I originally developed Named Printers back on version 3.0 when I worked for the selling ISV partner, Sequel Technology, and later sold the module to Great Plains Software for version 5.5 and it became part of the core Dynamics.dic code for 6.0.
Named Printers issues normally come down four classifications:
Just before we look at the troubleshooting steps, I want to explain a little of how Named Printers works:
The following Knowledge Base (KB) articles discuss some of these points:
Below are some questions that help define and troubleshoot a Named Printers issue, with an explanation of why each question is important:
That's all I can think of at this stage. I hope this information is helpful.
Posting from Mark Polino at DynamicAccounting.net
Nice info i got answers for many exciting queries. Thanx.
Posting from Mariano Gomez, The Dynamics GP Blogster
Regarding "3. Has the printer driver been updated manually or automatically (Windows Update) recently?", is there a way in Dexterity to detect that the printer driver for a named printer has been updated? I would like to detect this condition and then prompt the user to refresh the settings for that named printer.
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.