| Event Id | 100 |
| Source | ESE |
| Description | %1 (%2) %3The database engine %4.%5.%6.%7 started. |
| Event Information | Accrding to Microsoft: 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: 1.There may be insufficient permissions on the directory where the database or logs exist to mount the store. 2.There may be missing log files on the production or in an online restore. 3.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. Resolution : 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. |
| Reference Links | Event ID 100 from source ESE |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.