%1 (%2) %3Database %4 requires logfiles %5-%6 (%8 – %9) in order to recover successfully. Recovery could only locate logfiles up to %7 (%10).

Details
Product: Exchange
Event ID: 453
Source: ESE
Version: 8.0
Symbolic Name: REDO_MISSING_HIGH_LOG_ERROR_ID
Message: %1 (%2) %3Database %4 requires logfiles %5-%6 (%8 – %9) in order to recover successfully. Recovery could only locate logfiles up to %7 (%10).
   
Explanation

This Warning event indicates that the database requires log files that could not be located. The database requires log files in order to continue.

You will see the following phrase in the event description: Information Store number GUID Database path\filename requires log files (for example) 154-158 in order to recover successfully. Recovery could only locate log files up to (for example) 157.

There are several possible causes of this event. They are as follows:

  • An online restore fails because the log files are missing from the temporary folder that is specified in the Microsoft Windows Backup program under the temporary location for log files.

  • A hardware failure causes loss of log files in the log file sequence needed for the restore.

  • Antivirus software has quarantined the current log file, E0n.log.

   
User Action

To resolve this warning, do one or more of the following:

  • Verify whether the log files have been moved or deleted. If the log files have been deleted, restore them from backup media. If they have been moved, move them to the appropriate location. The event Description will specify the required files.

  • Check for related events and their description to determine specific causes and resolutions.

  • Try to locate the missing log files, put them in the appropriate folder and run eseutil /cc (hard recovery) or run eseutil /cc /t to specify another location for all the necessary logs together in one folder, and then mount the database.

  • If the log files cannot be located, restore from an earlier backup, or as a last resort, repair the database, run isinteg -fix. Then, use Move Mailbox to put the results to a blank database.

  • Stop the antivirus software that is scanning the Exchange store files directory, and check the registry settings for the antivirus software. Put the current log file back in the appropriate directory. Make sure that you have correctly configured your antivirus software. For more information, see the Microsoft Knowledge Base article 328841, Exchange and Antivirus Software.

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:

process name (process id) nameDatabase number requires logfiles number-number in order to recover successfully. Recovery could only locate logfiles up to %7.

Details
Product: Exchange
Event ID: 453
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) nameDatabase number requires logfiles number-number in order to recover successfully. Recovery could only locate logfiles up to %7.
   
Explanation

The database requires log files in order to continue.

You will receive the following phrase in the event Description:

Information Store (number) [guid] Database [path\filename] requires logfiles

[e.g.] 154-158 in order to recover

successfully. Recovery could only locate logfiles up to [e.g.] 157.

  • Cause 1 – An online restore fails due to log files missing from the

    temporary folder that is specified in the Microsoft Windows 2000 Backup

    program under the temporary location for log files.

  • Cause 2 – A hardware failure causes loss of log files in the log file

    sequence needed for the restore.

  • Cause 3 – Antivirus software has quarantined the current log file, E0n.log.
   
User Action

Generally, verify whether or not the log files have been moved or deleted. If

the log files have been deleted, restore them from backup media. If they have

been moved, move them to the appropriate location. The event text will specify

the required files.  Check for related events and their description to

determine specific causes and resolutions.

Here are some specific resolutions for the common causes above.

  • Resolution 1 – Attempt to locate the missing log files and place them in
    the appropriate folder and run Eseutil /cc (hard recovery) or run Eseutil /cc

    /t (using the /t switch) to specify another location for all the necessary

    logs together in one folder and mount the database. If the log files cannot be

    located, restore from an earlier backup or as a last resort, repair the

    database, run Isinteg -fix, and ExMerge the results to a blank database.

  • Resolution 2 – Restore from an earlier backup or as a last resort, repair

    the database, run Isinteg -fix, and ExMerge the results to a blank database.

  • Resolution 3 – Stop the antivirus software scanning the information store

    files directory and the M: drive and check the registry settings for the

    antivirus software.  Place the current log file back in the appropriate

    directory.

Related:

() Database requires logfiles – in order to recover successfully. Recovery could only locate logfiles up to .

Details
Product: Exchange
Event ID: 453
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Database <name> requires logfiles <number><number> in order to recover successfully. Recovery could only locate logfiles up to <number>.
   
Explanation

The database requires log files in order to continue.

You will receive the following phrase in the event Description:

Information Store (number) [guid] Database [path\filename] requires logfiles

[e.g.] 154-158 in order to recover successfully. Recovery could only locate logfiles up to [e.g.] 157.

  • Cause 1 – An online restore fails due to log files missing from the temporary folder that is specified in the Microsoft Windows 2000 Backup program under the temporary location for log files.
  • Cause 2 – A hardware failure causes loss of log files in the log file sequence needed for the restore.
  • Cause 3 – Antivirus software has quarantined the current log file, E0n.log.
   
User Action

Generally, verify whether or not the log files have been moved or deleted. If the log files have been deleted, restore them from backup media. If they have been moved, move them to the appropriate location. The event text will specify the required files. Check for related events and their description to determine specific causes and resolutions. Following are some specific resolutions for the common causes indicated in the Explanation.

  • Resolution 1 – Attempt to locate the missing log files and place them in the appropriate folder and run Eseutil /cc (hard recovery) or run Eseutil /cc /t (using the /t switch) to specify another location for all the necessary logs together in one folder and mount the database. If the log files cannot be located, restore from an earlier backup or as a last resort, repair the database, run Isinteg -fix, and ExMerge the results to a blank database.
  • Resolution 2 – Restore from an earlier backup or as a last resort, repair the database, run Isinteg -fix, and ExMerge the results to a blank database.
  • Resolution 3 – Stop the antivirus software scanning the information store files directory and the M: drive and check the registry settings for the antivirus software. Place the current log file back in the appropriate directory.

Related: