Thursday, June 30, 2011

How to Solve priv.edb (Private Information Store) Corruption Error ?

Private Information Store (priv.edb) in MS-Exchange Server gets corrupt because of many reasons. These reasons include sudden server shutdown, malicious virus, anti-virus scanning, log file corruption, and human errors. Once the priv.edb file gets corrupt, you start getting nasty error messages on your screen. Due to these errors, data of the Information store becomes totally inaccessible. In such critical situations backup can be used. In case you don’t have a backup file, you have another option of using third party Exchange recovery software.

Consider a scenario, suppose you decided to defrag the Information Store. You do the same, to mount the database. But during this process, you receive an error message ''an invalid checksum''. When an eseutil /k priv1.edb utility is executed, below output gets received like this:

ERROR: page 1004909 checksum failed ( 0x2f906db8 / 0xb0259cd4 )
ERROR: page 1004925 checksum failed ( 0xe2028fbd / 0x4bfa488c )
ERROR: page 1004910 returned page 1337544633
ERROR: page 1004926 returned page 870534172
ERROR: page 1004910 checksum failed ( 0xa0d54f36 / 0x66c8980e )
ERROR: page 1004926 checksum failed ( 0x35d1f641 / 0x8f9622cc )
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.”

Why this Error?

Above error message occurs due to corruption of Exchange Server or Private information store (Priv.edb) file.

How to Solve the Problem?

In order to resolving the above error message, you have to follow the below mentioned measures:

- Run ESEUTIL/D utility so that Exchange Server database gets easily defragmented. With the help of this utility, minor corruption problems of database could be easily solved.
- If still same problem persists, then it is better to restore the database from a valid backup.
- If backup is unavailable, then you can use third party Exchange Recovery software to repair the corrupt database.

These tools are specially developed for Exchange Server recovery. After performing recovery by these tools, corrupt Exchange Server database becomes free from logical corruption.

Stellar Phoenix Mailbox Exchange Server Recovery can be relied to achieve the successful Exchange recovery results. The tool restores mailbox items, such as contacts, attachments, appointments, journal, tasks, events, and e-mail messages in .pst file format. The tool is designed for MS Exchange 5.5, 2000, 2003, 2007, and 2010. It is also compatibility with Windows Vista, 7, XP, Server 2003, and 2000.

No comments:

Post a Comment