Blogs >> Technology >>
Fixing The Database files in this store are corrupted Error
An error message while opening an Microsoft Exchange Server database
primarily occurs when the database gets corrupted or damaged. In most
situations, the database corruption occurs due to improper, unexpected,
or dirty shutdown. Corruption in Exchange database can be surmounted by
using a repair utility known as 'ESEUTIL /P'. This utility checks the
logical and physical integrity of the database and performs repair to
maximum possible level. However, there are certain situations, where
the database remains corrupted when this utility fails to repair. In
such situations, the user needs to restore the Exchange database from
an adequate and complete backup. But, if in case of no backup
availability, you will need to repair the Exchange database (.edb file)
by using an effective third-party Exchange Repair software.
To illustrate the above case, consider a practical scenario where you encounter the below error message that appears after corruption in Exchange 2003 database:
“The Database files in this store are corrupted ID no: c104173b ESM”
After the above error message appears, all the data (e-mails, contacts, notes, and more) becomes inaccessible. On viewing the event log, you encounter the below information:
“EventID 465
Information Store (3612) First Storage Group: Corruption was detected during
soft recovery in logfile E:\Program Files\Exchsrvr\MDBDATA\E00.log.
The failing checksum record is located at position END. Data not matching
the log-file fill pattern first appeared in sector 2061 (0x0000080D).
This logfile has been damaged and is unusable.
EventID 454
Information Store (3612) First Storage Group: Database recovery/restore
failed with unexpected error -501.
EventID 9518
EventID 9175
Resolution:
To surmount the above MS Exchange database corruption error message, you will need to follow the below steps:
1. Use 'eseutil/p' inbuilt repair utility to repair the database.
2. In case the command fails and you have not maintained any backup, 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 a safe and user-friendly MS 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.
To illustrate the above case, consider a practical scenario where you encounter the below error message that appears after corruption in Exchange 2003 database:
“The Database files in this store are corrupted ID no: c104173b ESM”
After the above error message appears, all the data (e-mails, contacts, notes, and more) becomes inaccessible. On viewing the event log, you encounter the below information:
“EventID 465
Information Store (3612) First Storage Group: Corruption was detected during
soft recovery in logfile E:\Program Files\Exchsrvr\MDBDATA\E00.log.
The failing checksum record is located at position END. Data not matching
the log-file fill pattern first appeared in sector 2061 (0x0000080D).
This logfile has been damaged and is unusable.
EventID 454
Information Store (3612) First Storage Group: Database recovery/restore
failed with unexpected error -501.
EventID 9518
EventID 9175
Resolution:
To surmount the above MS Exchange database corruption error message, you will need to follow the below steps:
1. Use 'eseutil/p' inbuilt repair utility to repair the database.
2. In case the command fails and you have not maintained any backup, 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 a safe and user-friendly MS 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.
|
|
