0xFFFFFDDA JET_errDatabaseInconsistent

Microsoft Exchange Server is the highly advanced email messaging product developed by Microsoft Corporation. Emails and other related items created by users are stored in their respective mailboxes in .EDB file on Exchange Server.

The Exchange Server gets damaged anytime due to various logical and physical reasons. When any problem occurs in Exchange Server, the most affected component of Exchange Server is Information Store. An information store is the repository of Exchange Server where public folder store is saved. When there is any problem in the information store, you may face following issues:

  • 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 get rid of these issues, you need to restore the database from offline backup. After restoring the backup when you execute Information Store Integrity utility (Isinteg), following error message appears:

Error 4294966746: JET_errDatabaseInconsistent

Solution:

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:
  2. 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.

  3. 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.
  4. 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:
  5. 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.

  6. 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:
  7. Drive:\exchsrvr\bin> eseutil /p /ispriv

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

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

  8. Delete all .log, .chk, and Temb.edb (if exists) files in the exchsrvr\mdbdata folder.
  9. Start information store service to confirm that databases are working.
  10. Defragment the priv.edb and pub.edb files. Execute the following command to defragment the priv.edb file:
  11. Drive:\exchsrvr\bin> eseutil /d /ispriv

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

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

  12. 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:
  13. 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 8th step until there is no warning, error, or fixes.

  14. 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:
  15. Drive:\exchsrvr\bin>isinteg “patch

  16. Restart the information store.

After executing these steps, database comes back to the consistent state and information store starts successfully. However, it may also happen that executing these steps do not help you. If your problem does not resolve by executing these steps then you need to repair the priv.edb and pub.edb files using Kernel for Exchange Server software. It is the best exchange recovery software which efficiently handles the exchange dirty shutdowns, checksum errors, with deleted mailbox recovery. The exchange repair software rebuilds the EDB database and also saves each recovered mailbox to PST file.

Bookmark and Share
31 queries. 0.199 seconds.