The cluster resource could not be created in the specified resource monitor.
The cluster resource could not be brought online by the resource monitor.
The operation could not be completed because the cluster resource is online.
The cluster resource could not be deleted or brought offline because it is the quorum resource.
The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.
The cluster software is shutting down.
The group or resource is not in the correct state to perform the requested operation.
The properties were stored but not all changes will take effect until the next time the resource is brought online.
The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.
The cluster resource could not be deleted because it is a core resource.
The quorum resource failed to come online.
The quorum log could not be created or mounted successfully.
The cluster log is corrupt.
The record could not be written to the cluster log because it exceeds the maximum size.
The cluster log exceeds its maximum size.
No checkpoint record was found in the cluster log.
The minimum required disk space needed for logging is not available.
The cluster node failed to take control of the quorum resource because the resource is owned by another active node.
A cluster network is not available for this operation.
A cluster node is not available for this operation.
All cluster nodes must be running to perform this operation.
A cluster resource failed.
The cluster node is not valid.
The cluster node already exists.
A node is in the process of joining the cluster.
The cluster node was not found.
The cluster local node information was not found.
The cluster network already exists.
The cluster network was not found.
The cluster network interface already exists.
The cluster network interface was not found.
The cluster request is not valid for this object.
The cluster network provider is not valid.
The cluster node is down.
The cluster node is not reachable.
The cluster node is not a member of the cluster.
A cluster join operation is not in progress.
The cluster network is not valid.
The cluster node is up.
The cluster IP address is already in use.
The cluster node is not paused.
No cluster security context is available.
The cluster network is not configured for internal cluster communication.
The cluster node is already up.
The cluster node is already down.
The cluster network is already online.
The cluster network is already offline.
The cluster node is already a member of the cluster.
The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.
One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
This operation cannot be performed on the cluster resource because it is the quorum resource. You may not bring the quorum resource offline or modify its possible owners list.
The cluster quorum resource is not allowed to have any dependencies.
The cluster node is paused.
The cluster resource cannot be brought online. The owner node cannot run this resource.
The cluster node is not ready to perform the requested operation.
The cluster node is shutting down.
The cluster join operation was aborted.
The cluster join operation failed due to incompatible software versions between the joining node and its sponsor.
This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.
The system configuration changed during the cluster join or form operation. The join or form operation was aborted.
The specified resource type was not found.
The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.
No authentication package could be registered with the RPC server.
You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.
The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.
The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.
A non-locker code received a request to reserve the lock for making global updates.
The quorum disk could not be located by the cluster service.
The backed-up cluster database is possibly corrupt.
A DFS root already exists in this cluster node.
An attempt to modify a resource property failed because it conflicts with another existing property.
An operation was attempted that is incompatible with the current membership state of the node.
The quorum resource does not contain the quorum log.
The membership engine requested shutdown of the cluster service on this node.
The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.
A matching cluster network for the specified IP address could not be found.
The actual data type of the property did not match the expected data type of the property.