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.
<process name> (<PID>) The database engine stopped an instance (<instance>).
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of ESENT?
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.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 103 from source ESE98, MSW2KDB, TB217936|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated