| Previous | Next |
| ERROR_TRANSACTIONMANAGER_IDENTITY_MISMATCH | ERROR_TRANSACTION_MUST_WRITETHROUGH |
ERROR_RM_CANNOT_BE_FROZEN_FOR_SNAPSHOT
The resource manager cannot be frozen at a snapshot-consistent point
ERROR_RM_CANNOT_BE_FROZEN_FOR_SNAPSHOT belongs to the Windows Kernel Transaction Manager transaction-processing model. Transactional resource managers coordinate in-flight changes whose outcomes may still be commit, rollback, or in-doubt. Snapshot integration needs a controlled point where transactional state can be represented consistently. This error means the RM current state cannot be frozen for that snapshot operation; it is not a generic VSS provider failure or a statement that the volume lacks snapshot support.
Inspect active and in-doubt transactions for the RM and the freeze sequence used by the snapshot component. KTM and TxF structures expose transaction-active state for snapshot-related processing, while RM recovery can leave transactions awaiting an outcome. Correlate the error with long-running prepare phases, disconnected coordinators, or a concurrent RM start or recovery. Retrying is reasonable only after the transient transaction state changes; forcibly terminating the RM can turn a freeze problem into recovery work.
What to inspect
- Enumerate active or in-doubt transactional work associated with the RM.
- Check whether RM recovery or startup overlaps the snapshot freeze request.
- Correlate the error with the snapshot coordinator rather than diagnosing storage capacity first.
References
- Microsoft: TxF savepoint and snapshot transaction structures
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: creating and recovering a KTM resource manager
Looking for a different code? Search another status or error code.