Database engine is unable to replay log file sequence due to fatal error. No further updates to the database are possible
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2012-02-27
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
492 |
Event Source |
ESE |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine |
Rule Name |
Database engine is unable to replay log file sequence due to fatal error. No further updates to the database are possible. |
Explanation
This Error event indicates that the database engine cannot replay the log file sequence. Because this is a generic error, no specific errors are associated with this event in the event Description. Look for errors that are mentioned in the Description section of related events and 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 commonly described errors in events that are related to event 492 are the following:
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 Microsoft Exchange databases and log files are stored on network storage. This is unsupported. Additionally, the checkpoint file may be corrupted, or the log drive may have failed. The current log file may have been seized and either deleted or quarantined by antivirus software running on the server. Problems may also have occurred in the creation of the temp log file for the storage group (such as e00tmp.log ). Therefore, 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 that affect 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 have incorrectly quarantined a file, or a backup process may be temporarily denying access. A flat file backup system or antivirus software may be running against the database or may be 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 have to restore from a backup. To resolve this error, do one of the following:
Review the Application log for related events. For error 1811, make sure that the antivirus software is not running against the Exchange store and against the SRS database directories. Make sure that the database drive has not run out of space. Make sure that the database file exists where it is supposed to. For more information about correctly configuring your antivirus software, see the following Microsoft Knowledge Base article: Exchange and Antivirus Software.
For error 510, investigate the root cause of permissions issues, space issues, and other issues that affect 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 Information Store subdirectories. Use Exchange-aware online backup and antivirus software.
For More Information
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.