Read time 4 minutes

Usually, when corruption occurs in MS Exchange Server 2000 and MS Exchange Server 2003, the Information store is an affected component. Information store comprises of following database files:

  • Priv1.edb
  • Priv1.stm
  • Pub1.edb
  • Pub1.stm

Priv1.edb contains database of files which are in-process and stores non-STMP messages. The Priv1.stm file contains Simple Mail Transfer Protocol (SMTP) mail messages, i.e. those emails are in-process and those stored on the server. Pub1.edb database files comprise of public folder store for non-SMTP formatted data and Pub1.stm consists of public folder that store SMTP formatted information.

Generally, corruption comprises of one or both .EDB (Exchange Server 2000 and Exchange Server 2003 database) files. In most cases, either the Priv1.edb file or the Pub1.edb file (both located in Program Files\Exchsrvr\Mdbdata folder) is corrupted.

When the Information Store gets corrupt, user might come across symptoms mentioned below:

  • MS Exchange Information Store wont start.
  • You can’t stop the Information Store service and dependent services such as Post Office Protocol version 3 (POP3) and Internet Message Access Protocol Version 4rev1 (IMAP4).
  • The Information Store stops responding and the CPU usage level remains at 100 percent.
  • Clients cannot retrieve or send emails even if they stop and restart the Information Store service.
  • As you try restoring the Exchange Server 2000 and Exchange Server 2003 databases from an offline backup, run Information Store Integrity Checker utility (Isinteg.exe) patch, you may receive the following error:
    Error 4294966746: JET_errDatabaseInconsistent
  • When you try mounting mailbox store in Exchange System Manager, you receive error message given below:
    Unable to Mount the Mailbox Store with error c104173c “The Information Store is Busy”

When you try using Exchange System Manager to try mounting the database, you may receive the following error message:

An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.

ID no: c1041724
Exchange System Manager
Event ID: 9175
Source Exchange SA

Description: The MAPI call openmsgstore failed with the following error – network problems or the MSE server computer is down for maintenance.

Troubleshooting the recovery of information stored

  1. Make sure that Information Store service is stopped prior to running the Eseutil.exe program.
  2. Check the consistency of the databases. Run the following commands to check the consistency of the public and private databases
    C:\Program Files\exchsrvr\BIN>eseutil /mh
    “drive:\Program Files\exchsrvr\MDBDATA\priv1.edb”
    C:\Program Files\exchsrvr\BIN>eseutil /mh
    “drive:\Program Files\exchsrvr\MDBDATA\pub1.edb”

    In case an upgrade is done, the database files may be located in the C:\Exchsrvr\Mdbdata folder. If the databases have been optimized, database may be located on another drive.

  3. If the database is inconsistent and the eseutil/ r command does not return it in consistent state, then try the following process:
    Run the following commands
    To bring the Priv1.edb file back into a consistent state:

    C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /p priv1.edb

    To bring Pub1.edb file back into a consistent state:

    C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /p pub1.edb

    Click Yes to run the repair when the utility shows Scanning status of database integrity. When the process completes, the program displays the following message:
    Integrity check successful

  4. Delete all .log files in the Mdbdata folder, delete the .chk file and then delete the Temp.edb file (if it exists).
  5. Mount the database once and then immediately dismount them so that users cannot access them during this procedure.
  6. Halt the Information Store service and run a de-fragmentation of the private and public store databases. Moreover, you must run this step if you are low on disk space. To do so, run the following commands
    1. To defragment Priv1.edb:
      • C:\Program Files\exchsrvr\BIN>eseutil /d
      • C:\Program Files\exchsrvr\MDBDATA\priv1.edb
    2. To defragment Pub1.edb:
      • C:\Program Files\exchsrvr\BIN>eseutil /d
      • C:\Program Files\exchsrvr\MDBDATA\pub1.edb
  7. Use Isinteg.exe to fix the Pub1.edb database and Priv1.edb database. Isinteg.exe utility runs test on all areas of each of the databases and reports the results. Isinteg.exe tries to fix issues that are encountered. 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 8th step until there is no warning, error, or fixes.

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

However, if executing the steps mentioned above does not brings back your data into consistent state and information starts successfully then you need to repair the priv.edb and pub.edb files using Kernel for Exchange Server software. Its an efficient and result oriented Exchange Recovery software which is designed to repair .edb files and recover multiple mailboxes from them. EDB to PST converter saves the recovered mailboxes to PST and EDB files.

Kernel for Exchange Server