%1 (%2) %3Database recovery on ‘%5’ failed with error %4. The database is not in the state expected at the first reference of this database in the log files. It is likely that a file copy of this database was restored, but not all log files since the file copy was made are currently available. Procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the “more information” link at the bottom of this message.

Details
Product: Exchange
Event ID: 495
Source: ESE
Version: 8.0
Symbolic Name: ATTACHED_DB_MISMATCH_DURING_RECOVERY_ID
Message: %1 (%2) %3Database recovery on ‘%5’ failed with error %4. The database is not in the state expected at the first reference of this database in the log files. It is likely that a file copy of this database was restored, but not all log files since the file copy was made are currently available. Procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the “more information” link at the bottom of this message.
   
Explanation

This Warning event indicates that the database recovery failed. The database is not in the expected state at the first reference of the database in the log files. A file copy of this database was probably restored, but not all the log files were successfully restored.

This may be a critical error that prevents a storage group from initializing.

   
User Action

To resolve this issue, examine the Log Required field of the database header may indicate which logs are missing. To examine the field, run Eseutil /MH database filename. The Log Required field lists a numerical range of logs which must be converted from decimal to hexadecimal to identify the logs in the range. If the Log Required field is 0-0, no logs are needed.

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