%1 (%2) %3 The database engine stopped the instance (%4) with error (%5).

Product: Exchange
Event ID: 104
Source: ESE
Version: 6.5.7596.0
Message: %1 (%2) %3 The database engine stopped the instance (%4) with error (%5).

Event ID 104 frequently occurs with other related events. The following describes these three events.

  • ESE event 102   The database engine started a new instance (Instance #).

  • ESE event 103   The database engine stopped the instance (Instance #).

  • ESE event 104   The database engine stopped an instance (Instance #) with error (Error #).

There is only one Jet database engine, Ese.dll, per server. However, 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 ordinary operation of a Microsoft® Exchange Server environment, or they may be associated with errors. An error is never mentioned in the description section of event 103. Event 104 definitely indicates that there is a problem and that the named instance of Jet has stopped with a definite error associated with it. The error is named in the description section of Event 104.

Event ID 104 has many potential causes. Use the following explanations of common error codes to help you understand the root cause ESE 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 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. Access to the whole drive has been lost, sometimes temporarily. Examine 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 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 that contains 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. Error -1022 is frequently associated with Error 1022.

    Error 1022 indicates that there is a disk input/output (I/O) error. For example, it may mean that the hard disk has been corrupted. Error 1022 is generated by Exchange whenever Exchange cannot write to the hard disk. Although though you may suspect that there is a problem with a corrupted hard disk, Error 1022 may also occur when any software that is incompatible with Exchange is stopping Exchange from correctly 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 typically associated with a different ESE event. Error -510 can be caused by permissions issues, space issues, and other issues affecting reads or writes to the disks.

User Action

To resolve ESE Event ID 104

  1. Run chkdsk /f /r.

  2. If Chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure.

  3. If you still cannot mount the databases, troubleshoot any Microsoft Windows NT® file-level antivirus software running on the Exchange server.

For more information about related ESE event 103, search for information about that event in the Errors and Events Message Center.


Leave a Reply