|Component:||Microsoft Exchange Extensible Storage Engine|
|Message:||<process name> (<process id>) <storage group name>Corruption was detected during soft recovery in logfile <file name>. The failing checksum record is located at position <value>. Data not matching the log-file fill pattern first appeared in sector <value>. This logfile has been damaged and is unusable.|
A transaction log has become corrupted. If the problems in the log file are only torn writes, they will be corrected by the Jet engine. If the problems cannot be repaired, the database rejects rather than applies the data, logging an event in the application log similar to the following:
Corruption was detected during soft recovery in the log file. This log file has been damaged and is unusable.
This issue can occur if the log mentioned in the Event has become corrupted. Exchange cannot repair damage to log files because of factors other than torn writes, which will be fixed automatically by the ESE engine. Hardware failures that randomly damage a log file cannot be overcome because the data that was obliterated cannot be reliably reconstructed. ESE event 465 indicates damage that cannot be repaired.