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: 2016 Source: Srv

The server was unable to allocate virtual memory.
See the link to "McAfee Support Solution ID: nai23719" for information on this event.
On Windows NT4 SP6a this happened when I tried to move the pagefile off the system partition, after the reboot, server would freeze about 10 seconds after login. Rebooted again, changed Virtual memory back to system partition real fast, havent made any changes since.
I believe that this has occured after system was infected with W32.Nimda.A. Symptoms: system overall slow down, excessive use of processor time, memory hogged. (although it could be a direct result of the virus).
As per Microsoft: "The page file has reached the maximum page file size. There are no pages available in main memory or in the page file. This generally indicates a Memory Leak in a another process. Determine the process at fault by using the performance monitor to monitor each process's page File bytes or Working Set."

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.