| Previous | Next |
| ERROR_CLUSTER_RESOURCE_VETOED_CALL | ERROR_CLUSTER_RESOURCE_VETOED_MOVE_NOT_ENOUGH_RESOURCES_ON_DESTINATION |
ERROR_RESMON_SYSTEM_RESOURCES_LACKING
The shortage is in Resource Monitor or host capacity, not the clustered resource’s data volume
ERROR_RESMON_SYSTEM_RESOURCES_LACKING means Resource Monitor could not reserve sufficient system resources for a resource to start or continue. The scarce item may be virtual memory, process handles, threads, desktop or job-object limits, or another host resource required to isolate and supervise the resource DLL. It does not specifically mean the clustered disk is full.
Measure the Resource Monitor process and node at the failure time. Record commit usage, handle and thread counts, process creation failures, and the number and isolation arrangement of resource DLLs. Look for leaks that grow after repeated online/offline cycles. Moving the group can temporarily succeed if another node has capacity, but the original node still needs leak or limit analysis.
Host resource measurements
- Resource Monitor process, resource type, and isolation configuration.
- System commit, available memory, handles, threads, and process limits.
- Growth across repeated resource restarts or failovers.
- Differences between the failing node and a node where the resource starts.
References
- Microsoft: Resource Monitor process isolation
- Microsoft: resource DLL memory and lifecycle practices
- Microsoft: collecting cluster diagnostics
Looking for a different code? Search another status or error code.