| Previous | Next |
| ERROR_HOST_NODE_NOT_GROUP_OWNER | ERROR_RESMON_ONLINE_FAILED |
ERROR_RESMON_CREATE_FAILED
Resource Monitor failed before the resource could be controlled normally
The Cluster service uses Resource Monitor processes to isolate and call resource DLL entry points. Resource DLLs expose Startup and instance-management functions such as Open and Close before normal Online or Offline processing can occur. A create failure therefore points earlier than application startup.
Check resource type registration, DLL loading, and resource-specific initialization. Repeatedly bringing the resource online is unlikely to help when Resource Monitor cannot create a usable resource instance in the first place.
What to inspect
- Identify the resource type and verify that its resource DLL and required runtime components are installed consistently on eligible nodes.
- Correlate Resource Control Manager and Resource Monitor events with the cluster log for load or initialization failures.
- For a third-party resource DLL, collect vendor diagnostics and check recent binary, service-account, or dependency changes before recreating the resource.
Get-ClusterResource -Name <ResourceName> | Format-List *
Get-ClusterResourceType
References
- 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.