ceTe.DynamicPDF.Printing.PrintingException: Error initializing print options. Error code:6

Skip Navigation LinksHome  /  Support  /  Forums  /  DynamicPDF PrintManager for .NET (v4)  /  ceTe.DynamicPDF.Printing.PrintingException: Error initializing print options. Error code:6

DynamicPDF PrintManager for .NET (v4) Forum

We recently moved our Prod servers including our print server to Windows 2019 from Windows 2016.  We are printing to the same exact printers, and the code is an exact copy.  Printing from our app to the print server was working under Windows 2016.  However, under Windows 2019, we are seeing the following error.  We are on version 4.15.  How can we debug, or find out what is causing this Error initializing.  Error code:6 ? 

ceTe.DynamicPDF.Printing.PrintingException: Error initializing print options. Error code:6
   at ceTe.DynamicPDF.Printing.PrintJobPrintOptions..ctor(PrintJob A_0)
   at ceTe.DynamicPDF.Printing.PrintJob.a()
Posted by a ceTe Software moderator
Hi,

The error code 6 reported in the PrintingException is a window error returned by the spooler. PrintManger is passing on the error it received from the spooler (while creating the PrintJob) to your client application. 

It seems like a spooler malfunction is causing the PrintManager to error out as well. The Spooler could malfunction due to various reasons like print driver or OS issues etc. However, it is highly unlikely that the PrintManager is causing the issue.

Thanks,
ceTe Software Support Team
So, it appears to be service account related, specifically, when we use a Microsoft managed service account, then we see the error.   If we revert back to using our original windows service account (Domain account), it works properly.  The solution: we had to add the managed service account to the print servers, in addition to previously having added it to the app servers

We also found that the print drivers were not automatically downloading on the app servers, which spool the print jobs to the print servers, which became evident after the error above was fixed.  I loaded our Ricoh Universal print drivers on all of our app servers.

Once both steps above were done, our print jobs were spooling correctly again, with no more Printing Exceptions. 

All times are US Eastern Standard time. The time now is 5:37 PM.