I ran an offline defrag on an exchange 2003 database it stopped with the following error:"Operation terminated with error -1018 (JET_errReadVerifyFailure, Checksum error on a database page) after 389.31 seconds." Intergrity check also failed with checksum error. How can I repair this

Hi there, Please have a look on this.. http://support.microsoft.com/kb/314917Kottees : My Blog : Please mark it as an answer if it really helps you.

Hi davidjc52, Any updates? Please also check whether the eseutil is compatible with the current Exchange server database: Operation terminated with error -1018 (JET_errReadVerifyFailure, Checksum error on a database page) http://support.microsoft.com/kb/555524 If the issue still occurs, please run the Eseutil /P first. Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Frank Wang TechNet Community Support

thanks. that was very informative. Base on error and subsequent scan with eseutil /k, it looks the database is corrupt beyound repair. It had 150 page errors none repairable. Previously had run eseutil /p and 75GB database decreased in size to .98GB. Looks like we will try to pst all mailboxes hen try to rebuild exchange db.

We previously had run eseutil /p and the edb went from 75GB down to .98GB The previous kb was very helpful in explaining what the 1018 error meant. Looks like the db is beyond repair, although still mountable.

Error 1018 results because of checksum errors on database pages. The prominent reason for the occurance of this error 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. How you can solve ? You can solve these problems by these methods: * Try to perform backup using different storage group located on a different server disk. * Diagnose and troubleshoot your Exchange Server running system for possible hardware issues * Update your system with the latest firmware and drivers updates available * If a clean data backup is available, restore your database * Perform hard repair of the database using Eseutil /p in case no suitable backup is present Note: Hard repair (Eseutil /p) is a destructive repair tool that could delete the corrupted database pages. Thus, sometmes users have to face some critical data loss situations. To prevent such data lose consequences, you can use a third party Exchange database recovery utility like this: http://www.recover-computerdata.com/exchange-server-recovery.html This Software is powerful tool to examine, repair and restore damaged Exchange databases using efficient scanning algorithms.After repairing the database, this tool allows the users to directly mount the database file.

thanks. that was very informative. Base on error and subsequent scan with eseutil /k, it looks the database is corrupt beyound repair. It had 150 page errors none repairable. Previously had run eseutil /p and 75GB database decreased in size to .98GB. Looks like we will try to pst all mailboxes hen try to rebuild exchange db.

Hi davidjc52, If you are running Exchange 2003 Enterprise version, you can also try to create a new database then move mailboxes to the new one. Frank Wang TechNet Community Support

Thanks. It is exchange 2003 standard on sbs 2003 and that seems to be our only option as the db is badly damaged, although mountable. We will try to export each mailbox to a pst then move them in to new db.