| Previous | Next |
| ERROR_DEPENDENCY_TREE_TOO_COMPLEX | ERROR_CLUSTER_RHS_FAILED_INITIALIZATION |
ERROR_EXCEPTION_IN_RESOURCE_CALL
The failure crossed the resource DLL isolation boundary
ERROR_EXCEPTION_IN_RESOURCE_CALL means a call into the resource DLL escaped with an exception instead of returning a documented status. Resource DLLs run in Resource Monitor processes so that resource-specific failures are separated from the Cluster Service. The affected call may be Online, Offline, LooksAlive, IsAlive, or a control callback.
Collect the Resource Monitor dump, failing entry point, exception code, DLL version, resource parameters, and the cluster log around the call. Review lifetime and thread-safety of the resource context, callback cancellation, and buffers supplied through control codes. Restarting ClusSvc can remove immediate symptoms but loses the state needed to identify the resource DLL defect.
Developer-level evidence to retain
- Resource type, DLL path and version, and Resource Monitor process.
- Entry point and exception code or crash dump.
- Resource state and pending online/offline operation.
- Control-code buffers, context lifetime, and concurrent callbacks.
References
- Microsoft: resource DLL isolation in Resource Monitor
- Microsoft: resource DLL entry points
- Microsoft: recommended resource DLL practices
Looking for a different code? Search another status or error code.