How to recover when Exchange Server 2003 is unable to start

MS Exchange Server is the email service3. During the database restoration, incorrect log
management suite from Microsoft. It is used forfiles were replayed.
emailing, calendaring, managing contacts and tasks,4.The database log files were removed that were
providing data storage, etc. All such data is storednot fully committed.
in an EDB (Exchange Information Store Database)Such logical corruption issues are not immediately
file. Sometimes, the EDB file can get corrupt duespotted by the backup program. These errors are
to various reasons such as database headerdetected when you try to access the specific
corruption, abrupt system shutdown, transactionpage where the data is stored.
log files corruption, etc. You should consider takingResolution
appropriate corrective measures to resolve theTo resolve this situation, you should perform the
issue. However, if you are unable to do so thenfollowing methods, preferably in the given order:
you should use a third-party Exchange Server1. Restore from backup: You should restore the
Recovery software to do the needful.database with its online backup. However, you
Consider a scenario wherein you are havingmust ensure that the backup is clean and updated
Microsoft Exchange Server 2003 in yourbefore this corruption occurred.
organization. When you try to start MS Exchange2. Run ESEUTIL utility: You should use the
Server, it does not start. An error message isESEUTIL tool. It verifies the structure of database
displayed, that is:tables and perform offline defragmentation on the
"1067 The information store terminateddatabase.
abnormally."3. Run ISINTEG utility: You should use the
CauseISINTEG tool. It rebuilds the information store
The root cause of this error message is that theafter the restoration and fixes the errors in the
EDB file has corrupted because of errors in logicalinformation store.
database structure. It could have happenedThe aforementioned methods should resolve the
because of following reasons:issue. However, if the problem is still not
1. Certain transactions were not committed to theaddressed then you should use a third-party
hard disk by disk caching. Because of this, theexchange recovery software to do so. Such
server has stopped responding.read-only tools are able to repair the corrupted
2. The hard disk controller of the server isEDB databases without damaging the original
defective.contents.