Truncate Exchange Logs

Recover Exchange Database from Log File Corruption (Exchange 2013/16)

Today morning I experienced a dismounted exchange database failure after numerous power failures. I attempted to bring back the database online but to no avail. I have provided below instructions on how to recover your exchange database from Log File corruption.

After running ESEUTIL soft recovery, I get the -514 error and upon further checks have deduced that the E00.log file might have been corrupted in the process. The command used to check that is:

seutil /ml "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 0629442944\E00"

The below error is generated after running the above command:

Log file: C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 0629442944\E00.log

ERROR: Cannot read log file header. Error -541.

Operation terminated with error -541 (JET_errLogFileSizeMismatch, actual log file size does not match JET_paramLogFileSize) after 2181.375 seconds.

I would like to highlight that the above database had circular logging enabled.


I simply went ahead and cut and pasted the contents of the log files associated with the folder and pasted them to an alternate location and then ran the soft recovery option afresh. I noticed that despite the process failing, it managed to create the E00.log file along with the E00.chk file afresh and was successfully able to mount the database. This got the mails flowing once again and looks like little was lost in the process.

Leave a Reply

Your email address will not be published. Required fields are marked *

PHP Code Snippets Powered By :