| Groups | Blog | Home |
sql server clustering : SP3a on new cluster nodes
SQL Server 2000, SP3a. I have two additional nodes that I now want to merge into the cluster. I connected the existing cluster disks to the new servers. I ran SQL2K setup and successfully laid down the binaries. I ran SP3a setup, and received the following error: all cluster disks available to this virtual server are owned by other node(s) I don't understand this error. I have test equipment hooked up to the same SAN (NetApp 920c), and cannot reproduce the error. (The only major difference between the production and test environments is that production connects over FCP, whereas test uses iSCSI.) Any suggestions? Do I need to suspect the fibre channel connections and/or disk interface? Or is it a config problem with respect to SP3a? Thanks in advance. -- Ken Jensen
Below are the log file contents:
14:47:57 Begin Setup 14:47:57 Version on Media: 8.00.761 14:47:57 Mode = Normal 14:47:57 ModeType = NORMAL 14:47:57 Begin: SetupInitialize() 14:47:57 End: SetupInitialize() 14:47:57 Begin: CheckFixedRequirements() 14:47:57 Platform ID: 0xf00000 14:47:57 Version: 5.2.3790 14:47:57 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.186 14:47:57 End: CheckFixedRequirements() 14:47:57 Processor Architecture: x86 (Pentium) 14:47:57 ComputerName: DBMRSVCL1C 14:47:57 User Name: sqlservacct 14:47:57 IsAllAccessAllowed returned: 1 14:47:57 OS Language: 0x409 14:47:57 Begin: SetupInstall() 14:47:57 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ... 14:47:57 CommonFilesDir=C:\Program Files\Common Files 14:47:57 Windows Directory=C:\WINDOWS\ 14:47:57 Program Files=C:\Program Files\ 14:47:57 TEMPDIR=C:\DOCUME~1\SQLSER~1\LOCALS~1\Temp\ 14:47:57 End: SetupInstall() 14:48:00 Begin: ShowDialogs() 14:48:00 Initial Dialog Mask: 0x8300037, Disable Back=0x1 14:48:00 Begin Action ShowDialogsHlpr: 0x1 14:48:00 Begin Action: DialogShowSdWelcome 14:48:01 End Action DialogShowSdWelcome 14:48:01 Dialog 0x1 returned: 1 14:48:01 End Action ShowDialogsHlpr 14:48:01 ShowDialogsGetDialog returned: nCurrent=0x2,index=1 14:48:01 Begin Action ShowDialogsHlpr: 0x2 14:48:01 Begin Action: DialogShowSdMachineName 14:48:06 ShowDlgMachine returned: 1 14:48:09 Name = DBMCRPCL1SQLB, Type = 0x20000008 14:48:10 End Action DialogShowSdMachineName 14:48:10 begin ShowDialogsUpdateMask 14:48:10 nFullMask = 0x8300037, nCurrent = 0x2, nDirection = 1 14:48:10 Updated Dialog Mask: 0xb73c037, Disable Back = 0x1 14:48:10 Dialog 0x2 returned: 1 14:48:10 End Action ShowDialogsHlpr 14:48:10 ShowDialogsGetDialog returned: nCurrent=0x4,index=2 14:48:10 Begin Action ShowDialogsHlpr: 0x4 14:48:10 Begin Action: DialogShowSdInstallMode 14:48:10 ShowDlgInstallMode returned: 1 14:48:10 InstallMode : 0x2 14:48:10 End Action DialogShowSdInstallMode 14:48:10 begin ShowDialogsUpdateMask 14:48:10 nFullMask = 0xb73c037, nCurrent = 0x4, nDirection = 1 14:48:10 Updated Dialog Mask: 0xb034607, Disable Back = 0x1 14:48:10 Dialog 0x4 returned: 1 14:48:10 End Action ShowDialogsHlpr 14:48:10 ShowDialogsGetDialog returned: nCurrent=0x200,index=9 14:48:10 Begin Action ShowDialogsHlpr: 0x200 14:48:10 Begin Action: DialogShowSdInstanceName 14:48:10 Begin Action: ShowDlgInstanceName 14:48:10 SKU is : Enterprise Edition 14:48:10 End Action: ShowDlgInstanceName 14:48:10 ShowDlgInstanceName returned : 0 14:48:10 InstanceName : INST1 14:48:10 End Action DialogShowSdInstanceName 14:48:10 begin ShowDialogsUpdateMask 14:48:10 nFullMask = 0xb034607, nCurrent = 0x200, nDirection = 0 14:48:10 Updated Dialog Mask: 0xb034603, Disable Back = 0x1 14:48:10 Dialog 0x200 returned: 0 14:48:10 End Action ShowDialogsHlpr 14:48:10 ShowDialogsGetDialog returned: nCurrent=0x400,index=10 14:48:10 Begin Action ShowDialogsHlpr: 0x400 14:48:10 Begin Action: DialogShowSdMaintain 14:48:10 ShowDlgMaintainInstall returned : 1 14:48:10 Type : 0xc 14:48:10 CreateSetupTopology(DBMRSVCL1C), Handle : 0x11d4448, returned : 0 14:48:10 CreateSetupTopology returned : 0, Handle : 0x11d4448 14:48:10 Topology Type : 1, Return Value : 0 14:48:10 ST_GetPhysicalNode returned : 0, PNHandle : 0x11d3ea8 14:48:10 PN_EnumerateEx returned : 0 14:48:10 PN_GetSQLStates returned : 0, SqlStates : 0x88028221 14:48:10 PN_GetInstance for INST1 [0x11d3ea8] returned : 0 14:48:10 SQLI_GetPackageId [0x11d5758] returned : 0, PackageId = 0x3 14:48:10 SQLI_GetVersion [0x11d5758] returned : 0, Version = 8.00.194 14:48:10 SQLI_GetSQLStates for INST1 [0x11d5758] returned : 0, SQLStates: 0x420808 14:48:10 SQLI_GetInstallPath [0x11d5758] returned : 0, Path = \\DBMRSVCL1C\C$\Program Files\Microsoft SQL Server\MSSQL$INST1 14:48:10 SQLI_GetDataPath [0x11d5758] returned : 0, DataPath = \\DBMRSVCL1C\L$\Program Files\Microsoft SQL Server\MSSQL$INST1 14:48:10 SQLI_GetVersion [0x11d5758] returned : 0, Version = 8.00.194 14:48:10 SQLI_GetRegKeyRoot [0x11d5758] returned : 0, RegKeyRoot = Software\Microsoft\Microsoft SQL Server\INST1 14:48:10 SQLI_GetPackageName [0x11d5758] returned : 0, szPackage = Enterprise Edition 14:48:10 SQLI_GetPackageId [0x11d5758] returned : 0, PackageId = 0x3 14:48:10 Previous Install Path: \\DBMRSVCL1C\C$\Program Files\Microsoft SQL Server\MSSQL$INST1 14:48:10 Previous Install Data: \\DBMRSVCL1C\L$\Program Files\Microsoft SQL Server\MSSQL$INST1 14:48:10 Previous Install Version: 8.00.194 14:48:10 ReleaseSetupTopology 14:48:10 End Action DialogShowSdMaintain 14:48:10 begin ShowDialogsUpdateMask 14:48:10 nFullMask = 0xb034603, nCurrent = 0x400, nDirection = 1 14:48:10 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1 14:48:10 Dialog 0x400 returned: 1 14:48:10 End Action ShowDialogsHlpr 14:48:10 ShowDialogsGetDialog returned: nCurrent=0x2000,index=13 14:48:10 Begin Action ShowDialogsHlpr: 0x2000 14:48:10 Begin Action: DialogShowSdUpgrade 14:48:10 ShowDlgUpgrade returned : 1 14:48:10 Checking databases on instance 'INST1' 14:48:10 Begin Action: Check for VS Node 14:48:49 All cluster disks available to this virtual server are owned by other node(s). 14:48:54 Setup was unable to verify the state of the server for an upgrade. Verify the server is able to start and that you provided a valid sa password and restart setup. 14:48:54 End Action DialogShowSdUpgrade 14:48:54 End: ShowDialogs() 14:48:54 Action CleanUpInstall: 14:48:54 Installation Failed. [quoted text, click to view] "Uttam Parui[MS]" wrote:
> Hi Ken, > > Can you cut and paste the sqlsp.log ? This will tell us where the setup failed. WE may need to see other files later. But will need to start from here. > > Additional Information > ====================== > Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering > http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd020703/wcdblurb020703.asp > > 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 > >
Hi Ken,
Can you cut and paste the sqlsp.log ? This will tell us where the setup failed. WE may need to see other files later. But will need to start from here. Additional Information ====================== Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd020703/wcdblurb020703.asp 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
Hi Ken,
Try the following and see if it helps: 1) On ALL nodes Make sure that the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo\DSQUERY value to DBNETLIB. Make sure that the registry key, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem \NtfsDisable8dot3NameCreation , is set to 0. Make sure that the TEMP or the TMP environment variables do not have spaces. 2) Reboot all nodes 3) Open Cluster Admin and make sure that the node where you will be runing the service setup own all the resources in the SQL group. 4) Run SP3a setup on the node that owns all the resources in the SQL Server group. If setup succeeds, let us know :) 5) If the setup fails a) cut and paste the sqlsp.log. b) Open a command prompt and type cluster res Cut and paste the results. 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
I verified the registry keys on all nodes- everything was set as you
specified. The TEMP and TMP variables did have a space in them. I changed the values and attempted to install SP3a. That failed. It is worth noting the my test env. also has spaces in the variables, but the install worked there. Unfortunately, this is a production (24x7) system, so I will need to acquire a maintenance window to reboot. My question is: is there an underlying configuration problem? I shouldn't have to move the resources to the node I want to service pack. By following your suggestions (and the install succeeding), will we be able to detemine anything, or will I just be happy that it worked? Thanks for the help. Ken [quoted text, click to view] "Uttam Parui[MS]" wrote:
> Hi Ken, > > Try the following and see if it helps: > > 1) On ALL nodes > Make sure that the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo\DSQUERY value to DBNETLIB. > Make sure that the registry key, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem \NtfsDisable8dot3NameCreation , is set to 0. > Make sure that the TEMP or the TMP environment variables do not have spaces. > > 2) Reboot all nodes > 3) Open Cluster Admin and make sure that the node where you will be runing the service setup own all the resources in the SQL group. > 4) Run SP3a setup on the node that owns all the resources in the SQL Server group. > > If setup succeeds, let us know :) > > 5) If the setup fails > a) cut and paste the sqlsp.log. > b) Open a command prompt and type > cluster res > Cut and paste the results. > > 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 > >
Ken,
As such one does not have to move the SQL Server resources to the new node where you want to install SQL SP. If you want to troubleshoot and find the root cause you may want to open a case with Microsoft PSS. 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
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |