Blogs >> Education & Books >>
How to recover when Exchange Server 2003 is unable to start
MS Exchange Server is the email service management suite from Microsoft. It is used for emailing, calendaring, managing contacts and tasks, providing data storage, etc. All such data is stored in an EDB (Exchange Information Store Database) file. Sometimes, the EDB file can get corrupt due to various reasons such as database header corruption, abrupt system shutdown, transaction log files corruption, etc. You should consider taking appropriate corrective measures to resolve the issue. However, if you are unable to do so then you should use a third-party Exchange Server Recovery software to do the needful.
Consider a scenario wherein you are having Microsoft Exchange Server 2003 in your organization. When you try to start MS Exchange Server, it does not start. An error message is displayed, that is:
“1067 The information store terminated abnormally.”
Cause
The root cause of this error message is that the EDB file has corrupted because of errors in logical database structure. It could have happened because of following reasons:
1. Certain transactions were not committed to the hard disk by disk caching. Because of this, the server has stopped responding.
2. The hard disk controller of the server is defective.
3. During the database restoration, incorrect log files were replayed.
4.The database log files were removed that were not fully committed.
Such logical corruption issues are not immediately spotted by the backup program. These errors are detected when you try to access the specific page where the data is stored.
Resolution
To resolve this situation, you should perform the following methods, preferably in the given order:
1. Restore from backup: You should restore the database with its online backup. However, you must ensure that the backup is clean and updated before this corruption occurred.
2. Run ESEUTIL utility: You should use the ESEUTIL tool. It verifies the structure of database tables and perform offline defragmentation on the database.
3. Run ISINTEG utility: You should use the ISINTEG tool. It rebuilds the information store after the restoration and fixes the errors in the information store.
The aforementioned methods should resolve the issue. However, if the problem is still not addressed then you should use a third-party exchange recovery software to do so. Such read-only tools are able to repair the corrupted EDB databases without damaging the original contents.
Stellar Phoenix Exchange Mailbox Recovery is a Exchange 2003 recovery software that enables you to recover corrupted EDB files from all instances of corruption. It is supported by MS Exchange 2007, 2003, 2002, and 5.5. This MS Exchange Recovery tool is capable of recovering the EDB file in separate PSTs for each specific user. In addition, this Microsoft Exchange recovery software is capable of preserving the formatting of the RTF and HTML messages. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.
Consider a scenario wherein you are having Microsoft Exchange Server 2003 in your organization. When you try to start MS Exchange Server, it does not start. An error message is displayed, that is:
“1067 The information store terminated abnormally.”
Cause
The root cause of this error message is that the EDB file has corrupted because of errors in logical database structure. It could have happened because of following reasons:
1. Certain transactions were not committed to the hard disk by disk caching. Because of this, the server has stopped responding.
2. The hard disk controller of the server is defective.
3. During the database restoration, incorrect log files were replayed.
4.The database log files were removed that were not fully committed.
Such logical corruption issues are not immediately spotted by the backup program. These errors are detected when you try to access the specific page where the data is stored.
Resolution
To resolve this situation, you should perform the following methods, preferably in the given order:
1. Restore from backup: You should restore the database with its online backup. However, you must ensure that the backup is clean and updated before this corruption occurred.
2. Run ESEUTIL utility: You should use the ESEUTIL tool. It verifies the structure of database tables and perform offline defragmentation on the database.
3. Run ISINTEG utility: You should use the ISINTEG tool. It rebuilds the information store after the restoration and fixes the errors in the information store.
The aforementioned methods should resolve the issue. However, if the problem is still not addressed then you should use a third-party exchange recovery software to do so. Such read-only tools are able to repair the corrupted EDB databases without damaging the original contents.
Stellar Phoenix Exchange Mailbox Recovery is a Exchange 2003 recovery software that enables you to recover corrupted EDB files from all instances of corruption. It is supported by MS Exchange 2007, 2003, 2002, and 5.5. This MS Exchange Recovery tool is capable of recovering the EDB file in separate PSTs for each specific user. In addition, this Microsoft Exchange recovery software is capable of preserving the formatting of the RTF and HTML messages. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.
|
|
