An error message when opening a Microsoft Exchange Server database mainly occurs when the database becomes corrupted or damaged. In most situations, database corruption occurs due to improper, unexpected, or dirty shutdown. Corruption in the Exchange database can be remedied by using a repair utility known as ‘ESEUTIL / P’. This utility checks the logical and physical integrity of the database and makes repairs to the highest possible level. However, there are certain situations in which the database remains damaged when this utility cannot be repaired. In such situations, the user must restore the Exchange database from an adequate and complete backup. But if no backup is available, then you need to restore Exchange database (.edb file) using effective third party Exchange Server Repair software.
To illustrate the above case, consider a practical scenario where you will encounter the below error message that appears after corruption in the Exchange 2003 database:
“The database files in this store are corrupt ID number: c104173b ESM”
After the above error message is displayed, all data (emails, contacts, notes and more) will become inaccessible. When viewing the event log, you will come across the following information:
Information archive (3612) First storage group: Corruption was detected during
soft recovery in log file E: Program Files Exchsrvr MDBDATA E00.log.
The failing checksum record is at position END. Data does not match
the log fill pattern first appeared in sector 2061 (0x0000080D).
This log file is damaged and cannot be used.
Information store (3612) First storage group: database restore / restore
failed with unexpected error -501.
Error log file is corrupted when starting Storage Group
/ DC = local / DC = _DomainName_ / CN = Configuration / CN = Services / CN = Microsoft
Exchange / CN = _DomainName_ / CN = Administrative Groups / CN = First Administrative
group / CN = Servers / CN = _ServerName_ / CN = InformationStore / CN = Initial storage
Group in the Microsoft Exchange Information Store.
Storage group: Jet initialization failed.
The MAPI call “OpenMsgStore” failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is not available for maintenance.
The MAPI provider failed.
Microsoft Exchange Server information store
ID No: 8004011d-0526-00000000 “
To overcome the MS Exchange database corruption error message above, please follow the steps below:
1. Use the built-in repair tool ‘eseutil / p’ to repair the database.
2. If the job fails and you have not backed up, use a commercial Exchange Server Repair application. Such third-party tools perform absolute Exchange repair after almost all logical crashes.
Stellar Phoenix Mailbox Exchange Recovery is safe and easy to use Exchange repair utility that repairs logically damaged .edb files. Compatible with MS Exchange Server 5.5, 2000, 2003 and 2007, the tool is completely non-destructive. It can be installed on Windows 7, Vista, XP, 2003 and 2000.