The data saved in MS Exchange Server database is divided into various pages, each having its own logical page number. Corruption in these pages primarily results in invalid page checksum or incorrect page number, which further results in change of sequence of pages. After the above situation occurs, the data saved in the database becomes inaccessible. In most of these situations, an Exchange user encounters an error message. To get past this error message, a user can either restore the database from a valid backup or repair the database using Eseutil or Isinteg utilities. However, in situations where no backup exists and these utilities fail to repair the database, you need to use a commercial EDB Repair application.

To elaborate the above scenario, consider a real-time case wherein you encounter the below error message while trying to access the database:

“-1018 JET_errReadVerifyFailure”

On viewing the event log, you get the below event ID 515 stating:

“%1 (%2) %3 Database %4: Page %5 failed verification due to a flush-order dependency mismatch. This page should have flushed before page %6, but the latter page has instead flushed first. Recovery/restore will fail with error %7. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware “losing” one or more flushes on one or both of these pages sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem. ”

After the above error message flashes on your screen, the database can not be opened. Additionally, the same error message appears every time an Exchange user tries to access the database.

Resolution:

To resolve the above file-level corruption error, you need to:

1. Use an adequate database backup to perform restore
2. Use Eseutil or Isinteg utilities to repair database
3. Use Exchange Server Disaster Recovery Analyzer Tool to mount the database.
4. In case where all the above measures fail to resolve the problem and the database remains inaccessible, you need to search for a third-party .EDB Repair application. Such EDB Repair Tool use powerful scanning methods to repair and restore logically damaged MS Exchange database.

.EDB Repair Software is a secure and reliable application that repairs logical databases created in Exchange Server 5.5, 2000, 2003, and 2007. Supported by Windows 7, Vista, XP, 2003, and 2000, the non destructive Repair EDB utility stores recovered mailboxes in .pst file format.