| Previous | Next |
| ERROR_GROUP_NOT_FOUND | ERROR_HOST_NODE_NOT_RESOURCE_OWNER |
ERROR_GROUP_NOT_ONLINE
The clustered role has not reached an online state
A resource group can be Offline, Failed, or transitioning even when some individual resources are online. Since the group is the failover and ownership unit, operations that require an active role can reject a group that has not reached the required state.
Find the first member resource that prevented the group from becoming online. Starting the group repeatedly can obscure the sequence by generating additional recovery attempts without correcting the provider, property, or resource DLL failure.
What to inspect
- Inspect the group state and then list every resource whose OwnerGroup is the affected role.
- Read dependency order so an offline provider is not mistaken for the final application failure.
- Use cluster logs and FailoverClustering events to identify the first failed Online operation.
Get-ClusterGroup | Format-Table Name, State, OwnerNode
Get-ClusterResource | Where-Object OwnerGroup -eq <GroupName> | Format-Table Name, StateReferences
- Microsoft Open Specifications: Cluster Resources and Groups
- Microsoft: Get-ClusterGroup
- Microsoft: Get-ClusterLog
Looking for a different code? Search another status or error code.