| Previous | Next |
| ERROR_DEPENDENCY_NOT_FOUND | ERROR_RESOURCE_NOT_ONLINE |
ERROR_DEPENDENCY_ALREADY_EXISTS
The dependency edge is already persistent configuration
Adding a resource dependency is a configuration operation. MS-CMRP describes dependency changes as operations on a cluster resource, and the relationship becomes part of cluster state. Repeating the same add is therefore different from bringing a resource online twice: the graph already contains the requested edge.
This usually points to non-idempotent provisioning or to two management paths configuring the same clustered role. The existing dependency may be correct, so deleting it merely to make an add command succeed can introduce an availability regression.
What to inspect
- Read the current dependency expression or relationship before changing it.
- Check whether a deployment script, role installer, and administrator are all managing the same resource graph.
- Treat an already-present correct edge as success in automation; change it only when the intended provider is different.
Get-ClusterResource | Get-ClusterResourceDependencyReferences
- Microsoft Open Specifications: Cluster Resources and Groups
- Microsoft: Get-ClusterResourceDependency
- Microsoft: Get-ClusterResourceDependencyReport
Looking for a different code? Search another status or error code.