If you have face issues while mounting the Exchange Folders intermittently, then there is a case of EDB (Exchange Database) file corruption. Because of this,you are unable to mount the database and access valuable information in the user mailboxes. Also, various users, too, cannot access their Outlook profiles. In these situations, in-built methods like Eseutil to recover the corrupted database should be used. In case, EDB recovery is not possible using these methods, then the only safe choice is to employ a third-party exchange server recovery software.
Taking a practical scenario for the same, you are not able to mount the public store folder in MS Exchange 2000 Server Standard Edition. The following error message is displayed:
“The database files in this storage are inconsistent
Id no: c1041739”
Also, when you see the Application log, the following error signature is logged with 477 Event ID
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 477
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. The log range read from the file "2095104 (0x00000000001ff800)" at offset 12800 (0x00003200) for -501 (0xfffffe0b) bytes failed verification due to a range checksum mismatch. The read operation will fail with error %7. If this condition persists then please restore the logfile from a previous backup.”
The mentioned problem occurs when the store database is in an inconsistent state because of database corruption.
In such cases, you should execute the following steps to perform EDB recovery:
Enter the following command in Command Prompt to know the state of the database:
“eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"
In the event of consistent database, the following text appears:
“State: Clean Shutdown”
If the database is inconsistent, then the text would be:
“State: Dirty Shutdown”
Use the Eseutil command using the following syntax to rebuild the database:
“eseutil /d /t:x "drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
Lastly, use the following command to repair corruption:
“Isinteg –s exchange_server_name –fix –test alltests”
However, if Exchange Recovery is not attained using these methods that means the EDB file is severely corrupted. In such cases, employing a third-party exchange server recovery software is the need of the hour. By using such read-only tools, you can get the Exchange databases without any modifications to the original database.
One of the best exchange recovery tools around, Stellar Phoenix Exchange Server Recovery software is one of the best. Exclusively developed for MS Exchange 5.5, 2000, 2003, and 2007, this EDB recovery software recovers the trapped user mailboxes in distinct PST files. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this exchange server recovery utility preserves the formatting of the HTML and RTF messages.