| Previous | Next |
| ERROR_CLUSCFG_ALREADY_COMMITTED | ERROR_CLUSCFG_SYSTEM_DISK_DRIVE_LETTER_CONFLICT |
ERROR_CLUSCFG_ROLLBACK_FAILED
Rollback failure can leave partially applied cluster membership state
ERROR_CLUSCFG_ROLLBACK_FAILED means a cluster configuration action failed and its compensating cleanup could not fully restore the node. A rollback may need to undo service configuration, local cluster database state, security settings, and membership-related artifacts. The node should therefore be treated as partially configured rather than simply “not joined.”
Preserve both the original failure and the rollback failure; the first explains why configuration stopped, while the second identifies incomplete cleanup. Inspect Cluster Service and ClusCfg protocol logs, check whether the node still reports membership, and use supported node or cluster cleanup commands. Re-running cluster creation without confirming the local state can compound the inconsistency and make later diagnostics ambiguous.
Signs of an incomplete rollback
- Cluster Service configuration remains although the node is not an active member.
- Local cluster database or service registration differs from peer nodes.
- A subsequent join reports that the node is already configured or cannot be added.
- Remote cluster state and local node state disagree after the failed action.
References
Looking for a different code? Search another status or error code.