Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

Resolve Exchange Server error -501 JET_errLogFileCorrupt

wpedbtopst | October 1st, 2015 | general

Every now and then, there’s been a situation when Exchange administrator got stuck after being encountered with the error JET_errLogFileCorrupt that prevent him from mounting the data. This error occur because log file is not in healthy state and has become corrupted.

In Exchange server, log files play the most essential part since they are always used when Exchange server needs to be recovered. However, many a time log files also get damaged by giving an error -501 (0xfffffe0b)  JET_errLogFileCorrupt. This error makes recovery of Exchange server impossible. This article will explain the reasons & solutions of the problem.

Main Causes of the error 501 JET_errLogFileCorrupt

The main cause of this problem is when log file gets corrupted and is unable to write the changes to the Exchange database (EDB). Additionally, if the header of log file gets damaged due to some reason, the entire Exchange stops working in proper manner.

Check if log file is corrupted

Corruption in a log file is the only reason for this problem but if you want to confirm that log file is damaged or not then you can check in command line as shown below:

  • Go to the PowerShell command line
  • Run Eseutil tool by typing the command eseutil /ml Enn

How to solve the JET_errLogFileCorrupt error

The corrupted log file can be recovered using its backup. If you have a backup then all you have to do is restoring the backup & running Eseutility. But make sure to delete the damaged log file as soon as the copy of the log file is found.

When the log file is restored from the backup, a temporary file is created restore.env that store all logs that have not been committed to the Exchange Database (EDB) yet.

Then the next step is to run Eseutil command as shown below:

Eseutil /cc “Path of the restore.env”

The above command will fix log file issues & will delete the temporary file ‘restore.env’.

In case, if there is no backup then you can go for a hard recovery using Eseutility that will resolve the issue. However, hard recovery is not as easy as it seems, it requires deep knowledge of Eseutility. In addition, there is always a risk of copying the wrong data to the Exchange database. In such situation users can try expert suggested solution named Exchange Log Analyzer.

The following two tabs change content below.