| Previous | Next |
| ERROR_CLUSTER_INVALID_NODE_WEIGHT | ERROR_RESMON_SYSTEM_RESOURCES_LACKING |
ERROR_CLUSTER_RESOURCE_VETOED_CALL
A veto is an intentional resource decision, not an RPC transport failure
ERROR_CLUSTER_RESOURCE_VETOED_CALL means the resource handling code received the operation and deliberately refused it. The veto can protect application consistency during backup, maintenance, replication, failover, or another resource-specific transition. The outer Win32 code does not identify the private condition that caused the refusal.
Capture the operation, resource state, control code, and resource DLL or provider diagnostics. Check whether a dependent resource, maintenance mode, pending online/offline action, or application lock makes the call unsafe. Repeating the request without changing that condition should be expected to fail. Avoid bypassing the resource DLL with direct service, storage, or registry changes because that can violate the state the veto is protecting.
Information needed from the resource provider
- Exact move, control, online, offline, or configuration call.
- Resource state and pending operation.
- Provider-specific event or log entry accompanying the veto.
- Dependencies, maintenance, backup, or replication state.
References
- Microsoft: resource DLL responsibility for resource operations
- Microsoft: resource control callback contract
- Microsoft: supported clustered-resource movement
Looking for a different code? Search another status or error code.