| Previous | Next |
| ERROR_HOST_NODE_NOT_AVAILABLE | ERROR_RESOURCE_NOT_FOUND |
ERROR_RESOURCE_NOT_AVAILABLE
The resource object exists but is not currently serviceable
This status is broader than ERROR_RESOURCE_NOT_FOUND. The cluster can identify the resource, but its current lifecycle or ownership state prevents the requested work. Availability can be affected by failed dependencies, an unavailable owner node, a pending transition, or role movement.
Because the resource exists, recreating it is usually the wrong first action. Capture its state together with its group, owner node, dependencies, and recent cluster log sequence so the blocking state is visible.
What to inspect
- Check whether the resource or its group is OnlinePending, OfflinePending, Failed, or moving between nodes.
- Inspect provider dependencies before restarting the dependent application resource.
- Correlate the first resource failure with later availability errors; this code is often a consequence rather than the initiating fault.
Get-ClusterResource | Format-Table Name, State, OwnerGroup
Get-ClusterGroup | Format-Table Name, State, OwnerNodeReferences
- Microsoft Open Specifications: Cluster Resources and Groups
- Microsoft: Get-ClusterResource
- Microsoft: Get-ClusterLog
Looking for a different code? Search another status or error code.