Are you getting random error messages while trying to mount Exchange folders? If yes, then there is a prominent probability that the EDB database file is damaged due to any miscellaneous reason. Such corruption can lead to severe damages as important data of several users becomes insecure, which a very undesirable proposition. In such cases, you should use a third-party EDB recovery tool to recover corrupt EDB file if the traditional ways to fix the file fail to do so.
Let us take an instance in which you are unable to mount on an MS Exchange Server 2000 database. The following error message is displayed:
“The database files in this storage are inconsistent
Id no: c1041739”
In addition, the following error is logged in the Application event log for MS Exchange Server 2000:
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 465
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. Corruption was detected during soft recovery in logfile 4092:203. The failing checksum record is located at position 4117. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.”
The root cause of this problem is that either the public store database or the mailbox store database is in an inconsistent state.
To resolve the situations, you should either restore or repair the corrupt EDB file. This could be done using the following methods:
- Restore the backup: Restoring the backup can be done by performing the following steps:
- Move or rename the E00.log file. By default, it is stored in the Drive:\Program Files\Exchsrvr\MDBDATA folder.
- Restore the storage group and the log files from the backup file.
- Mount the database when the storage group is restored.
- Repair EDB database file: To repair the EDB database file, you need to perform the following steps:
- Click Start | Run, and enter ‘cmd’ in the ‘Open’ box.
- Press the ‘Enter’ key to open Command Prompt.
- Move to the Drive:\Program Files\Exchsrvr\Bin folder.
- Type the following command and press the ‘Enter’ key:
- Type the following command and press the ‘Enter’ key to defragment and rebuild the EDB database file:
- Verify the state of the database by using the following command:
- If the database is consistent, then the following text is displayed:
- Use the ‘isinteg’ tool with the following switches to repair the logical corruption:
- Mount the database and check if the error is appearing again or not.
eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb
eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
State: Clean Shutdown
Isinteg –s exchange_server_name –fix –test alltests
If the problem is still there, then you need to use a third-party EDB recovery software to recover EDB database file. The use of extremely safe scanning algorithms in a highly interactive user interface are some of the striking features of these EDB recovery tools.
Stellar Phoenix Exchange Server Recovery is one the best EDB recovery software that works well on Windows 7, Vista, Server 2003, XP, and 2000. With the ability to recover corrupt EDB files created for MS Exchange 5.5, 2000, 2003, and 2007, this EDB recovery utility extracts distinct PSTs from various user mailboxes.