() The database engine stopped the instance ().

Product: Exchange
Event ID: 103
Source: ESE
Version: 6.5.7638.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <instance> The database engine stopped the instance (<number>).
ESE Event ID 102 is as follows: The database engine started a new instance (Instance #).
ESE Event ID 103 is as follows: The database engine stopped the instance (Instance #).
ESE Event ID 104 is as follows: The database engine stopped an instance (Instance #) with error (Error #).
There is only one Jet database engine, ESE.dll, per server. But there can be one instance of Jet running per storage group. Event 102 signifies that an instance of Jet has started and indicates which instance has started. Event 103 indicates which instance has stopped. These events can occur in the normal scheme of Exchange operations, or they may be associated with errors. Event 103 never has an error mentioned in the Description section of the Event.
Event 104 definitely indicates that there is a problem and the named instance of Jet has stopped with a error associated with it that is named in the Description section of Event ID 104.
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. Known causes for the database instance stopping with Event 103 are as follows:
Failing to apply an Exchange service pack for a reinstall or an Exchange-aware restore.
Running out of disk space.
Attempting to restore multiple storage groups simultaneously.
Applying an Exchange service pack, which resulted in the databases becoming inconsistent.
Event ID 104 has a definite set of potential causes. The most probable causes are indicated in the Description section of Event 104:
Error -1090 = 0xfffffbbe = JET_errInstanceUnavailable = This instance cannot be used because it encountered a fatal error. If ESE encounters this error, ESE will not be able to roll back any transactions and it will dismount the databases in the Storage Group for that instance of Jet.
Error -1022 = 0xfffffc02 = 4294966274 = JET_errDiskIO = Disk IO error. A disk or controller failure has occurred, and access to the entire drive has been lost, sometimes temporarily. Check the System Log for I/O or drive errors near the time of the 439 Event. In this case, you may see Error -1022 in the description of Event ID 104. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a transaction log. Permissions have been removed from the folder where the file resides. The file has been marked read-only. The folder containing the file has been renamed or deleted. Error -1022 can occur when Exchange cannot write to the hard disk, and generates an error message: Either software that has been installed has prevented the write operation or the hard disk itself is corrupted. The event message, which accompanies the error message, refers to an error 1022. This type of error occurs when there is a disk input/output (I/O) error: It may mean that the hard disk has been corrupted. An error 1022 is generated by Exchange whenever Exchange cannot write to the hard disk. Even though you may have a problem with the hard disk (for example, it has been corrupted), this type of error may also be a result of other software that is not compatible with Exchange, which prevents Exchange from writing to the hard disk. This issue can also occur because of incorrect permissions on the Exchsrvr folder structure.
Error -510 = 0xfffffe02 = 4294966786 = JET_errLogWriteFail = Failure when writing to log file. This error has both been seen in the Description of Event 104 and has been more commonly with an associated event. Error -510 can be caused by permissions issues, space issues, and other issues affecting reads/writes to the disks.
User Action
For ESE Event ID 103, the resolution depends on the error code in the Description of the associated events in the application log. In many cases, no user intervention will be necessary.
For ESE Event ID 104, run “chkdsk /f /r” (without the quotation marks). If chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure. Make sure that SYSTEM has full control of Exchsrvr and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server.


Leave a Reply