Fix Error 528 Current Log File Missing Easily

It is very common for an administrator to face problems while using MS Exchange server in an organization. But it is the main task of the user to identify the reason behind error and to find a perfect solution for it. This article will focus on one of the usual error “Operation Terminated with Error 528 Current Log File Missing”. And will also cover all possible ways in which you can recover lost Log files.

We all aware of the importance and role of log files in Exchange Server. These are respiratory files of Exchange database as it maintains entire transaction record to retain data integrity in case of any service interruption. Also, these files are responsible for creating and modifying the operation of a message file. Once the log files are deleted Exchange database files are also affected and experience corruption. Hence, loss of Transaction log files can be catastrophic.

Cause of “528 - Current Log File is Missing”

There is variant of reasons responsible for the occurrence of the error:

• Which include improper installation of software, malware etc.
• Sudden power failure while using Exchange server is another reason. Currently running log files will automatically be missed during this action.
• Running an installed antivirus software on your system can lead to Operation Terminated with Error 528. This is due to improper configuration of the application.

An Expert advised Solution

For a professional and automated solution, you can use an EDB repair Tool which will fix entire Exchange database in a couple of minutes. The technique will resolve Error 528 Current Log File Missing as it will recover all lost data files very easily. Or you can opt any manual methods which are discussed below.

Resolution Of Error 528 Current Log File Missing

In order to fix this error, you can use any of the below-mentioned methods accordingly.

Solution 1:Use Eseutil for repairing the Exchange database

As suggested by Microsoft, in case of log file missing, You need to repair you complete database using Eseutil /p command. This command will repair your database but will lead to some minimal data loss. Therefore you need to perform Eseutil /d command to defragment the database.

This process will redo the database indexing and removes the empty white spaces.

Solution 2:Use NewmailboxRepairRequest Command

This is another and more preferred approach for repairing the database. This command is different as it will repair exchange database without dismounting it. Keeping the database online, it will fix and restore the data files. You can use the below-mentioned command for fixing the entire Exchange data files.

New-MailboxRepairRequest -Database[-StoreMailbox]

Solution 3: Use this method when Exchange database is not corrupted

• To begin with, Check if the antivirus is configured properly in exchange server. You can verify it by viewing Quarantine Program. If this option is not enabled, then all log files are considered as virus infected files. Hence, the server deletes them for security reasons.
• Therefore enable the Quarantine Program option and also move all log files from its current location to another file location. The log files should not be at the below mentioned location.
  p:\Program Files\exchsrvr\MDBDATA\E0000000.log
• Finally remove all .log files and you are left with res1.log, res2.log, & e00.chk files.
• Now restart all exchange server services for changes to take place. By now the error should be resolved.

Conclusion

The above-discussed methods will help you fixing “Operation Terminated with Error 528 Current Log File Missing”. But it is possible that manual method might not solve your problem perfectly. You can use an automated solution to et fast and efficient results.