KB Home | Lexmark Print Queues occasionally get stuck
During late 2012, PaperCut Technical support and a customer ran into an obscure issue where print jobs could occasionally become stuck or error in the print queue. To clear these, restarting the Windows Print Spooler service and PaperCut Print Provider service would result in various errors, the most common being “Error 1053: The service did not respond to the start or control request in a timely fashion.”
In this specific situation it was found that the Lexmark print queues were using a custom Printer Port under the service “lmab_device”. Restarting this service when the Windows Print Spooler and PaperCut Print Provider services were restarted stopped this error from coming up again.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.