%1 (%2) %3Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and will not be processed.

Details
Product: Exchange
Event ID: 446
Source: ESE
Version: 8.0
Symbolic Name: REDO_END_ABRUPTLY_ERROR_ID
Message: %1 (%2) %3Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and will not be processed.
   
Explanation

This Warning event indicates that database recovery stopped abruptly. The logs after this point may not be recognizable and will not be processed. Some log files may be damaged.

   
User Action

To resolve this warning, you may have to remove all transaction log files from this point forward. This causes the loss of some data. You can also check log files for problems by using Eseutil /ML log prefix, for example, Eseutil /ML E00 if the log files all start with E00.

If the affected log files were restored with the backup and were not previously on the server, you should restore the backup again or omit the backup if it is an incremental or differential backup.

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