Node '%1' successfully became part of a failover cluster and detected that its cluster service software has been updated.
Node '%1' failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource ...
Node '%1' failed to form a failover cluster. This was due to one or more nodes executing incompatible versions of the cluster ...
Node '%1' failed to join the cluster because it could not send and receive failure detection network messages with other ...
Node '%1' formed a failover cluster without performing a version compatibility check because version compatibility checking ...
Node '%1' successfully became part of a failover cluster and detected that its cluster service software has been updated. ...
Node {0} is not reachable from node {1}. It is necessary that each cluster node can communicate each other cluster node by ...
Node {0} is reachable from Node {1} by multiple communication paths, but each path includes network interface {2}. This network ...
Node {0} is reachable from Node {1} by only one pair of interfaces. It is possible that this network path is a single point ...
Non-HTTP Activation supports process activation via Message Queuing, TCP and named pipes. Applications that use Non-HTTP ...