Have you ever come across a situation wherein when you try to mount a public store or a mailbox store in Microsoft Exchange Server, you are unable to do so and receive the below-mentioned error message?
“The database files in this storage are inconsistent
Id no: c1041739”
Moreover, when you try to mount the database, the following event is logged into the Application log:
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 log file 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 log file has been damaged and is unusable.
After this error occurs, the EDB file becomes completely inaccessible.
In fact, the root cause behind the occurrence of the above-mentioned error is inconsistency in the public store database or mailbox store database of your Exchange Server. Moreover, this inconsistency in the public store database is the result of EDB corruption.
In order to resolve the aforementioned error and perform Exchange recovery, you can use the Microsoft inbuilt utility, Eseutil.
Though the Eseutil utility is aimed at repairing the damaged EDB file and performing Exchange recovery, Eseutil is able to repair only minor corruptions of an EDB file. In case the EDB file is highly damaged or severely corrupt, the Eseutil utility proves incapable of repairing the damaged and corrupt EDB files.
Since the Eseutil utility fails to repair highly corrupt EDB files, there has to be some other mechanism by which you can repair the damaged and corrupt EDB file and effectively perform Exchange database repair.
With the help of an efficient and powerful third party Exchange recovery tool, you can easily and accurately repair the damaged and corrupt EDB files.
Kernel for Exchange Server is an effective, eminent, and efficient Exchange database repair tool that has the ability to repair the damaged and corrupt EDB files, corrupted due to almost any reasons.