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.
Sharing printer failed + <error code>, Printer <printer name> share name <share name>.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "This can happen for many reasons; for example, the File and Printer Sharing component might not be bound to the network". See MSW2KDB for additional information about this event.
See ME831666 for a hotfix applicable to Microsoft Windows Server 2003.
Christophe Lubrano di Ciccone
According to ME185792 this may happen on NT 4 if the comment field for a shared printer contains more than 256 characters, including 2 characters for each new line.
Error code 1717 = "The interface is unknown." - In my case appeared after the hotfix installation: ME810647. The printer has no description, no location and is setup on a standard TCP/IP port and the server is SP3. (printer type HP LaserJet 2200 Series PCL 5e).
Error code 5 = "Access denied" - Occured after rights were changed on the printer to special access - changed rights on a W2K box on an NT4 server (set to print and manage documents).
Error code 5 = "Access denied" - This error occurs because the printer I created on my W2K server computer is not actually a real print device. It is a test printer for school.
As per ME273034, this issue can occur if the Startup value of the Spooler service is not set to use the "System Account" and is not set to interact with the desktop.
|Private comment: Subscribers only. See example of private comment|
|Links: ME185792, ME273034, ME831666, Error code 5, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated