Resolve ‘the database files are inconsistent’ error in Exchange 2000 server

At times, while using Microsoft Exchange 2000 server, you may face certain situations where you are unable to access the exchange database files which can further lead to errors like the database files are inconsistent. Similar is in the case where you are trying to mount a mailbox or public store in Exchange 2000 server, but instead of got the following error message:

The database files in this storage are inconsistent
Id no: c1041739

After getting this error, the following events are logged in the application log:

Event Type: Error Event Source: ESE98 Event Category: Logging/Recovery Event ID: 465 Date: Date Time: Time User: N/A Computer: Computer_Name 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.

Event Type: Error Event Source: ESE98 Event Category: Logging/Recovery Event ID: 477 Date: Date Time: Time User: N/A Computer: Computer_Name 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.

Cause:

Event id 465 or 477 occurs when the mailbox or public store you are trying to mount is in inconsistent state.

Solution:

In order to fix the database files are inconsistent error, first of all, you need to make sure about the exchange database inconsistent state. For this, type the following command in command prompt by moving on to Drive:\Program Files\Exchsrvr\Bin folder.If the output appears as State: Dirty Shutdown, the inconsistent state is confirmed.

eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_name.edb"

Then, the next step is to repair the exchange database. To do this, type the below command by moving on to Drive:\Program Files\Exchsrvr\Bin folder

eseutil /p "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"

After this, defragment and rebuild the database with the help of this command:

eseutil /d /t: x " drive :\program files\exchsrvr\mdbdata\ database_file_name .edb"

And lastly confirm the exchange database state to get output as State: Clean Shutdown by this command:

eseutil /mh " drive :\program files\exchsrvr\mdbdata\ database_file_name .edb"

But after following the above steps, the exchange database does not get repaired completely, then it is recommended to use corrupted edb repair tool which is highly competent enough to repair as well as restore all the database objects in an efficient manner.