It is feasible to recoup data from a corrupt or damaged Information Store database

By | January 30, 2012

Guest Post by Axel Culver.

One of the most fundamental components of MS Exchange Server is the Information store. It consists of ‘Pub1.edb’ and ‘Priv1.edb’ files that are responsible for storing user emails, appointments, tasks, calendars, journals, notes, etc. These files may occasionally become corrupt due to power failure, virus infection, abrupt Outlook termination, etc. As a consequence, the information store fails to mount and renders all user mailboxes inaccessible.

For further clarification of the above issue, let us study some cases that are encountered due to information store corruption:

  • You fail to start MS-Exchange Information store service.
  • The Information store fails to stop.
  • The Information store becomes unresponsive and the level of CPU usage is always 100%.
  • The e-mail messages can neither be sent nor retrieved. Even if you stop and restart the information store, you fail to do so.
  • After restoring the Exchange Server databases from an offline backup and running the Information Store Integrity tool ‘Isinteg’, you receive the following error message:

“Error 4294966746: JET_errDatabaseInconsistent”

Grounds of the Problem:

The above problems are experienced as a result of Information store corruption.

How to fix Information store corruption?

In order to sort out the above issue, follow the below given steps:

  • Start the information store.
  • Verify the consistency of Information store databases through the command line tool ‘Eseutil.exe’. In case a database is consistent, all the log files must have been committed to the store. If the database is inconsistent, it may or may not be damaged.
  • In case of inconsistent databases, try to do a soft recovery of the files. This will help you commit all uncommitted logs to the Information store database.
  • If any of the databases is still inconsistent and the eseutil/r command fails, perform hard repair using the Eseutil.exe tool.
  • Remove all the .log and .chk files from the ExchSrvr\Mdbdata folder. Also, delete the ‘Temp.edb’ file.
  • Start the MS-Exchange Information store service and check whether the databases are working. If the Information store starts without any problems, stop the service.
  • Now, perform defragmentation of the database that you have just repaired.
  • For repairing ‘Pub.edb’ and ‘Priv.edb’, run the the Isinteg.exe command-line tool.
  • Try to start the information store database. If the information store starts successfully, then restart the service. In case you get the error message -1011, run the given command form the ‘bin’ folder:

“isinteg -patch”

  • Run the Directory Service/Information Store (DS/IS) Consistency Adjuster.

If the problem still persists, use a third party Exchange recovery utility. The third party applications uses advanced scanning techniques to scan the damaged database files thoroughly and effectively repairs damaged Exchange server databases to retrieve precious user mailboxes. Most of these tools perform a precise recovery of all EDB files of MS Exchange 2010, 2007, 2003, 2000, and 2000.

About the Guest Post Author:

The Author of this post is a technical writer and an active blogger. She also specializes in Microsoft Exchange Server, Microsoft Outlook, and other email clients. Currently she has been writing articles on various topics like how to perform Exchange Server recovery and Exchange BKF recovery in case of corruption.