| Previous | Next |
| ERROR_CLUSTER_WATCHDOG_TERMINATING | ERROR_CLUSTER_INVALID_NODE_WEIGHT |
ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES
Possible ownership does not guarantee runtime compatibility
ERROR_CLUSTER_RESOURCE_VETOED_MOVE_INCOMPATIBLE_NODES means the resource’s placement logic determined that the destination node cannot host the workload compatibly. A node can appear in the possible-owner list yet still fail a dynamic check involving hardware, firmware, network, storage, feature level, or resource-specific state.
Compare the resource and all dependencies across the source and destination nodes. Record installed features, driver and firmware versions, accessible networks and disks, CPU or device capabilities, and vendor resource DLL diagnostics. Update the possible-owner list so it reflects real support, but do not remove the veto by forcing a move until the incompatible capability is identified.
Node compatibility data to compare
- Possible and preferred owners for the group and every resource.
- Hardware, firmware, driver, and Windows feature differences.
- Storage and network reachability from the destination.
- Resource-specific validation or vendor logs explaining the veto.
References
- Microsoft: possible and preferred owner configuration
- Microsoft: building the possible-owner list for a move
- ClusterLabs: independent reference on capability-based placement constraints
Looking for a different code? Search another status or error code.