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.
TraceFileName parameter not located in registry; Default trace file used is .
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is SNMP?
This event occurs if you installed the SNMP (Simple Network Management Protocol) service, but did not configure the Evntagnt.dll file for debug tracing. See "JSI Tip 7526" for additional information about this event.
As per Microsoft: "This problem occurs if you install the Simple Network Management Protocol (SNMP) service but you do not also configure this service. This error event is logged by the SNMP service when you restart the computer". See ME832790 for details on this issue.
See ME889082 and MSW2KDB for additional information on this event.
Event mostly appears in combination with event ID 1015 of EvntAgnt and only on systems with installed SNMP service. I solved the problem by adding under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNMP_EVENTS\EventLog\Parameters" a value "TraceFileName", REG_SZ, containing a file name, for example "test.log". After restart, this file will be created under "%systemroot%\system32" and further SNMP information is logged into it.
|Private comment: Subscribers only. See example of private comment|
|Links: ME832790, ME889082, JSI Tip 7526, Event id 1015, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated