%1 (%2) %3The logfile sequence in “%4” has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.

Details
Product: Exchange
Event ID: 492
Source: ESE
Version: 8.0
Symbolic Name: LOG_DOWN_ID
Message: %1 (%2) %3The logfile sequence in “%4” has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup.
   
Explanation

This Error event indicates that the database engine is unable to replay the log file sequence. Because this is a generic error, there are no specific errors associated with this event in the Description section of the event. Look for errors mentioned in the Description section of related events that refer to problems related to opening, creating, deleting, and writing log files. The cause of the error depends on the specific error. The most common errors in the Description section of events related to event 492 are as follows:

  • Error 1811 = 0xfffff8ed = Jet_errFileNotFound = File not found. The log file may be missing or there may be other causes for this error. For example, the current log file (such as E00.log) may have a mismatching signature between the log and the database. Error 1811 might also be generated when the Exchange databases and log files are stored on network storage. This is unsupported. In addition, the checkpoint file may be corrupted, or the log drive may have failed. The current log file may have been seized and deleted or quarantined by antivirus software running on the server. There have also been problems creating the temp log file for the storage group (such as e00tmp.log ). The temp log file may be corrupted.

  • Error 510 = 0xfffffe02 = 4294966786 = Jet_errLogWriteFail = Failure when writing to log file. Error 510 can be caused by permissions issues, space issues, SAN issues, and other issues affecting reads and writes to the disks.

  • Error 1032 = 0xfffffbf8 = 4294966264 = Jet_errFileAccessDenied = Cannot access file – the file is locked or in use. Another process has locked the file. Antivirus software may mistakenly quarantine a file, or a backup process may temporarily deny access. A flat file backup system or antivirus software may be running against the database or checking file directories. This error can also occur if the permissions on the folder that contain the files for the Exchange stores are not sufficient for the stores to function properly.

   
User Action

To resolve this error, you must correct the problem and restart the Microsoft Exchange Information Store service. Alternatively, you may need to restore from backup. Do the following to resolve this error:

  • Review the Application log for related events. For error 1811, ensure that the antivirus software is not running against the Exchange store and the SRS database directories. Ensure that the database drive has not run out of space. Ensure that the database file is present where it is supposed to be. For more information about properly configuring your antivirus software, see the Microsoft Knowledge Base article 328841, Exchange and Antivirus Software.

  • For error 510, investigate the root cause of permissions issues, space issues, and other issues affecting reads and writes to the disks.

  • For error 1032, change the permissions on the folders that contain the Exchange store files to the default permissions. Configure the flat file backup and antivirus software to not scan the Exchange Server Information Store subdirectories. Use Exchange-aware online backup 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:

Leave a Reply