For our remote users print jobs are becoming stuck in the queue, only restarting the Spooler allows printing to continue.  The remote users use a terminal server to access Sage 100 ERP. They can print for a period of time and then the print spooler freezes for one user at random and this causes a snowball effect where no users can print on the terminal server until the spool is cleared and the spooler is restarted. For the most part there are no error messages the print jobs just do not come through.  There are about 50 printers, each driver the client uses is identical on the TS.  This was tedious to verify but they were all matched and updated, but the problem remains.  Any feedback would be beneficial.

Specs:

1)  Application, recently upgraded from Sage 100 ERP 4.5 to Sage 5.0.  Professionally installed, but even this vendor has no answers for the printing issues.

2)  Terminal Server is a Win 2008 R2.  Utilizing RDP for the connection.

3)  Same drivers on the TS as the clients.

4)  All printing worked fine with Sage 4.5, but now we are having printer issues with Sage 5.0.  I have several tickets opened both Sage and the installer, but they have no solutions at this point.

5)  All other applications print fine;  Office, Notepad, Adobe, xps, etc.  Only Sage cannot print reliably.

6)  Only clearing the folder c:\windows\system32\spool\printers and then restarting the Spooler corrects the problem.  Then after sometime the problem returns.