| Previous | Next |
| ERROR_CLUSTER_DATABASE_SEQMISMATCH | ERROR_CLUSTER_GUM_NOT_LOCKER |
ERROR_RESMON_INVALID_STATE
Resource Monitor will not overlap incompatible lifecycle operations
Resource DLL entry points implement resource lifecycle operations, and some can take time to complete asynchronously. While a resource is OnlinePending or OfflinePending, Resource Monitor can reject another control such as Fail because the current transition has not completed.
This often exposes concurrent management or a hung resource DLL. Determine which operation entered the pending state and how long it has been there before issuing more state changes.
What to inspect
- Capture the exact resource State and the timestamp at which the pending transition began.
- Review Cluster.log for the resource DLL entry point that was called and whether it reported pending progress.
- Check for multiple automation systems controlling the same role; repeated start, stop, fail, and move requests can collide with a valid in-progress operation.
Get-ClusterResource -Name <ResourceName> | Format-List Name, State, ResourceType
Get-ClusterLog -UseLocalTimeReferences
- Microsoft: Resource DLL entry-point functions
- Microsoft: Recommended Practices for Resource DLLs
- Microsoft: Get-ClusterLog
Looking for a different code? Search another status or error code.