Due to G2S having quite a bespoke setup, as Orbis is hosted but the many printers are on their own server, this can be tricky to find the cause of.
β
The solution is to check the C:\Windows\System32\spool\SERVERS\192.168.2.10 location on the server running TaskCentre and remove any files with the same timestamp as the stuck print job. We recommend backing this up, so it can be put back if needed.
Print job stuck in Print Spooler queue that will not clear down
Updated over a week ago