| Previous | Next |
| STATUS_TRANSACTIONS_NOT_FROZEN | STATUS_NOT_SNAPSHOT_VOLUME |
STATUS_TRANSACTION_FREEZE_IN_PROGRESS
STATUS_TRANSACTION_FREEZE_IN_PROGRESS means that KTM cannot start another freeze because a freeze operation is already running. The correct diagnosis is concurrency or an incomplete prior transition, not the state of one individual application transaction.
During snapshot work, a freeze boundary is coordinated with other services such as VSS. Starting a second freeze can interfere with the same global state transition, so the caller should identify the existing owner and wait for its completion or error path.
A second freeze overlaps an active freeze request
- Correlate snapshot, backup, and transaction-manager events by time and owning service.
- Determine whether the current freeze is progressing, timed out, or waiting on a transaction callback before starting another one.
- Avoid restarting services or forcing a thaw without understanding which component owns the active transition.
References
- Microsoft: VSS interoperability with KTM and DTC
- Microsoft: KTM transaction managers
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.