What does Windows error code 5001 (ERROR_DEPENDENT_RESOURCE_EXISTS) mean?

ERROR_DEPENDENT_RESOURCE_EXISTS

The dependency graph still references the resource

Failover Clustering models startup ordering and availability through resource dependencies. A provider resource is brought online before a dependent resource, and taking the provider away can make the dependent role unusable. This status therefore protects the cluster configuration from deleting a resource that is still an input to another resource.

The useful question is not whether the target resource is currently online. A dependency is persistent cluster configuration, so the reference can remain even when both resources are offline. Enumerate the dependency graph and identify the consumer before removing or replacing the provider.

What to inspect

• Use Get-ClusterResourceDependency on resources in the same clustered role and generate a dependency report when the graph is not obvious.
• If the resource is being replaced, add and validate the new provider first, then change the dependency and only then remove the old object.
• Do not force deletion by editing cluster registry data; that bypasses graph validation and can leave a role that cannot start in the documented order.

Get-ClusterResource | Get-ClusterResourceDependency
Get-ClusterResourceDependencyReport

References

• Microsoft Open Specifications: Cluster Resources and Groups
• Microsoft: Get-ClusterResourceDependency
• Microsoft: Get-ClusterResourceDependencyReport