MS Exchange Exporter Comes to Great Use after Information Store Gets Corrupted

Corruption is a common problem even with the much stout Exchange Server.
Being the main repository and storage hub of entire email data of all users’
mailboxes, some or the other corruption issue is bound to come into this
database. Such corruption cases are frequently encountered and thus their
solutions are most often searched for. In this article, we will throw some light
upon the Exchange Information Store corruption and its recovery process.
Information Store Corruption: Exchange Information Store is most
likely to get affected and impacted adversely whenever any corruption issue
occurs in the database of Exchange Server 5.5. Exchange database is always prone
to such damages, which when occur, cause damage to the Exchange IS. A most
probable chance at this moment can be Priv.edb corruption or Pub.edb file
corruption also.
What Should Be Dome after Information Store Gets Corrupted? Getting
caught into such a damaging situation of Information Store (IS) corruption can
bring your business to a standstill after communication channel gets jammed in
your office due to Exchange corruption. To come out of this problematic
situation, the best thing that you can do is to convert (http://www.edbtopst.org/) EDB to PST using an MS
Exchange exporter; this will bring your unusable data again into usable form
i.e. of Outlook PST.
Symptoms Confirming Information Store Corruption
ISS, Information Store service does not start
Information store cannot be stopped
Information store not responding even though CPU usage level is 100%
Emails cannot be sent or received
On running ‘Isinteg, the Information Store Integrity utility’ you get the
error – 4294966746: JET_errDatabaseInconsistent
Steps to Recover and Repair Corrupted Public/Private Information
Store
First, give it a try to start your Exchange Information Store
Now, use ‘Eseutil.exe’ which is a command-line tool for checking the
consistency of IS databases
If database is consistent, then all log files are committed to the IS
However, if the database is inconsistent, and also the eseutil /r command
cannot return that database to consistent state, then you can use ‘Eseutil.exe’
tool for performing a hard repair
Delete all .log files present in the ExchSrvr\Mdbdata folder over the Server

Delete all .chk files present in the ExchSrvr\Mdbdata folder over the Server

In addition, if there exists an Temp.edb file in ExchSrvr\Mdbdata folder,
then you must delete it
Start ISS so as to verify whether the databases are working fine or not
After confirming that ISS is starting successfully, stop it
Defragment that database which has been just repaired
Now, you can use Isinteg.exe command-line tool for repairing Pub.edb and
Priv.edb
Finally, try to restart the IS database again
MS Exchange Exporter: If all other efforts fail, then the last resort
for you to try is to convert EDB into PST using an MS Exchange exporter. You can
use Exchange
Recovery software to perform this conversion in a seamless manner
as this software is everything but the best. Your call for action would call for
a minor investment but a major benefit of getting back entire Exchange database
content in usable form.

Additional articles about edb recovery

About the author

Amongst various useful tools is SysTools Outlook Recovery software, than helps in online OST to PST conversion.

Please Rate This Article

Select Rating Excellent Very Good Interesting Fair Could Use Improvement

Number of ratings: 0
Rating: 0