Sage 100

We have a customer for whom PDFs are not getting created for Vendors to email documents (ACH remittance). The email error is related to a PDF not getting created during the check printing process. Most of the PDFs are created for each vendor. However, one random PDF is not being created. The PDF not getting created appears to be a time-out issue for the Sage PDF converter. Sage is installed on a Terminal Server. The Sage PDF printer is installed correctly and working approximately 90% of the time. Yet when there are several documents (such as ACH remittance advice), it times out and doesn't produce all of them. This also happens for another client in a similar Terminal Server environment, but it happens when printing several General Journals. Most of them print to PDF, but then they get the error 'Printer not activated, error code -30' after which it won't print the remaining journals. Has anyone else experienced (resolved?) this issue in a Terminal Server environment?

I have a client who has experienced the same error after printing several ACH remittance advices, and they are not using a terminal server but are Sage 100 advanced. Would sure love to know what is the cause of this. We have applied every Sage PDF converter remedy, as well as uninstalled and reinstalled the workstation.

Adv or Std? Is the TS connected with a GB switch to the server? I have a couple clients that this happens with. When we test by sending directly from the Sage server, there are no issues. If ADV, is the CS ODBC service enabled? At another client, user would be running updating journal entries while running PR or AP DD advices. That was corrupting some of the PDF's as well.

The customer having the problem with ACH remittances is on Standard 2015, and the Sage Server and Workstation share the Terminal Server instance in that case. The customer having issues printing Journals is on Advanced; also 2015. They have Sage Server on an application server connected at GB speed to the Terminal Server running Sage Workstation. The ODBC service is enabled.

Make sure all the printers are active, valid printers.

Is there by any chance a non-standard character within the vendor number (or anything in the intended PDF file name which would require character substitution)? (I ran into a Paperless problem recently and noticed slash characters in the affected customer #).