Unable to roll back operation on database: all future updates will be rejected
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2012-02-29
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 |
471 |
Event Source |
ESE |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine |
Rule Name |
Unable to roll back operation on database: all future updates will be rejected. |
Explanation
This Error event indicates that the database engine was unable to roll back an operation on the database that is specified in the event description. No entries in the database can be updated until this problem is resolved.
The cause of the problem depends on the error number in the “Description” section of the event. The most common causes of Event 471 are the following:
Error -510 = 0xfffffe02 = 4294966786 = Jet_errLogWriteFail = Failure when writing to log file: This error is associated with both Event 104 and, more typically, with an associated event. The 510 error can be caused by permissions issues, by space issues, by SAN issues, and by other issues that affect read and write operations to the disks.
Error -1022 = 0xfffffc02 = 4294966274 = Jet_errDiskIO = disk I/O error: The 1022 error is a generic error that is generated when a disk I/O problem prevents Exchange from gaining access to a check file or to a requested page in the database. A disk or controller failure may have occurred, and access to the whole drive has been lost, sometimes temporarily. The controller software or firmware may be out of date. Check the System log for I/O for drive errors that occurred near the time of Event 471.
Error -614 = 0xfffffd9a = Jet_errCheckpointDepthTooDeep = Checkpoint depth is approaching 1024 generations: The -614 error indicates that a maximum of 1,024 logs can be outstanding and uncommitted to the store at one time. When the checkpoint becomes greater than 1,024, ESE advances the checkpoint incorrectly. If the database were to subsequently crash, ESE would start recovery from the wrong log generation and not replay some operations.
Note
This error does not occur if the checkpoint file is deleted.
In earlier versions of Exchange, the maximum depth of the checkpoint was increased from 256 generations to 1,024 generations. When the checkpoint approaches 1024, ESE Event 471 is reported, ESE generates error -614, and the database disconnects.
User Action
To resolve this error, do one or more of the following:
For the -510 error, investigate the root cause of permissions issues, of the space issues, and of other issues that affect read and write operations to the disks.
For the -1022 error, make sure that the drive for the Exchange store files can be accessed, and that the path for the Exchange store files is specified correctly. If these conditions are met, run the chkdsk /f /r command. If Chkdsk does not resolve the issue, examine the permissions on the Exchange Server folder structure. Make sure that the System user has full control of Exchange Server (installation folder path) and of all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any file-level antivirus software that’s running on the server that’s running Exchange. Check the System log for I/O for drive errors that occur near the time of event 471.
For the -614 error, take note that if you receive an error message before you reach 1,024 generations, this indicates that you can safely run recovery starting from the checkpoint because it has not advanced incorrectly. However, you should also make sure that you have identified the cause of the error. This is typically a hung backup that should be easy to diagnose, or a long-running transaction that may be less obvious.
For Error 1022, see Microsoft Knowledge Base article 314917, Understanding and Analyzing -1018, -1019, and -1022 Exchange database errors.
For other ESE error codes other than the codes that are described in this topic, see the following Microsoft Knowledge Base articles:
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.