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

Details
Product: Exchange
Event ID: 104
Source: ESE
Version: 8.0
Symbolic Name: STOP_INSTANCE_ID_WITH_ERROR
Message: %1 (%2) %3The database engine stopped the instance (%4) with error (%5).
   
Explanation

This Error event first occurs when there are no log file names remaining. The affected storage group will not start until you resolve the problem.

The maximum number of transaction log files that can be generated in a single sequence is 2,147,486,647 (0x7FFFFFFF). Typically, it will take dozens to hundreds of years of operation before this many log files will be generated.

The transaction log file names resemble E0100012345.log, E01000ABCDE.log, E01000FFF00.log. The last eight characters of each log file name is the number of the log in the sequence. ESE has reached the last usable log generation number (0x7FFFFFEC), which is 16 logs before the maximum (0x7FFFFFFF) and all databases in the storage group have stopped with the error Jet_errLogSequenceEnd. Stopping this error before the end of the sequence enables more than enough additional logs for the database to be returned to a Clean Shutdown state.

   
User Action

To recover from this problem, you must reset the log file sequence. To do this requires removing all existing transaction logs. After you do this, a new sequence of log files, starting with 0x00000001 will be generated.

Before removing transaction logs, you must verify that all databases in the storage group are in a Clean Shutdown state.

For more information about how to reset the log file sequence, follow the steps under WORKAROUND in Microsoft Knowledge Base article 830408, Store databases are dismounted without warning or users cannot log on to their mailboxes in Exchange Server 2003 or in Exchange 2000 Server.

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.

Related:

Leave a Reply