| Previous | Next |
| STATUS_HANDLE_NO_LONGER_VALID | STATUS_RM_DISCONNECTED |
STATUS_LOG_CORRUPTION_DETECTED
Preserve the log before attempting recovery
Transaction logs define which operations must be committed, rolled back, or recovered after interruption. Corruption therefore affects more than diagnostic history: it can remove the evidence required to decide the correct outcome of pending transactions.
Do not delete the log merely to bring the service online. First identify whether corruption is limited to a container, metadata, a restored file set, or the underlying storage. Application-level consistency checks may be required even after the transaction manager can start again.
What to inspect
- Take a read-only copy of the complete log set and associated metadata.
- Collect storage, filesystem, controller, and power-loss events around the first failure.
- Verify that all log containers came from the same backup or snapshot generation.
- Follow the resource manager's supported recovery or restore process and validate affected data afterward.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: using log streams with KTM
- Microsoft: transaction manager objects
- Microsoft: writing a resource manager
Looking for a different code? Search another status or error code.