Exchange Server recovery method for corrupt information store

It is the information store which becomes the foremost victim of corruption in Exchange Server 2000 & Exchange Server 2003. The information store encompasses the elements like Private EDB files, Public EDB Files, Private STM file and Public STM files. The Microsoft Exchange Information Store becomes inaccessible and shows various errors like Error 4294966746: JET_errDatabaseInconsistent, The Information Store is Busy, etc. Amidst of the error, when a user tries to mount the database with System Manager he faces an error called “An internal processing error has occurred. A user can restore the Exchange Server with these methods.

Open the Microsoft Exchange Information Store and register the error first. Assure that the Information Store has been stopped before running the Eseutil.exe program. If the information store is not responding then disable it by restarting the server. Now check the consistency of databases with these commands:

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 you have executed an upgrade then the files would reside at C:\Exchsrvr\Mdbdata folder. Check whether the EDB files are inconsistent or not with these commands:

C:\Program Files\exchsrvr\BIN>eseutil /mh
C:\Program Files\exchsrvr\MDBDATA\priv1.edb > mypriv.txt

C:\Program Files\exchsrvr\BIN>eseutil /mh
C:\Program Files\exchsrvr\MDBDATA\pub1.edb > mypub.txt

If the Public or Private EDB folders are not residing in Program Files folder on the same drive then replace the “C:\program files\mdbdata\priv1.edb” with the full path of the Private and Public EDB files.

Note: If the files are not consistent then perform a soft recovery on the log files with C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /r E00 on the prompt and press yes. If this has not worked then bring the Private & Public EDB files to consistent state:

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

Now eradicate all .log files in the Mdbdata folder, .chk filed, and Temp.edb files. Quickly mount and dismount the databases so that other users cannot access them. Defragment the Public and Private EDB files:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\priv1.edb

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

Now run the Isinteg.exe tool for fixing the private & public EDB databases and restart the information store: C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests.

If the Information has not been restored then a user can derive the data with restore EDB tool. This is a majestic Restore Exchange tool which retrieves the EDB and STM files from any kind of corruption.