|Message:||process name (process id) valueThe database engine value.value.value.%7 started.|
ESE Event ID 100 indicates that the database engine started.
ESE Event ID 101 indicates that the database engine stopped.
ESE Event ID 100 is usually followed by a series of other ESE Events
describing an online restore, or mounting of information store databases.
If an online restore fails to complete, or a database fails to mount, you may
receive an Event ID 101, indicating that the database engine has stopped.
You may also receive this event when an information store dismounts for any
reason. If you try to mount the store again and the store fails to mount,
you may receive Event ID 100 indicating the database engine started, and then
again receive Event ID 101, indicating the database engine failed to start.
In Exchange System Manager, if the arrow points down and is red, which displays
on the Exchange System Manager icon, this indicates that the stores are
In summary, receiving ESE Event ID 100 simply means that the database engine
started. It does not mean the information store will mount, since it may be
followed by an ESE Event ID 101, which means the database engine stopped.
In this case, the store failed to mount. The reasons for ESE Event ID 101
are many and varied. These events by themselves are generic for restoring
and for mounting of the information store databases.
For examples of causes, there may not be enough permissions on the
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
Restore.env file. There may be file level virus scanning software running
against the log file directory.
In normal operations, if you receive ESE Event ID 100 or ESE Event 101, and
Exchange is functioning normally, no user action is required.
However, if an online aware restore of Exchange fails, or an information
store database fails to mount as expected, then ESE Event ID 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 ID 101.