During the installation of a virtual server on a cluster, the SQL Server setup may appear to stop responding (hang) after completing the Failover Clustering screen. CPU utilization remains at 100 percent, and the Cluster Disk Selection screen never displays.

Back to the top

If one of the available shared disks in the Cluster has the same resource name as its resource group, the setup stops responding while enumerating the available shared disks in the cluster.

Back to the top

To work around this issue, change the name of the disk resource so that it is different from its resource group name. Microsoft recommends that you use the default behavior of including the drive letter in the disk resource name.

For example, use "Disk X:" where X is the drive letter of the disk resource.

Back to the top

Microsoft has confirmed this to be a problem in SQL Server 2000.

Back to the top

The last entry in SQLSTP.log file is:

   Begin Action : DialogShowSdDiskGroups
				

The action DialogShowSdDiskGroup never completes.

This problem can also occur if the resource name for an available shared disk or the resource group name for the available shared disk has the name as the disk itself. If drive X: has a resource name of X:, or its resource group name is X:, the same symptoms will occur.

Back to the top