| Previous | Next |
| ERROR_RESMON_SYSTEM_RESOURCES_LACKING | ERROR_ENCRYPTION_FAILED |
ERROR_CLUSTER_RESOURCE_VETOED_MOVE_NOT_ENOUGH_RESOURCES_ON_DESTINATION
Destination capacity is evaluated in addition to possible ownership
ERROR_CLUSTER_RESOURCE_VETOED_MOVE_NOT_ENOUGH_RESOURCES_ON_DESTINATION means the target node is otherwise a candidate owner, but cannot currently reserve enough capacity for the resource. Capacity can include memory, CPU, device slots, storage paths, ports, licenses, or vendor-defined utilization attributes—not only free RAM.
Record the requested destination and compare current consumption with the resource’s requirements. Check the entire group, because dependencies move together and can increase the reservation. Review placement or resource-provider diagnostics for the rejected capacity dimension. Freeing resources, choosing another node, or changing supported placement constraints is appropriate; repeatedly forcing the same move can create an outage on the destination.
Capacity and placement checks
- Resource group and all dependencies included in the move.
- Destination CPU, memory, devices, storage paths, ports, and vendor limits.
- Possible/preferred owners and current workload distribution.
- Provider-specific reservation or placement diagnostic.
References
- Microsoft: possible and preferred owners
- Microsoft: node selection during failover
- ClusterLabs: independent reference on utilization-aware placement
Looking for a different code? Search another status or error code.