Win32 error code returned by the print processor: 0x0."Ĩ05,Print job diagnostics,Rendering job 42.ģ07,Printing a document,"Document 42, Print Document owned by TestUser on \\PrintSRV01 was printed on PaperCut Global PostScript through port nul. No user action is required."Ĩ01,Print job diagnostics,Printing job 42.Ĩ42,Isolating printer drivers and other plug-ins,"The print job 42 was sent through the print processor winprint on printer PaperCut Global PostScript, driver PaperCut Global PostScript, in the isolation mode 1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). ![]() No user action is required."ģ09,Printing a document,"Document 42, Print Document owned by TestUser was resumed on PaperCut Global PostScript. This document will not print until the document owner resumes the print job. 800,Print job diagnostics,Spooling job 42.ģ08,Printing a document,"Document 42, Print Document owned by TestUser was paused on PaperCut Global PostScript. Around that time we changed the way the job is paused for analysis so now there is only one event 308. There will generally be 7–8 events for each job… In versions of PaperCut prior to v19.1, you would see two event 308 happen twice. Now that we know how to find the logs, what should a typical job look like in the Operational logs? So if you need to gather logs from a production environment you may want to increase the log size by right-clicking on the Operational log, select Properties, and increasing the Maximum log size (KB) setting to something larger that may suit your needs. Note □ The default log size is a paltry 1024 KB, which means this log can fill up quickly on a busy print server and rollover. Return to this area and save the Operational logs by right-clicking on the Operational log and click Save All Events As.Ĭhoose the Event Files (*.evtx) format, and save the file. Reproduce the issue you are trying to troubleshoot. ![]() Right click on the Operational log and select Enable log to start logging print jobs. ![]() It is off by default, but below we explain how to enable this log and how to read it. The Print Service Operational log shows events related to printing documents. Right-click on the Admin log and click Save All Events As.Ĭhoose the Event Files (*.evtx) format, and save the file On the affected Windows system (this could be either the client or server), open Event Viewer by pressing Windows key + R, then type eventvwr.msc and hit the enter key.Įxpand Applications and Services, then Microsoft, Windows, and PrintService. The Print Service Admin Log shows events related to the management of print queues like Sharing printers and installing print drivers, so it can be useful when trying to understand when a printer did not install correctly. If you’re here for a reason and you know what you’re doing, then read on… If you’re simply looking for a simple way to see and understand what people are printing, then you might be interested in PaperCut NG. ![]() Occasionally we might also ask customers to gather these logs to help us get a fuller understanding of what might be going wrong.Īdmittedly, these logs are very granular and not easy for people to read. From time to time we get questions about how to read Windows Event Logs to understand what’s going on with a print system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |