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: 103 Source: ESENT

<process name> (<PID>) The database engine stopped an instance (<instance>).
As per TB217936, this event may have many causes:
- The database instance failed to apply an Exchange Server service pack for a reinstall or an Exchange-aware restore.
- The database instance ran out of disk space.
- The database instance tried to restore multiple storage groups at the same time.
- The database instance applied an Exchange Server service pack. This caused the Exchange Server databases to be inconsistent.
See the article for recommended actions.
According to Microsoft, event 103 indicates which Jet instance has stopped. Event ID 103 has many potential causes - check events in the Application log before and after Event 103 to determine which errors are mentioned in the Description section of other events. See MSW2KDB for a list of known causes and troubleshooting steps.

See EventID 103 from source ESE98 for more information on this event.

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.