| Previous | Next |
| STATUS_TRANSACTIONMANAGER_IDENTITY_MISMATCH | STATUS_TRANSACTION_MUST_WRITETHROUGH |
STATUS_RM_CANNOT_BE_FROZEN_FOR_SNAPSHOT
The resource manager has state that prevents a consistent snapshot freeze
Snapshot coordination may need transaction processing to reach a stable point so the captured volume can later be recovered consistently. An RM can refuse or fail the freeze when transactions, recovery work, log state, or another lifecycle transition make that point unavailable.
Do not assume the snapshot is consistent merely because the storage layer created one. TxF exposes snapshot-specific controls to determine whether transactions were active and whether recovery is required on a mounted snapshot.
What to inspect
- Collect the RM state, active transactions, recovery state, and snapshot-writer events.
- Check for another freeze/thaw operation or long-running transaction.
- Retry only after the resource manager returns to a stable online state.
- Validate the snapshot with the TxF transaction-active query before using it for restore.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: FSCTL_TXFS_TRANSACTION_ACTIVE
- Microsoft: FSCTL_TXFS_QUERY_RM_INFORMATION
- Microsoft: alternatives to Transactional NTFS
Looking for a different code? Search another status or error code.