The database engine started
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this event, do one or more of the following:
Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.
Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
100 |
Event Source |
ESE |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
The database engine started. This event can generally be ignored. If you are experiencing problems keeping your databases mounted, review the event log for ESE 101 events. |
Explanation
This Information event indicates that the database engine started. ESE event 100 is usually followed by a series of other ESE events that describe an online restore or mounting of Exchange store databases. If an online restore does not finish, or a database does not mount, you may receive a 101 event that indicates that the database engine has stopped. Exchange may also log ESE event 101 when an Exchange store disconnects for any reason. If you try to mount the store again and it does not mount, you may receive ESE event 100. This indicates that the database engine started.
There are many reasons for ESE event 101. These events are generic for restoring and for mounting of the Exchange store databases.
The following are some of the possible causes of ESE event 101:
There may be insufficient permissions on the directory where the database or logs exist to mount the store.
There may be missing log files on the production or in an online restore.
There may be old log files that are out of sequence with the log that is mentioned in the Restore.env file. There may be file-level antivirus software running against the log file directory.
User Action
No user action is required if ESE event 100 and ESE event 101 are logged as long as Exchange is functioning correctly. However, if an online database restore process fails, or if an Exchange store database does not mount as expected, ESE event 101 indicates that a problem with the database or its logs may exist. Check the Application log and the System log for related events to determine the exact sequence of events that lead up to ESE event 101.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.