Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Document <document number>, <application> - <document name> owned by <user name> was printed on <printer name> via port <port name>. Size in bytes: <size>; pages printed: <no of pages>
|English: Request a translation of the event description in plain English.|
Indicates a successul printing. To disable this type of messages follow these steps:
- On the server open the Printers folder.
- In the File menu you will find "Server Properties".
- Use the Advanced tab to configure the logging level.
You have to restart the server for the changes to take effect. Just restarting the Spooler service is not enough.
If the number of pages is listed as 0 (with 0 bytes) then see ME232230 and ME319198.
If the job is listed as being owned by ANONYMOUS LOGON, then see ME323909. There is a fix available for this.
This event can occur if you redirect LPT1 using the "Net Use" command to use the shared network printer connected to the local computer, then print to it. See ME137065 for a workaround on this issue.
See MSW2KDB for additional information about this event.
I have a windows 2000 server on sp3 which had a network shared hp deskjet 930c via usb connection. The event was caused by 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: ME137065, ME232230, ME319198, ME323909, ME328020, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated