Article ID: 4007, created on Mar 17, 2008, last review on Apr 28, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.0


When you add nodes to a cluster, The Setup Wizard may stop working during the Analyze phase. When this occurs, the following error message is generated:

Date: 10/23/2002
Time: 9:51:50 AM
Computer: NODENAME
Major Task ID: {B8C4066E-0246-4358-9DE5-25603EDD0CA0}
Minor Task ID: {3BB53C9E-E14A-4196-9066-5400FB8860C9}
Progress (min, max, current): 0, 1, 1
Checking that all nodes have access to the quorum resource
Status: 0x800713de
The quorum disk could not be located by the cluster service.
Additional Information:
For more information, visit Help and Support Services at

This occurs only while you are adding nodes to an existing cluster.


This behavior is caused by an interaction between two technologies: the new Cluster Setup Wizard and the storage area network (SAN) configuration. The new Cluster Setup Wizard contains heuristics to verify that all cluster nodes have access to the same disks. The wizard does this by determining whether all cluster nodes recognize the disks with the same target ID (TID) and logical unit number (LUN). Typically, in a correctly configured cluster shared-disk array, this is the case. However, with a complex SAN configuration, this may not be true.

With a complex SAN environment, the same set of disks may be detected on different LUNs and TIDs by individual nodes, but this can still be a valid cluster configuration. Therefore, the disk-detection heuristics may incorrectly detect that the disk configuration is not valid for Setup.


To work around this issue, click Advanced when you are prompted for the nodes to add to the cluster, and then click Advanced (minimum) configuration. The Advanced option excludes the detection that is described earlier in this article from the Analyze process, and permits the cluster installation to continue. However, if there are disk-configuration issues, the cluster may experience issues with bringing the disks online or with disk failover.


Please see original Microsoft article here

28d0f7cc091e3b9304fa556c03f9a940 965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF