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.
The server service was unable to map error code <error code>
|English: Request a translation of the event description in plain English.|
See ME872790 for a hotfix applicable to Microsoft Windows 2000.
See the links to "EventID 2510 from source Server" and "EventID 2510 from source NCP Server" for additional information on this event.
As a starting point, use "net helpmsg <error code>" to get a brief description of the problem. I.e. Error code 1722 (net helpmsg 1722) means "The RPC server is unavailable.". This event is quite similar to event 2510 having "Server" as source.
Error code 1722 = "The RPC server is unavailable." - This problem is caused by the JetAdmin port monitor being corrupted or outdated. See ME199915 and ME246523.
As per ME319335, this may also occur if the Windows Spooler service is stopped.
Sometimes, these error conditions during printing may occur when third-party fax software is installed either on an Windows NT print server computer or on a computer running Windows NT Workstation. See ME158751 for workaround.
ME246523 says that in certain conditions, this behavior can occur because of a conflict between FPNW and the 'NWMON' value in the registry. See the Q article for resolution. This article also apply to Error code 1726 ("The remote procedure call failed.").
|Private comment: Subscribers only. See example of private comment|
|Links: ME158751, ME199915, ME246523, ME319335, ME872790, EventID 2510 from source Server, EventID 2510 from source NCP Server|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated