0xFFFFFE0B JET_errLogFileCorrupt

When you work with MS Exchange Server then various log files are generated. These log files are very important for smooth working of Exchange Server. If any of the log files gets corrupt, following error message appears:

“Operation terminated with error -501 (JET_errLogFileCorrupt, Log file is corrupt)”

Reason:

The most common log files that get corrupt during the write operation have prefixes E00. The basic reason for the damage of .log files is torn write (incomplete physical write to log file). A torn write can occur due to abrupt system shutdown, virus infection, operating system failure, etc. When torn write occurs then checksum value for the affected log is calculated incorrectly due to which log file becomes defected.

The torn write is not a big issue. A log file, which has been reported damaged gets automatically repaired when the Exchange Server is restarted. But, in case the log file is not damaged due to torn write then following information is recorded in the application log:

Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 465
Date: 12/9/1999
Time: 2:48:48 PM
User: N/A
Computer: Computer_Name

Description:

Information Store (2428) Corruption was detected during soft recovery in log file E:\exchsrvr\THIRD\E00123ab.log. The failing checksum record is located at position 8189:328. Data not matching the log-file fill pattern first appeared in sector 8195.

The preceding information states that the log file cannot be repaired.

Solution:

To resolve the specified error message, discard the damaged log file and restore it from the backup. But, in case you do not have backup, you need to repair the database. You can repair the database either by using the eseutil.exe (built-in Exchange Server tool for database repairing) or by using any third-party MS Exchange Recovery software.

Use of the third-party to repair exchange server database is always recommended because eseutil.exe may not help you perfectly in repairing the database. While, a third-party Exchange recovery software thoroughly scans the damaged database and repairs it. Kernel for Exchange Server is a third-party Exchange repair and recovery software, which supports Exchange Server 5.0, 5.5, 2000, 2003, and 2007.

Comments are closed.