Friday, October 30, 2009

Checksum Errors on Exchange Server Database Pages

A corrupted or damaged Exchange Server database exhibits abrupt behavior while normal database operations. However, you can deduce the root cause of the issue and sometimes, solution to the problem by application log entries. You should restore the corrupted database from the last backup, if is available and valid. In case of database issues, you are recommended to use EDB Recovery Software to repair the damaged database.

For example, consider you use Exchange Server 2003 or Exchange Server 2000. You use Exchange online backup to backup your Information Store database and fail to do so. When you view the application log in Event Viewer, you encounter the below error message:  

“Information Store (2240) The database page read from the file "E:\program files\exchsrvr\mdbdata\priv1.edb" at offset 204275712 (0x000000000c2d0000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 303571876 (0x121823a4) and the actual checksum was 303571940 (0x121823e4). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup.”

This error is logged with event ID 474.  

Cause

Error 1018 indicates JET_errReadVerifyFailure error.

It results because of checksum errors on database pages. The prominent reason for this error to occur is Exchange database corruption due to file system errors. If the disk subsystem is suffering from issues, like defective disk drivers, faulty controller or outdated or incompatible firmware, this could result into Exchange database corruption.  

Solution

You can solve these problems by these methods:
1.Try to perform backup using different storage group located on a different server disk.
2.Diagnose and troubleshoot your Exchange Server running system for possible hardware issues
3.Update your system with the latest firmware and drivers updates available
4.If a clean data backup is available, restore your database
5.Perform hard repair of the database using Eseutil /p in case no suitable backup is present
6.Eseutil /p is a destructive repair operation that could delete the corrupted database pages.

To prevent the consequences, you should use safe EDB Recovery utilities. EDB Recovery Software are powerful tools to examine, repair and restore damaged Exchange databases using efficient scanning algorithms. These tools provide you graphically rich user interface and advanced features that result complete database repair.

Stellar Phoenix Mailbox Exchange Recovery is a fully-competent EDB Recovery Tool to systematically repair damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It provides safe EDB Repair and extracts all user mailboxes by converting them into Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

No comments:

Post a Comment