| Previous | Next |
| ERROR_CLUSTER_RESOURCE_TYPE_BUSY | ERROR_INVALID_CLUSTER_IPV6_ADDRESS |
ERROR_RESOURCE_CALL_TIMED_OUT
Resource Monitor waited too long for the resource DLL
Cluster Resource Monitor invokes resource DLL entry points to control and check resources. Microsoft recommends that long-running resource DLL work be handled asynchronously so time-critical or other entry points are not blocked. This error indicates that a resource call did not complete within the expected window.
The timeout can be caused by the resource DLL itself or by a dependency it waits on, such as a service control call, storage request, network operation, or vendor API. Increasing timeouts without identifying the blocked call can only lengthen failover and recovery.
What to inspect
- Identify the resource and entry-point activity around the timeout in Cluster.log and Resource Control Manager events.
- Collect resource-specific diagnostics and, for a reproducible hang, a dump of the Resource Monitor process according to the vendor or Microsoft support procedure.
- Compare timing on another possible-owner node to find node-local dependencies such as storage, DNS, service, or security delays.
Get-ClusterResource -Name <ResourceName> | Format-List Name, State, ResourceType, OwnerGroup
Get-ClusterLog -UseLocalTimeReferences
- Microsoft: Recommended Practices for Resource DLLs
- Microsoft: Resource DLL entry-point functions
- Microsoft: Get-ClusterLog
Looking for a different code? Search another status or error code.