Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1003 Source: EvntAgnt

TraceFileName parameter not located in registry; Default trace file used is .
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.

Windows Event Log Analysis Splunk App

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



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.