Microsoft KB Archive/293788

= BUG: The installation of a SQL Server virtual server stops responding (hangs) if the disk name and the group name are the same =

Article ID: 293788

Article Last Modified on 4/6/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Enterprise Edition

-



This article was previously published under Q293788



BUG #: 352628 (SHILOH)



SYMPTOMS
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.



CAUSE
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.



WORKAROUND
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 &quot;Disk X:&quot; where X is the drive letter of the disk resource.



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



MORE INFORMATION
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.

Additional query words: lock failover clustering install

Keywords: kbtshoot kbbug kbpending KB293788

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.