• Article

The log files are not in valid sequence

 

Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this event, do one or more of the following:

  • Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.

  • Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.

Details

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

458

Event Source

ESE

Alert Type

Warning

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine

MOM Rule Name

The log files are not in valid sequence. File replay cannot succeed. Use Eseutil.exe to remove log files out of sequence or restore database with Eseutil.exe manual hard recovery option.

Explanation

This Warning event indicates that a gap in the log file sequence was detected. Log file replay cannot succeed if there are gaps in the sequence of available log files.

You will see the following phrase in the event description: Information Store number Restorenumber: The log files, Exxxxxxx.log and E0n.log, are not in a valid sequence. Log file replay cannot succeed if there are gaps in the sequence of available log files.

If all log files mentioned in the Restore.env file in the temp folder for the log files and check file, and the log files subsequent to that in the production folder are not in contiguous sequence, then ESE event 458 is logged.

Some of the causes are as follows:

  • This can occur if a full backup of the entire storage group is done and the log files are purged and then a previous backup of the storage group (before the last full backup is restored) is performed. This produces a gap of the log files that were purged.

  • It can also happen if there is more than one database in a storage group, and only one of the databases is restored to the storage group.

User Action

To resolve this warning, do the following:

  • Run eseutil /cm to view the content of the Restore.env file. Record the range of the log files. Remove all log files that are out of sequence with the log file range from Restore.env. Mount the database.

  • Restore a single database. Do not replay log files that were created since the backup that does not affect other databases in the storage group by performing the following steps.

    1. Restore the database, ensuring you click to clear the Last Backup Set check box.

    2. Perform a manual hard recovery with the /cc and /t switches of the eseutil command. For example: eseutil /cc temporary_folder /t (where temporary_folder is the folder that is specified in the Microsoft Windows NTBackup restoration temporary location for log and patch files dialog box, such as C:\Temp\My Backup).

    3. Mount the database.

For More Information

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.

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.