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.
|Source: W32 SMDR|
The description for Event (0) in Source (W32 SMDR) could not be found. It contains the following insertion sting(s): <date and time>
|English: Request a translation of the event description in plain English.|
From a newsgroup post: "I've seen this error a lot using NDS Corp Ed. Although is reported as an error, it does not actually cause a problem. Novell NDS4NT support in the U.S. confirmed we can stop the SMDR service as we are not backing up the NDS directory from the NT server. This prevents
From another post: "It is not a real error - I only see it when the SMDR service starts up and NDS isn't fully running yet - mostly a timing thing. The thing is: do you see the SMDR service in the Tasks List? If so, there's nothing to worry about."
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated