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.
A request from client was refused because system is out of resources.
|English: Request a translation of the event description in plain English.|
There are a few things you can try to help you identify what may be happening here. At the time of the failure, you can run the "winmsd" from the command prompt and look under the "Software Environment" section. Expand this section and look into the "Print Jobs" to establish if there are any jobs stuck while still processing. This will give you information on who printed, what was printing, and a time.
In addition, in Windows 2000 you can check the folder C:\winnt\system32\spool\printers. This folder should be completely empty. If there are files in the folder, delete them. If there are files located here, we may be dealing with a bad print driver.
See the link to “LPD server adds and prints control codes“ for more information on what may be happening.
|Private comment: Subscribers only. See example of private comment|
|Links: LPD server adds and prints control codes|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated