| Previous | Next |
| STATUS_RM_NOT_ACTIVE | STATUS_TRANSACTION_NOT_JOINED |
STATUS_RM_METADATA_CORRUPT
Resource-manager metadata corruption is a recovery problem, not a normal transaction conflict
A durable resource manager stores enough information to reconnect transactions and enlistments after interruption. If that metadata cannot be validated, continuing to accept work could produce outcomes that no longer match the transaction manager log.
Preserve the log and metadata before attempting repair. The correct recovery path depends on whether the resource manager is an application RM or the filesystem RM used by TxF. Deleting files to make startup succeed can discard unresolved transaction state.
What to inspect
- Collect the resource-manager identity, log path, storage errors, and the first validation failure.
- Check whether files were restored independently, truncated, moved, or replaced from a different machine.
- Use the resource manager's documented recovery or restore procedure.
- Verify application data consistency after recovery, especially for transactions that were in doubt.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: writing a resource manager
- Microsoft: using log streams with KTM
- Microsoft: FSCTL_TXFS_QUERY_RM_INFORMATION
Looking for a different code? Search another status or error code.