Table of Contents
If you have print server log files on your computer, this blog post might help you fix the problem.
PC running slow?
PC running slow?
ASR Pro is the ultimate solution for your PC repair needs! Not only does it swiftly and safely diagnose and repair various Windows issues, but it also increases system performance, optimizes memory, improves security and fine tunes your PC for maximum reliability. So why wait? Get started today!
We are sometimes asked how to read the Windows event logs to understand what is happening with the new printing system. From time to time, we might also ask clients to collect these logs to help us better understand what might go wrong.
Of course, most of the protocols are very detailed and not painful for humans. Basically, if you are looking for an easy way to meet people and understand what printing is, you might be interested in Print Logger or PaperCut NG.
If you are doing this for some reason and you know exactly what you are doing, read on …
Service Prints Administration Log
How do I find print logs on a print server?
Step 1. Turn on logging. On the Event Viewer toolbar, click Applications and Services Logs -> Microsoft -> Windows -> Print Service -> Running. Right click on Operational and select Properties. Check the box next to Enable Vedethe magazine. Click Apply with OK.
The service image management log displays events related to maintaining the print queue, such as printer sharing and printer driver installation. This symbol is enabled by default.
- On the specific affected Windows system (it could be one of two clients or servers) open Event Viewer by pressing Windows Key + R after typing eventvwr.msc and pressing Get to get.
- Expand the possibilitiesand Applications and Services, then Microsoft, and then Windows using PrintService.
- Right-click the administration log and select Save All Events As.
- Select the event files (* .evtx) and format them, save the file
Print Service Activity Log
The print service job log shows the capabilities of printing documents. It is enabled by default, but below we will tell you how to activate this log and ask yourself how to read it.
- In a vulnerable Windows function (it could be a client or possibly a server), open Event Viewer by pressing the Windows R key + then type eventvwr.msc using the Enter key a.
- Expand Applications and Services, then Microsoft, then Windows, and then PrintService.
- Right-click the Job icon and select Enable to start recording print jobs.
- Reproduce the problem you are trying to solve.
- Return to this area and save the activity logBy right-clicking the action icon and selecting Save All Events As.
- Select these event files (* .evtx) and format the file frequently.
Note 💡 The standard log size is literally 1024 KB, which means that the log can be quickly filled up and sent to a really busy print server. So, if you need to collect logs in a production environment, you can increase the log size by right-clicking the action log, selecting Properties, and multiplying the Maximum Log Size (KB) setting by something larger that might meet your requirements. amazing needs.
Tracking A Typical Print Job …
So now we know how to search for data, for example, what should a typical job look like in company logs?
There are usually 7-8 events for each job … In versions of PaperCut before 19.1, a person sees two 308 events twice. At that time, we changed the selection that pauses task analysis, so now there is only one 308 meeting.
After All, What Other Types Witheveryday Life?
Event 812 “The Spooler Was Unable To Delete The File …”
This event, which can be found in the activity log, appears in completely realistic print environments and sometimes gets the attention of administrators. This is a Schedule Document (SHD) that the Print Spooler uses to track the job and can run with or without PaperCut. Obviously, this will be ignored. You can find out more with Microsoft Technet at PrintService EventID 812.
Event 310 “User’s Printed Document Deleted”
This event, detected in the progress symbol, occurs when a print job has been completed by the user or by another tool (other than PaperCut). Look at the “Event User” field to see the user that is or the canceled account. When PaperCut cancels or deletes jobs, it again calls another method used from the Windows Print Spooler API that actually fires this event.
Event 372 Job View Error
This is an event that can be found in the hell logminiature, usually associated with associated print options that do not print and do not “disappear”.
We have seen various reasons for this, for example, it can happen …
- When macOS computers print to the Windows shared queue, it is configured to use Type 4 drivers.
- In a Find-Me print script where the source and city print queues are configured for different types of data, as detailed in our article Troubleshoot Find-Me Print Missing Jobs.
Do You Have Any Questions?
Let us know! I love that we are discussing what’s going on under the hood. Please feel free to leave comments below, you can visit our support portal for assistance.