Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 13 Source: Print
Document <number>, <document name> owned by <user name> was deleted on <printer name>.
|English: Request a translation of the event description in plain English.|
Indicates that a user deleted a print job from the queue.
To disable the informational messages from the print server open the Printers folder, select "Print Server Properties" from the "File" menu and in the "Advanced" tab select the level of logging that you desire. Restart the computer.
As per Microsoft: "This problem occurs because a change was made to the spooler process in Windows Server 2003 SP1. When an application submits print jobs by calling the ImpersonateLoggedOnUser function, the application may not have access to duplicate handles. Duplicate handles are required by the Print Spooler service". See ME909906 for a hotfix applicable to Microsoft Windows Server 2003.
This issue can occur because certain models of IBM network printers require the LPD queue to have a specific name. If the LPD queue has a different name, the print job may not be successfully completed. See ME282420 to solve this problem.
See MSW2KDB for additional information on this event.
In a recent experience, my windows 2000 sp3 server was receiving this event although none of my users were deleting their print jobs. Some jobs were printing (majority came out incomplete), others were being deleted before the print run. Was also receiving event id 10 but with "pages printed: 0". The issue was due to the usb connection. I connected the printer via serial cable and the problem was solved.
|Private comment: Subscribers only. See example of private comment|
|Links: ME282420, ME909906, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated