Unable to roll back operation on database: all future updates will be rejected
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 |
471 |
Event Source |
ESE |
Alert Type |
Critical Error |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
Unable to roll back operation on database: all future updates will be rejected. Investigate common ESE error codes for this event: 510, 1022, and 614. |
Explanation
This Error event indicates that the database engine was unable to roll back an operation on the database specified in the event description. No entries in the database can be updated until this situation is resolved.
The cause depends on the error number in the Description section of the event. The most common error codes for event 471 are in the following list.
Error -510 = 0xfffffe02 = 4294966786 = Jet_errLogWriteFail = Failure when writing to log file. This error has both been seen in the description of event 104 and has been more typically seen with an associated event. Error 510 can be caused by permissions issues, space issues, SAN issues, and other issues affecting reads and writes to the disks.
Error -1022 = 0xfffffc02 = 4294966274 = Jet_errDiskIO = disk I/O error. The 1022 error is a generic error that appears whenever a disk I/O problem prevents Exchange from gaining access to a requested page in the database or to a check file. 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 or drive errors near the time of the 471 Event.
Error -614 = 0xfffffd9a = Jet_errCheckpointDepthTooDeep = Checkpoint depth is approaching 1024 generations. In other words, there is a maximum of 1024 logs that can be outstanding and uncommitted to the store at a time. When the checkpoint becomes greater than 1024 the ESE engine advanced the checkpoint incorrectly. If the database were to subsequently crash, ESE would start recovery from the wrong log generation and miss replaying operations (unless you deleted the checkpoint file). In earlier versions of Exchange, the maximum depth of the checkpoint was increased from 256 generations to 1024 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 Error -510, investigate the root cause of permissions issues, space issues, and other issues affecting reads and writes to the disks.
For Error -1022, check to 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 it is, run chkdsk /f /r. If chkdsk does not resolve the issue, examine the permissions on the Exchange Server folder structure. Make sure that System has full control of Exchange Server (install folder path) and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any file-level antivirus software running on the Exchange server. Check the System log for I/O or drive errors near the time of the 471 event.
For Error -614, receiving an error before reaching 1024 generations means that you can safely run recovery starting from the checkpoint because it has not incorrectly advanced. However, you should also make sure that you have identified the cause of the error. It 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 ones explained in this topic, see the following Microsoft Knowledge Base articles:
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.