| Previous | Next |
| ERROR_CLUSTER_INVALID_STRING_FORMAT | ERROR_CLUSTER_DATABASE_TRANSACTION_NOT_IN_PROGRESS |
ERROR_CLUSTER_DATABASE_TRANSACTION_IN_PROGRESS
Cluster database transactions cannot be nested implicitly
ERROR_CLUSTER_DATABASE_TRANSACTION_IN_PROGRESS means a new transactional update was started before the current cluster database transaction was completed. This usually indicates reentrancy, an unbalanced begin/commit path, or a retry that reuses transaction state after an earlier call returned asynchronously.
Track transaction ownership and lifecycle explicitly. Record where the transaction began, which thread or callback owns it, and whether exception handling skipped commit or rollback. Avoid calling configuration code recursively from a resource DLL callback. If several changes must be atomic, add them to one supported batch instead of opening a second transaction around an existing batch.
Transaction-lifecycle evidence
- Transaction or batch handle and creating call stack.
- Owning thread, callback, or management request.
- Commands already queued before the nested begin attempt.
- Commit, rollback, and cleanup paths for every early return.
References
- Microsoft: cluster database access model
- Microsoft: adding commands to a cluster registry batch
- Microsoft: cluster registry command sequencing
Looking for a different code? Search another status or error code.