Hello,
We have a legacy PB/EAServer web application that has been in use for 7 years using the AmyUni print driver to generate PDFs.
It will generate PDFs successfully for a period of time and then the Print command eventually starts to receive -1. Restarting EAServer is only workaround that clears the print errors.
Initially these errors only occurred once every few months but this has gradually become worse over the years as the site became busier and we now must restart 4 or 5 times a day.
I originally thought the issue was with the AmyUni print driver so recently I switched to GhostScript using the SaveAs PDF command but the problem remains the same. We have 3 different PB components that generate PDFs so I set one to use AnyUni and the other 2 to use GhostScript. Once a print error is encountered all components, regardless of the print driver return -1.
There are no errors in the Windows event log. The print spooler does not appear to be locked. I’ve tried restarting the Print Spool service and refreshing components but the only workaround appears to be restarting EAServer.
I’m not sure what else to try short of a rewrite which may still be a year or two away.
Suggestions would be appreciated.
…Herb
Environment:
PowerBuilder 11.2 (build 8669),
EAServer 5.3.0 (build 53016)
EAF 4.0
Windows 2003 SP2
AmyUni 3.0
GhostScript 9.14