A Private Information Store (priv.edb) in Microsoft Exchange Server is a copy of data saved in the user mailboxes. Corruption in priv.edb file can occur due to improper server shutdown, log file corruption, virus attack, anti-virus scanning, or human mistakes. Once this file is corrupted, the user receives error message while accessing the database that further results in inaccessibility of stored records. To overcome such cases, the user needs to erase the corrupt priv.edb file and restore an updated file from an online backup. However, if the backup is inaccessible or deleted, then the user needs to opt for advanced third-party Exchange Server Repair software.

To explain the above issue, consider the below error message that appears when you try to access the data saved in your Private Information Store:

“ERROR: page 1004909 checksum failed ( 0×2f906db8 / 0xb0259cd4 )
ERROR: page 1004925 checksum failed ( 0xe2028fbd / 0×4bfa488c )
ERROR: page 1004910 returned page 1337544633
ERROR: page 1004926 returned page 870534172
ERROR: page 1004910 checksum failed ( 0xa0d54f36 / 0×66c8980e )
ERROR: page 1004926 checksum failed ( 0×35d1f641 / 0×8f9622cc )
…
1005074 pages seen
1001748 bad checksums
3324 uninitialized pages
1001748 wrong page numbers
62818 reads performed
3926 MB read
195 seconds taken
20 MB/second
197970362 milliseconds used
3151 milliseconds per read
54141 milliseconds for the slowest read
31 milliseconds for the fastest read
File: e:\exchsrvr\mdbdata\first storage group\priv1.STM
Checksum Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|-|-|-|-|-|-|-|-|-|-|
…
0 pages seen
0 bad checksums
0 uninitialized pages
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non
database file or corrupted db) after 196.109 seconds.”

Cause:

The above error message pops up only when the Private Information Store or your Exchange Server gets corrupted/damaged.

Resolution:

Below are some techniques that help you in resolving the above error message:

  • Execute ESEUTIL/D command to defragment your database. This enables you to resolve minor corruption problems in your database.

  • If the problem persists, then restore the database from a valid backup.

  • If no backup is available, then you need to use a third-party Exchange Server Repair tool to repair your database. These Exchange Repair utilities can be used after any type of logical corruption situation.

MS Exchange Repair is a safe repair application that repairs databases without modifying or overwriting any data. The Exchange Repair tool is easy to understand and restores the recovered user mailboxes in individual PST files. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, the tool supports Windows 7, Vista, XP, 2003 and 2000.