Groups | Blog | Home
all groups > sql server clustering > september 2004 >

sql server clustering : SQL 2000 Install Hangs


Jim
9/27/2004 9:41:08 AM
We have a 4 node Windows 2003 cluster with 3 Instances of
SQL Server 2000 already installed. I am trying to
install a 4th node on the cluster and the install fails
right after I enter the Virtual IP for the 4th Instance.
I'm using all the same settings as the first 3
Instances. Any suggestions would be greatly appreciated.

NT Event Application Log:
Hanging application _INS5576._MP, version 5.53.168.0,
hang module comctl32.dll, version 5.82.3790.0, hang
address 0x00057f63.

The sqlstp.log:
10:32:18 Begin Setup
10:32:18 8.00.194
10:32:18 Mode = Normal
10:32:18 ModeType = NORMAL
10:32:20 GetDefinitionEx returned: 0, Extended: 0x0
10:32:20 ValueFTS returned: 1
10:32:20 ValuePID returned: 1
10:32:20 ValueLic returned: 1
10:32:20 System: Windows NT Enterprise Server
10:32:20 SQL Server ProductType: Enterprise Edition [0x3]
10:32:20 IsNTCluster returned: 1
10:32:20 Begin Action: SetupInitialize
10:32:20 End Action SetupInitialize
10:32:20 Begin Action: SetupInstall
10:32:20 Reading
Software\Microsoft\Windows\CurrentVersion\CommonFilesDir .
...
10:32:20 CommonFilesDir=C:\Program Files\Common Files
10:32:20 Windows Directory=C:\WINDOWS\
10:32:20 Program Files=C:\Program Files\
10:32:20 TEMPDIR=C:\WINDOWS\TEMP\
10:32:20 Begin Action: SetupInstall
10:32:20 digpid size : 256
10:32:21 digpid size : 164
10:32:21 Begin Action: CheckFixedRequirements
10:32:21 Platform ID: 0xf00000
10:32:21 Version: 5.2.3790
10:32:21 File Version - C:\WINDOWS\system32\shdocvw.dll:
6.0.3790.186
10:32:21 End Action: CheckFixedRequirements
10:32:29 Begin Action: ShowDialogs
10:32:29 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
10:32:30 Begin Action ShowDialogsHlpr: 0x1
10:32:30 Begin Action: DialogShowSdWelcome
10:32:47 End Action DialogShowSdWelcome
10:32:47 Dialog 0x1 returned: 1
10:32:47 End Action ShowDialogsHlpr
10:32:47 ShowDialogsGetDialog returned:
nCurrent=0x2,index=1
10:32:47 Begin Action ShowDialogsHlpr: 0x2
10:32:47 Begin Action: DialogShowSdMachineName
10:33:03 ShowDlgMachine returned: 1
10:33:03 Name = NTSQLSHARE, Type = 0x10000008
10:33:04 Begin Action: CheckRequirements
10:33:04 Processor Architecture: x86 (Pentium)
10:33:04 ComputerName: NTSQLPRD1
10:33:04 User Name: sqldba
10:33:04 IsAllAccessAllowed returned: 1
10:33:04 OS Language: 0x409
10:33:04 End Action CheckRequirements
10:33:04 This combination of Package and Operating System
allows a full product install.
10:33:05 End Action DialogShowSdMachineName
10:33:05 begin ShowDialogsUpdateMask
10:33:05 nFullMask = 0x183000f7, nCurrent = 0x2,
nDirection = 0
10:33:05 Updated Dialog Mask: 0xbf3c037, Disable Back =
0x1
10:33:05 Dialog 0x2 returned: 0
10:33:05 End Action ShowDialogsHlpr
10:33:05 ShowDialogsGetDialog returned:
nCurrent=0x4,index=2
10:33:05 Begin Action ShowDialogsHlpr: 0x4
10:33:05 Begin Action: DialogShowSdInstallMode
10:33:05 InstallMode : 0x1
10:33:05 End Action DialogShowSdInstallMode
10:33:05 begin ShowDialogsUpdateMask
10:33:05 nFullMask = 0xbf3c037, nCurrent = 0x4,
nDirection = 1
10:33:05 Updated Dialog Mask: 0x1bf7c037, Disable Back =
0x1
10:33:05 Dialog 0x4 returned: 1
10:33:05 End Action ShowDialogsHlpr
10:33:05 ShowDialogsGetDialog returned:
nCurrent=0x10,index=4
10:33:05 Begin Action ShowDialogsHlpr: 0x10
10:33:05 Begin Action: DialogShowSdRegisterUserEx
10:33:09 End Action DialogShowSdRegisterUserEx
10:33:09 begin ShowDialogsUpdateMask
10:33:09 nFullMask = 0x1bf7c037, nCurrent = 0x10,
nDirection = 1
10:33:09 Updated Dialog Mask: 0x1bf7c037, Disable Back =
0x1
10:33:09 Dialog 0x10 returned: 1
10:33:09 End Action ShowDialogsHlpr
10:33:09 ShowDialogsGetDialog returned:
nCurrent=0x20,index=5
10:33:09 Begin Action ShowDialogsHlpr: 0x20
10:33:09 Begin Action: DialogShowSdLicense
10:33:16 End Action DialogShowSdLicense
10:33:16 Dialog 0x20 returned: 1
10:33:16 End Action ShowDialogsHlpr
10:33:16 ShowDialogsGetDialog returned:
nCurrent=0x4000,index=14
10:33:16 Begin Action ShowDialogsHlpr: 0x4000
10:33:16 Begin Action: DialogShowSdVirtualServer
10:33:51 ShowDlgVirtualServer returned: 0
10:33:51 Ipaddress = 192.168.197.64,255.255.255.0,Front
Office
10:33:51 szNewList = 192.168.197.64,255.255.255.0,Front
Office
10:33:51 szModifiedList =
10:33:51 szRemovedList =
10:33:51 End Action DialogShowSdVirtualServer
10:33:51 begin ShowDialogsUpdateMask
10:33:51 nFullMask = 0x1bf7c037, nCurrent = 0x4000,
nDirection = 1
10:33:51 Updated Dialog Mask: 0x1bf7c037, Disable Back =
0x1
10:33:51 Dialog 0x4000 returned: 1
10:33:51 End Action ShowDialogsHlpr
10:33:51 ShowDialogsGetDialog returned:
nCurrent=0x8000,index=15
10:33:51 Begin Action ShowDialogsHlpr: 0x8000
10:33:51 Begin Action : DialogShowSdDiskGroups
Hilary Cotter
9/28/2004 8:32:16 AM
go to task manager, click on the processess tab, right click on setup.exe
and select set priority. Then give it high or real time priority. Watch cpu
utilization and memory consumption to see if this boost doesn't get over the
hang.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html


