Node '{0}' could not be initialized for validation testing. Possible causes for this are that another validation test is being run from another management client, or a previous validation test was unexpectedly terminated. If a previous validation test was unexpectedly terminated, the best corrective action is to restart the node and try again.
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}' could not be initialized for validation testing. Possible causes for this are that another validation test is ...
Node '{0}' is missing a memory resource pool '{1}' that is present on at least one other node. Either remove the resource ...
Node '{0}' is missing a network resource pool '{1}' that is present on at least one other node. Either remove the resource ...
Node '{0}' is missing a processor resource pool '{1}' that is present on at least one other node. Either remove the resource ...
Node '{0}' is missing a resource pool of virtual hard disks for Hyper-V called '{1}' that is present on at least one other ...