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.
SAM failed to start the TCP/IP or SPX/IPX listening thread
|English: Request a translation of the event description in plain English.|
This issue occurs because the logon account for the Remote Procedure Call (RPC) service is changed from the Local System account to the NetworkService account in Windows Server 2003 with SP1. See ME930220 to solve this problem.
Olexandr A. Bilyk
In my case, the issue was produced by accidentally removing the SeImpersonatePrivilege privilege from the SERVICE account by an incorrect group policy. To fix the problem, reassign the privilege to the SERVICE account. This can be done by the way of Security Configuration and Analysis MMC console.
This issue can occur if the Client for Microsoft Networks is not installed. See ME307734 for more details.
According to Microsoft: "The error is benign and causes no loss in functionality. It may be due to a failure by the FPNW uninstall process to remove two registry values under the LSA Control key."
|Private comment: Subscribers only. See example of private comment|
|Links: ME172151, ME307734, ME930220|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated