What version of Sage 500, and what task typically will yield these errors?  Have you tried using a different PDF Printer?

Version 7.4

AP voucher and PO receipt of invoice user gets the errors.

User tried using CutePDF and it does not show errors but will not create PDFs.

Hello BelterrAG,

You might try to compare the version of PDF Adobe distiller installed on the user's workstation reporting the issue with another workstation that is not experiencing the problem.

-Tony

We have Sage installed on only 4 windows server 2008 R2 servers. All users use Sage with RDP.

Adobe Distiller v11.0.929

Delete their profile and let the system rebuild it.  50% chance that works.

JohnHanrahan we have tried that and it did not solve anything.

Sorry if this is too elementary of a suggestion, but have you tried printing from another application, like Notepad, to the PDF printer or from another screen/report in Sage 500 to make sure that it's only the AP voucher and PO receipt of invoice that are having the problem?

I have definitely heard of people having PDF printer issues on terminal servers before, but it had to do with the PDF printers not handling terminal server well, not specifically with the applications that are trying to print.

Sorry if this is too elementary of a suggestion, but have you tried printing from another application, like Notepad, to the PDF printer or from another screen/report in Sage 500 to make sure that it's only the AP voucher and PO receipt of invoice that are having the problem?

I have definitely heard of people having PDF printer issues on terminal servers before, but it had to do with the PDF printers not handling terminal server well, not specifically with the applications that are trying to print.

Just tested with notepad and Firefox and both work flawlessly.

It only happens when the user does AP voucher and PO receipts.

Weird. What about sending the reports to the screen and then printing to PDF from within the Crystal Reports viewer. Do you still get the error? This would be a pain of a workaround, but I'm just trying to troubleshoot.