[quoted text, click to view]

Jim
9/29/2004 11:21:04 AM
That didn't help. I don't get setup in task manager. I
do get Setupsql and _INS5576._MP and I boosted their
priority. The server never went above 10% in processor
and minimal memory was ever consummed.

[quoted text, click to view]
uttamkp NO[at]SPAM online.microsoft.com
9/30/2004 2:00:04 AM
Hi Jim,

The last entry in the sqlstp.log that you pasted is

10:33:51 Begin Action : DialogShowSdDiskGroups

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

If this is the case then 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.

OR
====
If you have any disks in the system that do not have drive letters, such as drives that are mount points, or preparing to do so, it may cause this problem.
Why ? On a clustered instance of SQL Server 2000, data storage on mounted drives is not supported. The installation of SQL Server 2000 is not supported on a clustered configuration that has mounted drives even if
the mounted drives are not intended to be used with SQL Server.For more information, refer to
SQL Server 2000 support for mounted volumes
http://support.microsoft.com/?id=819546

HTH,

Best Regards,

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Jim
10/6/2004 11:33:27 AM
It actually turns out an issue found in:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;815431&Product=sql2k

This fixed the problem.
Jim

[quoted text, click to view]
the same resource name as its resource group? If yes then
the setup stops responding while enumerating the
available shared disks in the cluster.
[quoted text, click to view]
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
[quoted text, click to view]
drive letters, such as drives that are mount points, or
preparing to do so, it may cause this problem.
[quoted text, click to view]
storage on mounted drives is not supported. The
installation of SQL Server 2000 is not supported on a
clustered configuration that has mounted drives even if
[quoted text, click to view]
Technology Protection Program and to order your FREE
Security Tool Kit, please visit
http://www.microsoft.com/security.
[quoted text, click to view]
access update their Microsoft software to better protect
against viruses and security vulnerabilities. The easiest
way to do this is to visit the following websites:
[quoted text, click to view]
AddThis Social Bookmark Button