| Previous | Next |
| ERROR_NO_TXF_METADATA | ERROR_CANT_RECOVER_WITH_HANDLE_OPEN |
ERROR_LOG_CORRUPTION_DETECTED
The transactional recovery log contains data the RM cannot safely replay
ERROR_LOG_CORRUPTION_DETECTED belongs to the Windows Kernel Transaction Manager transaction-processing model. KTM resource managers can use log streams to record state needed to recover enlistments after a crash. The recovery process depends on matching durable RM information with KTM notifications and stored enlistment recovery data. Corruption in that log is therefore a recovery-integrity failure: the RM may be unable to determine what work was prepared or how to reconcile an outcome.
Preserve the log and collect CLFS, filesystem, and storage events before recreation. Determine whether the code comes from a custom RM log or a TxF resource-manager log, because the supported recovery procedure differs. For custom software, validate restart-area and record parsing against the version that wrote the log. Do not infer that all affected transactions rolled back; KTM presumed-abort rules apply only when the coordinator recovery model says so, not when RM durable state is unreadable.
What to inspect
- Identify the RM and physical log stream that reported corruption.
- Correlate with CLFS, NTFS, disk, and restore events.
- Reconcile in-doubt resource data before discarding or recreating the recovery log.
References
- Microsoft: KTM resource-manager log streams and recovery
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: transactional resource manager and log management
Looking for a different code? Search another status or error code.