This may be to select an account to bill to or enter their credentials when prompted.Ī handy way to see if this is the issue is to wait 10 minutes after printing the test job (I kid you not), and then head into the PaperCut admin interface, and look at Logs → Application Log. The job reaches the print server and is held in the queue, but the user sees nothing to release… Is the PaperCut Application Server waiting for the user to respond to a client Popup?Ĭertain PaperCut features like Account Selection and Unauthenticated Printing require users to run the PaperCut Client on their workstations to respond to pop-up messages. This is not a common issue, but if you come across this message then take a look at this article on the ‘attempted to be unpaused’ error.

This means the job has been ‘resumed’ outside of PaperCut’s control. If printing through the server is not desired, then one option is to install the PaperCut Direct Print Monitor on the user’s workstation so that these jobs can be tracked.Īt a minimum we need to make certain that the user is printing to a queue that is monitored by PaperCut, and that print jobs show up in the PaperCut Job Log, otherwise there is not much for PaperCut to track.ĭo you see an error message in the Application log with “A print job was attempted to be unpaused while being held and was deleted by the system”? You can ensure this by having the user connect to a shared print queue on the print server or by setting up PaperCut Mobility Print to share printers. If this is the case, consider deleting this print queue and connecting to the print server instead. It could be the case that the workstation is printing straight to a Bonjour-enabled printer, or directly to the IP address of the printer. If the print job isn’t reaching the server at all, then check to see how the printer connection is set up. The job never reaches the print server or printer… Is the print job somehow bypassing PaperCut? If this only happens with Mobility Print print jobs.If the job reaches the print server, the user can release the job, but nothing prints out….If the job reaches the print server and is held in the queue, but the user sees nothing to release….If the job reaches the print server but then disappears from the queue….If the job never reaches the print server or printer….Which behavior describes your issue the best?

Epson scanner software disapreas