Restore inaccessible or unmountable exchange server database easily

Transaction log file in MS Exchange server is the one that stores details about all the transactions performed in the database. But in certain circumstances, you may face problems when the transaction log file gets corrupt and thus does not allow you to access or mount the database and can even lead to severe data loss situations. Hence, the need arises to restore Exchange server.

Suppose a situation where you are trying to mount Exchange server mailbox or public store but instead of you get the following error message:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: c1041724”.

After this, you can observe the following events in Application Event log:

1. Event ID: 465 Source: Ese98 Type: Error Computer: Server1 Information Store (2184) Corruption was detected during soft recovery in logfile C:\Programme\Exchsrvr\mdbdata\E00000E8.log. The failing checksum record is located at position 6531:471. Data not matching the log-file fill pattern first appeared in sector 6600. This logfile has been damaged and is unusable. For more information, click

2. Event ID: 454 Source: Ese98 Type: Error Computer: Server1 Information Store (2184) Database recovery/restore failed with unexpected error -501.


The cause for the above encountered error can be the log file corruption or exchange server public store corruption. In any of the two cases, you need to go for restoring exchange server database.


You can try out the following solutions in order to fix up the error:

In case of log file corruption, first of all, you need to remove the log file and then restart Exchange server.

If the problem is due to exchange server public store corruption, then you must use Edb repair tool so as to restore exchange database which is highly capable to repair the database corruption issues and thus allows access to access or mount the database easily.