0xFFFFFDDA JET_errDatabaseInconsistent

Read time 4 minutes

Microsoft Exchange Server stands as Microsoft Corporation’s sophisticated email messaging solution. Users’ emails and associated content find their storage within their dedicated mailboxes, residing within .EDB files on the Exchange Server.

Regrettably, Exchange Server is susceptible to damage caused by a multitude of logical and physical factors. When such issues arise, the Information Store, acting as Exchange Server’s vital repository, often bears the brunt of the impact. The Information Store is the guardian of the public folder store, safeguarding critical data. Should any complications surface within this core component, you may encounter the following challenges:

• You cannot start information store service.
• If the information store service is already running then you cannot stop it.
• CPU usage becomes 100% even when no other application is running.
• The process of transferring emails stops.

To resolve these issues, you should initiate a database restoration from an offline backup. Upon completing the restoration process, when you proceed to run the Information Store Integrity utility (Isinteg), you may encounter the following error message:

Follow the steps given below to resolve the preceding error message:

1. First of all, you need to check the consistency of information store. To check the information store consistency, execute the eseutil.exe tool.To check the consistency of priv.edb file, execute the following command:
   Drive:\exchsrvr\bin> eseutil /mh ..\mdbdata\priv.edb

   To check the consistency of pub.edb file, execute the following command:

   Drive:\exchsrvr\bin>eseutil /mh ..\mdbdata\pub.edb

   Note: In preceding commands, replace the term Drive with drive letter where Exchange Server is installed.

2. Verify the output of preceding commands to know if the information store is in consistent state or not. To check this view the output in the State line and if priv.edb and pub.edb are found consistent then go to step 7.
3. If anyone or both of the .edb files are found inconsistent then you need to perform soft recovery. During the soft recovery uncommitted logs are committed to the information store database. Execute the following command to perform soft recovery on
   priv.edb file:Drive:\exchsrvr\bin> eseutil /r /ispriv

   Execute the following command to perform soft recovery on pub.edb file:

   Drive:\exchsrvr\bin> eseutil /r /ispub

   Note: In preceding commands, replace the term Drive with drive letter where Exchange Server is installed.
   Soft recovery helps you bring the priv.edb and pub.edb in consistent state. However, after performing the soft recovery, you need to execute the step 1 to recheck the database state. If the files are found consistent then go to step 7.

4. In case, anyone of the file does not achieve consistent state then you need to perform hard recovery. Execute the following command to perform hard recovery on priv.edb file: Drive:\exchsrvr\bin> eseutil /p /ispriv Execute the following command to perform hard recovery on pub.edb file: Drive:\exchsrvr\bin> eseutil /p /ispub
5. Delete all .log, .chk, and Temb.edb (if exists) files in the exchsrvr\mdbdata folder.
6. Start information store service to confirm that databases are working.
7. Defragment the priv.edb and pub.edb files. Execute the following command to defragment the priv.edb file:
   Drive:\exchsrvr\bin> eseutil /d /ispriv

   Execute the following command to defragment the pub.edb file:

   Drive:\exchsrvr\bin> eseutil /d /ispub
8. After defragmenting the priv.edb and pub.edb files, you need to run isinteg.exe command-line tool to repair priv.edb and pub.edb files. Execute the following command to repair priv.edb file:
   Drive:\exchsrvr\bin>isinteg -pri -fix -test alltests

   Execute the following command to repair pub.edb file:

   Drive:\exchsrvr\bin>isinteg -pub -fix -test alltests

   On executing the preceding commands, you receive a report, which displays total number of warnings, errors, and fixes. Repeat the 8^th step until there is no warning, error, or fixes.

9. Start the information store. If it starts successfully go to step 10 otherwise restore the priv.edb and pub.edb by executing the following command:
   Drive:\exchsrvr\bin>isinteg “patch

After completing these steps, the database returns to a consistent state, allowing the information store to start successfully. Nevertheless, there may be instances where these steps alone do not resolve your issue. In such cases, you should consider repairing the priv.edb and pub.edb files using Kernel for Exchange Server, widely regarded as the premier Exchange Recovery software. This robust tool excels in addressing Exchange dirty shutdowns, checksum errors, and facilitates deleted mailbox recovery. Moreover, the software not only rebuilds the Exchange Server database but also securely preserves each recovered mailbox from EDB to PST file for your convenience.