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.
<service> failed to logon <user name> because of error <error code>.
|English: Request a translation of the event description in plain English.|
The local indexing service includes a catalog that references a privileged or remote scope in which credentials have been supplied for access. The credentials entered are incorrect or are no longer valid for the scope. Look for EventID 4135 to identify the wrong configured scope or examine the properties of each directory in each catalog of the indexing service for credentials. Once identified, either delete the directory, remove it from the catalog or supply valid credentials.
As per Microsoft: "This event record usually means you have entered the wrong password for a universal naming convention catalog". See MSW2KDB for more details.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 4135 from source Ci, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated