| Groups | Blog | Home |
sql server clustering : Setup Failed to Perform Req'd operations on CLuster Nodes
Please post the entire SQLStop log files from both nodes.
By NetBIOS disabled, do you mean you removed File and Print sharing and/or Windows Client network tools. If so, then you cannot build a SQL cluster. SQL Installer relies on this functionality to copy installation files to remote nodes. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message news:09FAE2F0-01CC-4CC0-852D-D31C3A0C6810@microsoft.com... > SQL 2000 Ent. on 2003 sp1 Cluster. > > -Installation & Service accounts are both domain admins > -NetBIOS disabled on NICs > -CLuster service & failover running properly > -Cluster resource names contain no spaces > -User PATH for TEMP and TMP set to c:\temp > -AVScanner Services stopped > -Licensing Mode = Per Processor (4) > > Cluster Machines reside in own OU > > SQLstp.log files on Node1 and on Node2 both indicate "Installation > Successful" > > 14:28:04 End Action LogSelectedComponents > 14:28:05 SQL program folder: C:\Program Files\Microsoft SQL Server\MSSQL > 14:28:05 SQL data folder: R:\Program Files\Microsoft SQL Server\MSSQL > 14:28:05 Windows system folder: C:\WINDOWS\system32\ > 14:28:05 Prog req: 38205, Data req: 34432, Sys req: 96876 > 14:28:05 Prog avail: 30955000, Data avail: 716796800, Sys avail: 30955000 > 14:28:05 Prog req vs. avail, 135081, 30955000 > 14:28:05 Data req vs. avail, 34432, 716796800 > 14:28:05 Sys req vs. avail, 96876, 30955000 > 14:28:05 DisplaySystemPreReq > 14:28:05 Begin Action InstallPkgs: > 14:28:05 Begin Action: Locked Connectivity Files Check > 14:28:06 ConnectivityLocked returned: 0 > 14:28:06 The operation completed successfully. > > But then hang for approx 20 mins on > > > 14:28:06 End Action: Locked Connectivity Files Check > 14:28:06 Setup is installing Microsoft Data Access Components (MDAC) ... > 14:28:06 D:\ENGLISH\ENT\x86\Other\sqlredis.exe /q:a > 14:28:49 ExitCode: 0 > 14:28:49 InstallMSSearch instance: MSSQLSERVER > 14:28:49 Software\Microsoft\Search\Install:Version not present > 14:28:49 MSSearch 2.0 or greater version check returned -1 > 14:28:49 Setup is installing the Microsoft Full-Text Search Engine ... > 14:28:49 "D:\ENGLISH\ENT\x86\FullText\MSSearch\Search\SearchStp.exe" /s > /a:SQLServer > > > End abruptly end with > > "Setup Failed to Perform Required Operations on the Cluster Nodes" > > 2 Nodes. > > Have tried installing only to the local node -- Same Result > > No indication of "Installation Failed" or "exit code was (2)" as in MSKB > 321063 > > After above error popup, cannot re-run cd:\ENGLISH\ENT\AUTORUN.EXE until > server is restarted, and will only do so from "shutdown /i" > > Please Advise. > >
SQL 2000 Ent. on 2003 sp1 Cluster.
-Installation & Service accounts are both domain admins -NetBIOS disabled on NICs -CLuster service & failover running properly -Cluster resource names contain no spaces -User PATH for TEMP and TMP set to c:\temp -AVScanner Services stopped -Licensing Mode = Per Processor (4) Cluster Machines reside in own OU SQLstp.log files on Node1 and on Node2 both indicate "Installation Successful" 14:28:04 End Action LogSelectedComponents 14:28:05 SQL program folder: C:\Program Files\Microsoft SQL Server\MSSQL 14:28:05 SQL data folder: R:\Program Files\Microsoft SQL Server\MSSQL 14:28:05 Windows system folder: C:\WINDOWS\system32\ 14:28:05 Prog req: 38205, Data req: 34432, Sys req: 96876 14:28:05 Prog avail: 30955000, Data avail: 716796800, Sys avail: 30955000 14:28:05 Prog req vs. avail, 135081, 30955000 14:28:05 Data req vs. avail, 34432, 716796800 14:28:05 Sys req vs. avail, 96876, 30955000 14:28:05 DisplaySystemPreReq 14:28:05 Begin Action InstallPkgs: 14:28:05 Begin Action: Locked Connectivity Files Check 14:28:06 ConnectivityLocked returned: 0 14:28:06 The operation completed successfully. But then hang for approx 20 mins on 14:28:06 End Action: Locked Connectivity Files Check 14:28:06 Setup is installing Microsoft Data Access Components (MDAC) ... 14:28:06 D:\ENGLISH\ENT\x86\Other\sqlredis.exe /q:a 14:28:49 ExitCode: 0 14:28:49 InstallMSSearch instance: MSSQLSERVER 14:28:49 Software\Microsoft\Search\Install:Version not present 14:28:49 MSSearch 2.0 or greater version check returned -1 14:28:49 Setup is installing the Microsoft Full-Text Search Engine ... 14:28:49 "D:\ENGLISH\ENT\x86\FullText\MSSearch\Search\SearchStp.exe" /s /a:SQLServer End abruptly end with "Setup Failed to Perform Required Operations on the Cluster Nodes" 2 Nodes. Have tried installing only to the local node -- Same Result No indication of "Installation Failed" or "exit code was (2)" as in MSKB 321063 After above error popup, cannot re-run cd:\ENGLISH\ENT\AUTORUN.EXE until server is restarted, and will only do so from "shutdown /i" Please Advise.
NetBIOS disabled by
Control panel - network connections - public NIC - TCP/IP Properties - advanced - WINS - DISABLE NetBIOS over TCP/IP Note: this installation run as PER SEAT(4) rather than per Processor(4) as was suggested elsewhere SQLStop from Root Node of installation: 14:27:58 Begin Setup 14:27:58 8.00.194 14:27:58 Mode = Silent 14:27:58 ModeType = CLUSTER 14:27:58 Cluster node. 14:27:58 g_szIssPath=C:\WINDOWS\setup~0.iss 14:27:58 GetDefinitionEx returned: 0, Extended: 0x0 14:27:58 ValueFTS returned: 1 14:27:58 ValuePID returned: 1 14:27:58 ValueLic returned: 1 14:27:58 System: Windows NT Enterprise Server 14:27:58 SQL Server ProductType: Enterprise Edition [0x3] 14:27:58 IsNTCluster returned: 1 14:27:58 Begin Action: SetupInitialize 14:27:58 End Action SetupInitialize 14:27:58 Begin Action: SetupInstall 14:27:58 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ... 14:27:58 CommonFilesDir=C:\Program Files\Common Files 14:27:58 Windows Directory=C:\WINDOWS\ 14:27:58 Program Files=C:\Program Files\ 14:27:58 TEMPDIR=c:\Temp\ 14:27:58 Begin Action: SetupInstall 14:27:58 digpid size : 256 14:27:58 digpid size : 164 14:27:58 Begin Action: CheckFixedRequirements 14:27:58 Platform ID: 0xf00000 14:27:58 Version: 5.2.3790 14:27:58 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2440 14:27:58 End Action: CheckFixedRequirements 14:27:58 Begin Action: ShowDialogs 14:27:58 Initial Dialog Mask: 0x183000f7, Disable Back=0x1 14:27:58 Begin Action ShowDialogsHlpr: 0x1 14:27:58 Begin Action: DialogShowSdWelcome 14:27:58 End Action DialogShowSdWelcome 14:27:58 Dialog 0x1 returned: 1 14:27:58 End Action ShowDialogsHlpr 14:27:58 ShowDialogsGetDialog returned: nCurrent=0x2,index=1 14:27:58 Begin Action ShowDialogsHlpr: 0x2 14:27:58 Begin Action: DialogShowSdMachineName 14:27:58 [DlgMachine] 14:27:58 Result = 1 14:27:58 Type = 268435466 14:27:58 Name = FCIADB1 14:27:58 ShowDlgMachine returned: 1 14:27:58 Name = FCIADB1, Type = 0x1000000a 14:27:58 Begin Action: CheckRequirements 14:27:58 Processor Architecture: x86 (Pentium) 14:27:58 Service Pack: 256 14:27:58 ComputerName: FCIADB1 14:27:58 User Name: kmcdermott 14:27:58 IsAllAccessAllowed returned: 1 14:27:58 OS Language: 0x409 14:27:58 End Action CheckRequirements 14:27:58 This combination of Package and Operating System allows a full product install. 14:27:58 End Action DialogShowSdMachineName 14:27:58 begin ShowDialogsUpdateMask 14:27:58 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0 14:27:58 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1 14:27:58 Dialog 0x2 returned: 0 14:27:58 End Action ShowDialogsHlpr 14:27:58 ShowDialogsGetDialog returned: nCurrent=0x4,index=2 14:27:58 Begin Action ShowDialogsHlpr: 0x4 14:27:58 Begin Action: DialogShowSdInstallMode 14:27:58 [DlgInstallMode] 14:27:58 Result = 1 14:27:59 Type = 1 14:27:59 InstallMode : 0x1 14:27:59 End Action DialogShowSdInstallMode 14:27:59 begin ShowDialogsUpdateMask 14:27:59 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1 14:27:59 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 14:27:59 Dialog 0x4 returned: 1 14:27:59 End Action ShowDialogsHlpr 14:27:59 ShowDialogsGetDialog returned: nCurrent=0x10,index=4 14:27:59 Begin Action ShowDialogsHlpr: 0x10 14:27:59 Begin Action: DialogShowSdRegisterUserEx 14:27:59 End Action DialogShowSdRegisterUserEx 14:27:59 begin ShowDialogsUpdateMask 14:27:59 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1 14:27:59 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 14:27:59 Dialog 0x10 returned: 1 14:27:59 End Action ShowDialogsHlpr 14:27:59 ShowDialogsGetDialog returned: nCurrent=0x20,index=5 14:27:59 Begin Action ShowDialogsHlpr: 0x20 14:27:59 Begin Action: DialogShowSdLicense 14:27:59 End Action DialogShowSdLicense 14:27:59 Dialog 0x20 returned: 1 14:27:59 End Action ShowDialogsHlpr 14:27:59 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14 14:27:59 Begin Action ShowDialogsHlpr: 0x4000 14:27:59 Begin Action: DialogShowSdVirtualServer 14:27:59 [DlgVirtServer] 14:27:59 Result = 1 14:27:59 VirtServerName = FCSQLIA 14:27:59 IpAddresses = 192.86.226.148,255.255.255.0,Public 14:28:02 ShowDlgVirtualServer returned: 0 14:28:02 Ipaddress = 192.86.226.148,255.255.255.0,Public 14:28:02 szNewList = 192.86.226.148,255.255.255.0,Public 14:28:02 szModifiedList = 14:28:02 szRemovedList = 14:28:02 End Action DialogShowSdVirtualServer 14:28:02 begin ShowDialogsUpdateMask 14:28:02 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1 14:28:02 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 14:28:02 Dialog 0x4000 returned: 1 14:28:02 End Action ShowDialogsHlpr 14:28:02 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15 14:28:02 Begin Action ShowDialogsHlpr: 0x8000 14:28:02 Begin Action : DialogShowSdDiskGroups 14:28:02 [DlgDiskGroups] 14:28:02 Result = 1 14:28:02 DiskGroupsName = Group0 14:28:02 ShowDlgDiskGroups returned: 1 14:28:02 Disk Group = Group0 14:28:02 End Action : DialogShowSdDiskGroups 14:28:02 begin ShowDialogsUpdateMask 14:28:02 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1 14:28:02 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 14:28:02 Dialog 0x8000 returned: 1 14:28:02 End Action ShowDialogsHlpr 14:28:02 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16 14:28:02 Begin Action ShowDialogsHlpr: 0x10000 14:28:02 Begin Action: DialogShowSdClusterDef 14:28:02 [DlgClusterDef] 14:28:02 Result = 1 14:28:02 nNumNodes = 2 14:28:02 VirtServerName = FCSQLIA 14:28:02 szPrefowners = FCIADB1,FCIADB2 14:28:02 ShowDlgClusterDef returned: 1 14:28:02 PrefOwners = FCIADB1,FCIADB2, NumIp = 0 14:28:02 End Action DialogShowSdClusterDef 14:28:02 begin ShowDialogsUpdateMask 14:28:02 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1 14:28:02 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 14:28:02 Dialog 0x10000 returned: 1 14:28:02 End Action ShowDialogsHlpr 14:28:02 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17 14:28:02 Begin Action ShowDialogsHlpr: 0x20000 14:28:02 Begin Action : Cluster Security - DlgAcct 14:28:02 [DlgAccount] 14:28:02 Result = 1 14:28:02 Domain = FC-IA 14:28:02 DomainAcct = kmcdermott 14:28:02 DomainPwd 14:28:02 ValidateUser returned: 1, 0, 0x1b0 14:28:02 IsAcctValidForCluster returned: 1, 0 14:28:02 End Action : Cluster Security - DlgAcct 14:28:02 begin ShowDialogsUpdateMask 14:28:02 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1 14:28:02 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 14:28:02 Dialog 0x20000 returned: 1 14:28:02 End Action ShowDialogsHlpr 14:28:02 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18 14:28:02 Begin Action ShowDialogsHlpr: 0x40000 14:28:02 Begin Action: DialogShowSdCliSvr 14:28:02 DisplaySystemPreReq 14:28:02 [DlgClientServer] 14:28:02 Result = 1 14:28:02 Type = 2
SQLStop from Node2: 13:19:38 Begin Setup 13:19:38 8.00.194 13:19:38 Mode = Silent 13:19:38 ModeType = CLUSTER 13:19:38 Cluster node. 13:19:38 Cluster secondary node. 13:19:38 Cluster secondary node. 13:19:39 g_szIssPath=C:\WINDOWS\setup~0.iss 13:19:39 GetDefinitionEx returned: 0, Extended: 0x0 13:19:39 ValueFTS returned: 1 13:19:39 ValuePID returned: 1 13:19:39 ValueLic returned: 1 13:19:39 System: Windows NT Enterprise Server 13:19:39 SQL Server ProductType: Enterprise Edition [0x3] 13:19:39 IsNTCluster returned: 1 13:19:39 Begin Action: SetupInitialize 13:19:39 End Action SetupInitialize 13:19:39 Begin Action: SetupInstall 13:19:39 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ... 13:19:39 CommonFilesDir=C:\Program Files\Common Files 13:19:39 Windows Directory=C:\WINDOWS\ 13:19:39 Program Files=C:\Program Files\ 13:19:39 TEMPDIR=C:\DOCUME~1\TRANSA~1\LOCALS~1\Temp\ 13:19:39 Begin Action: SetupInstall 13:19:39 digpid size : 256 13:19:39 digpid size : 164 13:19:39 Begin Action: CheckFixedRequirements 13:19:39 Platform ID: 0xf00000 13:19:39 Version: 5.2.3790 13:19:39 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2440 13:19:39 End Action: CheckFixedRequirements 13:19:40 Begin Action: ShowDialogs 13:19:40 Initial Dialog Mask: 0x183000f7, Disable Back=0x1 13:19:40 Begin Action ShowDialogsHlpr: 0x1 13:19:40 Begin Action: DialogShowSdWelcome 13:19:40 End Action DialogShowSdWelcome 13:19:40 Dialog 0x1 returned: 1 13:19:40 End Action ShowDialogsHlpr 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x2,index=1 13:19:40 Begin Action ShowDialogsHlpr: 0x2 13:19:40 Begin Action: DialogShowSdMachineName 13:19:40 [DlgMachine] 13:19:40 Result = 1 13:19:40 Type = 268435466 13:19:40 Name = FCIADB2 13:19:40 ShowDlgMachine returned: 1 13:19:40 Name = FCIADB2, Type = 0x1000000a 13:19:40 Begin Action: CheckRequirements 13:19:40 Processor Architecture: x86 (Pentium) 13:19:40 Service Pack: 256 13:19:40 ComputerName: FCIADB2 13:19:40 User Name: transactioncluster 13:19:40 IsAllAccessAllowed returned: 1 13:19:40 OS Language: 0x409 13:19:40 End Action CheckRequirements 13:19:40 This combination of Package and Operating System allows a full product install. 13:19:40 End Action DialogShowSdMachineName 13:19:40 begin ShowDialogsUpdateMask 13:19:40 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0 13:19:40 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1 13:19:40 Dialog 0x2 returned: 0 13:19:40 End Action ShowDialogsHlpr 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x4,index=2 13:19:40 Begin Action ShowDialogsHlpr: 0x4 13:19:40 Begin Action: DialogShowSdInstallMode 13:19:40 [DlgInstallMode] 13:19:40 Result = 1 13:19:40 Type = 1 13:19:40 InstallMode : 0x1 13:19:40 End Action DialogShowSdInstallMode 13:19:40 begin ShowDialogsUpdateMask 13:19:40 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1 13:19:40 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 13:19:40 Dialog 0x4 returned: 1 13:19:40 End Action ShowDialogsHlpr 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x10,index=4 13:19:40 Begin Action ShowDialogsHlpr: 0x10 13:19:40 Begin Action: DialogShowSdRegisterUserEx 13:19:40 End Action DialogShowSdRegisterUserEx 13:19:40 begin ShowDialogsUpdateMask 13:19:40 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1 13:19:40 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 13:19:40 Dialog 0x10 returned: 1 13:19:40 End Action ShowDialogsHlpr 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x20,index=5 13:19:40 Begin Action ShowDialogsHlpr: 0x20 13:19:40 Begin Action: DialogShowSdLicense 13:19:40 End Action DialogShowSdLicense 13:19:40 Dialog 0x20 returned: 1 13:19:40 End Action ShowDialogsHlpr 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14 13:19:40 Begin Action ShowDialogsHlpr: 0x4000 13:19:40 Begin Action: DialogShowSdVirtualServer 13:19:40 [DlgVirtServer] 13:19:40 Result = 1 13:19:40 VirtServerName = FCSQLIA 13:19:40 IpAddresses = 192.86.226.148,255.255.255.0,Public 13:19:44 ShowDlgVirtualServer returned: 0 13:19:44 Ipaddress = 192.86.226.148,255.255.255.0,Public 13:19:44 szNewList = 192.86.226.148,255.255.255.0,Public 13:19:44 szModifiedList = 13:19:44 szRemovedList = 13:19:44 End Action DialogShowSdVirtualServer 13:19:44 begin ShowDialogsUpdateMask 13:19:44 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1 13:19:44 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 13:19:44 Dialog 0x4000 returned: 1 13:19:44 End Action ShowDialogsHlpr 13:19:44 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15 13:19:44 Begin Action ShowDialogsHlpr: 0x8000 13:19:44 Begin Action : DialogShowSdDiskGroups 13:19:44 [DlgDiskGroups] 13:19:44 Result = 1 13:19:44 DiskGroupsName = Group 0 13:19:44 ShowDlgDiskGroups returned: 1 13:19:44 Disk Group = Group 0 13:19:44 End Action : DialogShowSdDiskGroups 13:19:44 begin ShowDialogsUpdateMask 13:19:44 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1 13:19:44 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 13:19:44 Dialog 0x8000 returned: 1 13:19:44 End Action ShowDialogsHlpr 13:19:44 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16 13:19:44 Begin Action ShowDialogsHlpr: 0x10000 13:19:44 Begin Action: DialogShowSdClusterDef 13:19:44 [DlgClusterDef] 13:19:44 Result = 1 13:19:44 nNumNodes = 2 13:19:44 VirtServerName = FCSQLIA 13:19:44 szPrefowners = FCIADB1,FCIADB2 13:19:44 ShowDlgClusterDef returned: 1 13:19:44 PrefOwners = FCIADB1,FCIADB2, NumIp = 0 13:19:44 End Action DialogShowSdClusterDef 13:19:44 begin ShowDialogsUpdateMask 13:19:44 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1 13:19:44 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 13:19:44 Dialog 0x10000 returned: 1 13:19:44 End Action ShowDialogsHlpr 13:19:44 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17 13:19:44 Begin Action ShowDialogsHlpr: 0x20000 13:19:44 Begin Action : Cluster Security - DlgAcct 13:19:44 [DlgAccount] 13:19:44 Result = 1 13:19:44 Domain = FC-IA 13:19:44 DomainAcct = transactioncluster 13:19:44 DomainPwd 13:19:44 ValidateUser returned: 1, 0, 0x1b0 13:19:44 IsAcctValidForCluster returned: 1, 0 13:19:44 End Action : Cluster Security - DlgAcct 13:19:44 begin ShowDialogsUpdateMask 13:19:44 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1 13:19:44 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 13:19:44 Dialog 0x20000 returned: 1 13:19:44 End Action ShowDialogsHlpr 13:19:44 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18 13:19:44 Begin Action ShowDialogsHlpr: 0x40000 13:19:44 Begin Action: DialogShowSdCliSvr 13:19:44 DisplaySystemPreReq 13:19:44 [DlgClientServer] 13:19:44 Result = 1 13:19:44 Type = 2 13:19:44 ShowDlgClientServerSelect returned: 1 13:19:44 Type : 0x2 13:19:44 End Action DialogShowSdCliSvr 13:19:44 begin ShowDialogsUpdateMask
It is definitely failing on the Search installation. If you don't need
search, disable the install. Here are some things to try. Log in to the remote node under the install account and try to access the \\FCIADB1\D$\ENGLISH\ENT\x86\FullText\MSSearch\Search\SearchStp.exe file. Just try and copy it somewhere. You may find you have a corrupt CD or a permissions issue. Try copying the CD to a local drive on the first node and see if that helps. No spaces in the file path, please. Try installing to only one node and then add the second node. Sometimes this can help with timeout issues. Let me know how this works. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message
news:56433901-2CCC-422C-B0C5-BC896E44E2B4@microsoft.com... > > > SQLStop from Node2: > > 13:19:38 Begin Setup > 13:19:38 8.00.194 > 13:19:38 Mode = Silent > 13:19:38 ModeType = CLUSTER > 13:19:38 Cluster node. > 13:19:38 Cluster secondary node. > 13:19:38 Cluster secondary node. > 13:19:39 g_szIssPath=C:\WINDOWS\setup~0.iss > 13:19:39 GetDefinitionEx returned: 0, Extended: 0x0 > 13:19:39 ValueFTS returned: 1 > 13:19:39 ValuePID returned: 1 > 13:19:39 ValueLic returned: 1 > 13:19:39 System: Windows NT Enterprise Server > 13:19:39 SQL Server ProductType: Enterprise Edition [0x3] > 13:19:39 IsNTCluster returned: 1 > 13:19:39 Begin Action: SetupInitialize > 13:19:39 End Action SetupInitialize > 13:19:39 Begin Action: SetupInstall > 13:19:39 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir > ... > 13:19:39 CommonFilesDir=C:\Program Files\Common Files > 13:19:39 Windows Directory=C:\WINDOWS\ > 13:19:39 Program Files=C:\Program Files\ > 13:19:39 TEMPDIR=C:\DOCUME~1\TRANSA~1\LOCALS~1\Temp\ > 13:19:39 Begin Action: SetupInstall > 13:19:39 digpid size : 256 > 13:19:39 digpid size : 164 > 13:19:39 Begin Action: CheckFixedRequirements > 13:19:39 Platform ID: 0xf00000 > 13:19:39 Version: 5.2.3790 > 13:19:39 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2440 > 13:19:39 End Action: CheckFixedRequirements > 13:19:40 Begin Action: ShowDialogs > 13:19:40 Initial Dialog Mask: 0x183000f7, Disable Back=0x1 > 13:19:40 Begin Action ShowDialogsHlpr: 0x1 > 13:19:40 Begin Action: DialogShowSdWelcome > 13:19:40 End Action DialogShowSdWelcome > 13:19:40 Dialog 0x1 returned: 1 > 13:19:40 End Action ShowDialogsHlpr > 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x2,index=1 > 13:19:40 Begin Action ShowDialogsHlpr: 0x2 > 13:19:40 Begin Action: DialogShowSdMachineName > 13:19:40 [DlgMachine] > 13:19:40 Result = 1 > 13:19:40 Type = 268435466 > 13:19:40 Name = FCIADB2 > 13:19:40 ShowDlgMachine returned: 1 > 13:19:40 Name = FCIADB2, Type = 0x1000000a > 13:19:40 Begin Action: CheckRequirements > 13:19:40 Processor Architecture: x86 (Pentium) > 13:19:40 Service Pack: 256 > 13:19:40 ComputerName: FCIADB2 > 13:19:40 User Name: transactioncluster > 13:19:40 IsAllAccessAllowed returned: 1 > 13:19:40 OS Language: 0x409 > 13:19:40 End Action CheckRequirements > 13:19:40 This combination of Package and Operating System allows a full > product install. > 13:19:40 End Action DialogShowSdMachineName > 13:19:40 begin ShowDialogsUpdateMask > 13:19:40 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0 > 13:19:40 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1 > 13:19:40 Dialog 0x2 returned: 0 > 13:19:40 End Action ShowDialogsHlpr > 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x4,index=2 > 13:19:40 Begin Action ShowDialogsHlpr: 0x4 > 13:19:40 Begin Action: DialogShowSdInstallMode > 13:19:40 [DlgInstallMode] > 13:19:40 Result = 1 > 13:19:40 Type = 1 > 13:19:40 InstallMode : 0x1 > 13:19:40 End Action DialogShowSdInstallMode > 13:19:40 begin ShowDialogsUpdateMask > 13:19:40 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1 > 13:19:40 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 > 13:19:40 Dialog 0x4 returned: 1 > 13:19:40 End Action ShowDialogsHlpr > 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x10,index=4 > 13:19:40 Begin Action ShowDialogsHlpr: 0x10 > 13:19:40 Begin Action: DialogShowSdRegisterUserEx > 13:19:40 End Action DialogShowSdRegisterUserEx > 13:19:40 begin ShowDialogsUpdateMask > 13:19:40 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1 > 13:19:40 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 > 13:19:40 Dialog 0x10 returned: 1 > 13:19:40 End Action ShowDialogsHlpr > 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x20,index=5 > 13:19:40 Begin Action ShowDialogsHlpr: 0x20 > 13:19:40 Begin Action: DialogShowSdLicense > 13:19:40 End Action DialogShowSdLicense > 13:19:40 Dialog 0x20 returned: 1 > 13:19:40 End Action ShowDialogsHlpr > 13:19:40 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14 > 13:19:40 Begin Action ShowDialogsHlpr: 0x4000 > 13:19:40 Begin Action: DialogShowSdVirtualServer > 13:19:40 [DlgVirtServer] > 13:19:40 Result = 1 > 13:19:40 VirtServerName = FCSQLIA > 13:19:40 IpAddresses = 192.86.226.148,255.255.255.0,Public > 13:19:44 ShowDlgVirtualServer returned: 0 > 13:19:44 Ipaddress = 192.86.226.148,255.255.255.0,Public > 13:19:44 szNewList = 192.86.226.148,255.255.255.0,Public > 13:19:44 szModifiedList = > 13:19:44 szRemovedList = > 13:19:44 End Action DialogShowSdVirtualServer > 13:19:44 begin ShowDialogsUpdateMask > 13:19:44 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1 > 13:19:44 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 > 13:19:44 Dialog 0x4000 returned: 1 > 13:19:44 End Action ShowDialogsHlpr > 13:19:44 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15 > 13:19:44 Begin Action ShowDialogsHlpr: 0x8000 > 13:19:44 Begin Action : DialogShowSdDiskGroups > 13:19:44 [DlgDiskGroups] > 13:19:44 Result = 1 > 13:19:44 DiskGroupsName = Group 0 > 13:19:44 ShowDlgDiskGroups returned: 1 > 13:19:44 Disk Group = Group 0 > 13:19:44 End Action : DialogShowSdDiskGroups > 13:19:44 begin ShowDialogsUpdateMask > 13:19:44 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1 > 13:19:44 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 > 13:19:44 Dialog 0x8000 returned: 1 > 13:19:44 End Action ShowDialogsHlpr > 13:19:44 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16 > 13:19:44 Begin Action ShowDialogsHlpr: 0x10000 > 13:19:44 Begin Action: DialogShowSdClusterDef > 13:19:44 [DlgClusterDef] > 13:19:44 Result = 1 > 13:19:44 nNumNodes = 2 > 13:19:44 VirtServerName = FCSQLIA > 13:19:44 szPrefowners = FCIADB1,FCIADB2 > 13:19:44 ShowDlgClusterDef returned: 1 > 13:19:44 PrefOwners = FCIADB1,FCIADB2, NumIp = 0 > 13:19:44 End Action DialogShowSdClusterDef > 13:19:44 begin ShowDialogsUpdateMask > 13:19:44 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1 > 13:19:44 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1 > 13:19:44 Dialog 0x10000 returned: 1
Geoff...
Installed MSSearch manually on both nodes successfully. Re-registered gathercl.dll on both nodes successfully. Re-ran the installation as normal, new errors during the "Setup is creating Virtual Server resources on the Cluster" process: -An Error Occurred while creating virtual server resources for clustering. Cluster specific registry entries couldn't be written <<OK>> -Setup is performing cleanup operations on cluster nodes and will exit once the cleanup is complete. Finally seeing MSSQLSERVER events in Application log of FCIADB1 Per MSKB 872931, added LOCAL SERVICE to the READ permissions on HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg key Deleted the existing but offline/unstartable SQL resources from the Cluster Add MSDTC Resource to the Cluster Group (MSKB 301600 - step 7 on) Enable DTC Access in Windows 2003 (Add/Remove Programs > Application Server [quoted text, click to view] > Enable DTC Access) on both nodes (MSKB 817064) Add LOCAL SERVICE with Read Permissions to HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg key on both nodes (MSKB 872931) Confirm that Remote Registry was started on both nodes Login to each node as domain account used for install and log off Installation Successful. Only problem is, that now I cannot apply SP3a. downloaded & expanded SQLSP3a to c:\sqlsp3a on local node. SETUP FAILED TO PERFORM OPERATIONS ON CLUSTER THE NODES
16:14:52 Begin Setup
16:14:52 Version on Media: 8.00.761 16:14:52 Mode = Normal 16:14:52 ModeType = NORMAL 16:14:52 Begin: SetupInitialize() 16:14:52 End: SetupInitialize() 16:14:52 Begin: CheckFixedRequirements() 16:14:52 Platform ID: 0xf00000 16:14:52 Version: 5.2.3790 16:14:52 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2440 16:14:52 End: CheckFixedRequirements() 16:14:52 Processor Architecture: x86 (Pentium) 16:14:52 Service Pack: 256 16:14:52 ComputerName: FCIADB1 16:14:52 User Name: kmcdermott 16:14:52 IsAllAccessAllowed returned: 1 16:14:52 OS Language: 0x409 16:14:52 Begin: SetupInstall() 16:14:52 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ... 16:14:52 CommonFilesDir=C:\Program Files\Common Files 16:14:52 Windows Directory=C:\WINDOWS\ 16:14:52 Program Files=C:\Program Files\ 16:14:52 TEMPDIR=c:\Temp\ 16:14:52 End: SetupInstall() 16:14:53 Begin: ShowDialogs() 16:14:53 Initial Dialog Mask: 0x8300037, Disable Back=0x1 16:14:53 Begin Action ShowDialogsHlpr: 0x1 16:14:53 Begin Action: DialogShowSdWelcome 16:14:57 End Action DialogShowSdWelcome 16:14:57 Dialog 0x1 returned: 1 16:14:57 End Action ShowDialogsHlpr 16:14:57 ShowDialogsGetDialog returned: nCurrent=0x2,index=1 16:14:57 Begin Action ShowDialogsHlpr: 0x2 16:14:57 Begin Action: DialogShowSdMachineName 16:15:02 ShowDlgMachine returned: 1 16:15:02 Name = FCSQLIA, Type = 0x20000008 16:15:02 End Action DialogShowSdMachineName 16:15:02 begin ShowDialogsUpdateMask 16:15:02 nFullMask = 0x8300037, nCurrent = 0x2, nDirection = 1 16:15:02 Updated Dialog Mask: 0xb73c037, Disable Back = 0x1 16:15:02 Dialog 0x2 returned: 1 16:15:02 End Action ShowDialogsHlpr 16:15:02 ShowDialogsGetDialog returned: nCurrent=0x4,index=2 16:15:02 Begin Action ShowDialogsHlpr: 0x4 16:15:02 Begin Action: DialogShowSdInstallMode 16:15:02 ShowDlgInstallMode returned: 1 16:15:02 InstallMode : 0x2 16:15:02 End Action DialogShowSdInstallMode 16:15:02 begin ShowDialogsUpdateMask 16:15:02 nFullMask = 0xb73c037, nCurrent = 0x4, nDirection = 1 16:15:02 Updated Dialog Mask: 0xb034607, Disable Back = 0x1 16:15:02 Dialog 0x4 returned: 1 16:15:02 End Action ShowDialogsHlpr 16:15:03 ShowDialogsGetDialog returned: nCurrent=0x200,index=9 16:15:03 Begin Action ShowDialogsHlpr: 0x200 16:15:03 Begin Action: DialogShowSdInstanceName 16:15:03 Begin Action: ShowDlgInstanceName 16:15:03 SKU is : Enterprise Edition 16:15:03 End Action: ShowDlgInstanceName 16:15:03 ShowDlgInstanceName returned : 0 16:15:03 InstanceName : MSSQLSERVER 16:15:03 End Action DialogShowSdInstanceName 16:15:03 begin ShowDialogsUpdateMask 16:15:03 nFullMask = 0xb034607, nCurrent = 0x200, nDirection = 0 16:15:03 Updated Dialog Mask: 0xb034603, Disable Back = 0x1 16:15:03 Dialog 0x200 returned: 0 16:15:03 End Action ShowDialogsHlpr 16:15:03 ShowDialogsGetDialog returned: nCurrent=0x400,index=10 16:15:03 Begin Action ShowDialogsHlpr: 0x400 16:15:03 Begin Action: DialogShowSdMaintain 16:15:03 ShowDlgMaintainInstall returned : 1 16:15:03 Type : 0xc 16:15:03 CreateSetupTopology(FCIADB1), Handle : 0x14d3e90, returned : 0 16:15:03 CreateSetupTopology returned : 0, Handle : 0x14d3e90 16:15:03 Topology Type : 1, Return Value : 0 16:15:03 ST_GetPhysicalNode returned : 0, PNHandle : 0x14d3eb8 16:15:03 PN_EnumerateEx returned : 0 16:15:03 PN_GetSQLStates returned : 0, SqlStates : 0x88008221 16:15:03 PN_GetInstance for MSSQLSERVER [0x14d3eb8] returned : 0 16:15:03 SQLI_GetPackageId [0x14d4448] returned : 0, PackageId = 0x3 16:15:03 SQLI_GetVersion [0x14d4448] returned : 0, Version = 8.00.194 16:15:03 SQLI_GetSQLStates for MSSQLSERVER [0x14d4448] returned : 0, SQLStates: 0x400209 16:15:03 SQLI_GetInstallPath [0x14d4448] returned : 0, Path = C:\Program Files\Microsoft SQL Server\MSSQL 16:15:03 SQLI_GetDataPath [0x14d4448] returned : 0, DataPath = R:\Program Files\Microsoft SQL Server\MSSQL 16:15:03 SQLI_GetVersion [0x14d4448] returned : 0, Version = 8.00.194 16:15:03 SQLI_GetRegKeyRoot [0x14d4448] returned : 0, RegKeyRoot = Software\Microsoft\MSSQLServer 16:15:03 SQLI_GetPackageName [0x14d4448] returned : 0, szPackage = Enterprise Edition 16:15:03 SQLI_GetPackageId [0x14d4448] returned : 0, PackageId = 0x3 16:15:03 Previous Install Path: C:\Program Files\Microsoft SQL Server\MSSQL 16:15:03 Previous Install Data: R:\Program Files\Microsoft SQL Server\MSSQL 16:15:03 Previous Install Version: 8.00.194 16:15:03 ReleaseSetupTopology 16:15:03 End Action DialogShowSdMaintain 16:15:03 begin ShowDialogsUpdateMask 16:15:03 nFullMask = 0xb034603, nCurrent = 0x400, nDirection = 1 16:15:03 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1 16:15:03 Dialog 0x400 returned: 1 16:15:03 End Action ShowDialogsHlpr 16:15:03 ShowDialogsGetDialog returned: nCurrent=0x2000,index=13 16:15:03 Begin Action ShowDialogsHlpr: 0x2000 16:15:03 Begin Action: DialogShowSdUpgrade 16:15:03 ShowDlgUpgrade returned : 1 16:15:03 Checking databases on instance 'MSSQLSERVER' 16:15:03 Begin Action: Check for VS Node 16:15:03 Begin Action: Check for VS Node 16:15:03 Begin Action: Cluster Resources Offline 16:15:09 End Action: Cluster Resources Offline 16:15:09 Authenticate access 16:15:09 Begin SDPassword Dialog 16:15:28 End SDPassword Dialog 16:15:28 c:\Temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 6 -Service MSSQLSERVER 16:15:28 Process Exit Code: (0) 16:15:28 c:\Temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4010 \-T4022 \-m 16:15:39 Process Exit Code: (0) 16:15:39 C:\sql2ksp3\x86\BINN\osql.exe -Slpc:FCSQLIA -n -d master -Q "exit" -o "c:\Temp\sqlsp.out" -E 16:15:39 Process Exit Code: (0) 16:15:39 Begin: CheckSAPassword 16:15:39 Begin: LogOnUsingBlankSA 16:15:39 C:\sql2ksp3\x86\BINN\osql.exe -Slpc:FCSQLIA -n -d master -o "c:\Temp\sqlsp.out" -Q"Exit(declare @ret int if (select count(*) from master..syslogins where name='sa' AND ( (1 = pwd 16:15:39 Process Exit Code: (0) 16:15:39 End: LogOnUsingBlankSA 16:15:39 Begin: SdBlankPwd 16:15:39 End: SdBlankPwd 16:15:39 End: CheckSAPassword 16:15:39 Begin: SdShowSp3WrngDlg 16:15:39 C:\sql2ksp3\x86\BINN\osql.exe -Slpc:FCSQLIA -n -d master -o "c:\Temp\sqlsp.out" -Q"Exit(declare @ret int if (select count(*) from msdb.dbo.systargetservers) = 0 Set @ret=0 else Set @ret=403 Select @ret)" -E 16:15:40 Process Exit Code: (0) 16:15:54 End: SdShowSp3WrngDlg 16:15:54 Begin : SdErrorReportingDlg 16:15:57 End: SdErrorReportingDlg 16:15:57 Access authenticated 16:15:57 C:\sql2ksp3\x86\BINN\osql.exe -Slpc:FCSQLIA -n -b -d master -o c:\Temp\~sqldb0.txt -i c:\Temp\SqlSetup\Bin\dbverify.sql -E 16:15:57 Process Exit Code: (0) 16:15:57 c:\Temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 6 -Service MSSQLSERVER 16:16:12 Process Exit Code: (0) 16:16:12 Setup Type: Custom (303) 16:16:12 Processing: SQLProg 16:16:12 Processing: SQLProg\SQLServr
Geoff...
rebooted node 1 checked version as per http://support.microsoft.com/default.aspx?scid=/support/servicepacks/sql/2000/sp3readme.asp#_identifying_the_current_version_of_sql_server_or_analysis_services confirmed version to be 8.00.766 -- looking good rebooted node 2 Source: EventSystem Category (50) EventID 4609 COM+EventSystem detected a bad return code during its internal processing. HRESULT was 80070005 from line 44 of d:\srvtm\com\complus\src\eventsystemobj.cpp Please Contact Microsoft Product Support Services. So now I have no network connections in Control Panel, Network Service won't start (hangs) and subsequently cannot see the network, AD, or cluster.
Have evicted node2 from the cluster but unable to run cleanup as the network
cannot see it, and it cannot see any other machines. Have removed node2 from AD, and am rebuilding it from scratch. Will see what happens. Thanks very much for all of your assistance & suggestions throughout.
By CLEAN do you mean CLUSTER NODE NODE2 /FORCECLEANUP ??
[quoted text, click to view] "Geoff N. Hiten" wrote:
> Make sure and run the SQL install to clean Node 2 from the SQL installation > or you will not be able to install SQL to the replacement node later on. It > will fuss that it cannot find the target node, but it still has to run to > clean out references to it from the working node(s). > > -- > Geoff N. Hiten > Senior Database Administrator > Microsoft SQL Server MVP > > "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message > news:C075B8D7-D64A-4BA8-86E1-BB4E06DEC7B5@microsoft.com... > > Have evicted node2 from the cluster but unable to run cleanup as the > > network > > cannot see it, and it cannot see any other machines. Have removed node2 > > from > > AD, and am rebuilding it from scratch. > > > > Will see what happens. > > > > Thanks very much for all of your assistance & suggestions throughout. > > > > > >
Reboot both nodes before SP3a. Install may have a file locked on the remote
node. Also, move the SQL resource group back and forth between the nodes at least once aftre the reboot but before the SP3a install. That should either fix the cluster registry keys or determine what is broken. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message news:3EC7FB56-2168-424D-925E-C810C7A30EFC@microsoft.com... > Geoff... > > Installed MSSearch manually on both nodes successfully. > > Re-registered gathercl.dll on both nodes successfully. > > Re-ran the installation as normal, new errors during the "Setup is > creating > Virtual Server resources on the Cluster" process: > > -An Error Occurred while creating virtual server resources for clustering. > Cluster specific registry entries couldn't be written <<OK>> > -Setup is performing cleanup operations on cluster nodes and will exit > once > the cleanup is complete. > > Finally seeing MSSQLSERVER events in Application log of FCIADB1 > > Per MSKB 872931, added LOCAL SERVICE to the READ permissions on > HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg key > > Deleted the existing but offline/unstartable SQL resources from the > Cluster > > Add MSDTC Resource to the Cluster Group (MSKB 301600 - step 7 on) > > Enable DTC Access in Windows 2003 (Add/Remove Programs > Application > Server >> Enable DTC Access) on both nodes (MSKB 817064) > > Add LOCAL SERVICE with Read Permissions to > HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServers\Winreg key on both > nodes (MSKB 872931) > > Confirm that Remote Registry was started on both nodes > > Login to each node as domain account used for install and log off > > Installation Successful. > > > Only problem is, that now I cannot apply SP3a. > > downloaded & expanded SQLSP3a to c:\sqlsp3a on local node. > > SETUP FAILED TO PERFORM OPERATIONS ON CLUSTER THE NODES > > log follows:
Sounds like a blown node due to a COM+ security mixup. I would follow BOL
instructions for replacing a failed node (scenario 1). Once the failed node is out of the mix, you should be able to apply SP3a + whatever hotfix you need to the remaining node. You can likely reformat and reload the OS on the failed node faster than you can undo a COM+ snafu . Alternatively, you could call PSS and see if they have any advice. At this point $250 may be the cheapest way out. BTW, Step 2 should say remove the failed node, not remove the entire instance. I believe the docs are being updated to reflect the correct procedure. Look under Maintaining a Failover Cluster, Removing a node from an existing Failover cluster for how to remive a node from an instance. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message news:1D00E424-F866-46D0-8856-A829121A6634@microsoft.com... > Geoff... > > rebooted node 1 > checked version as per > http://support.microsoft.com/default.aspx?scid=/support/servicepacks/sql/2000/sp3readme.asp#_identifying_the_current_version_of_sql_server_or_analysis_services > > confirmed version to be 8.00.766 -- looking good > > rebooted node 2 > Source: EventSystem > Category (50) > EventID 4609 > > COM+EventSystem detected a bad return code during its internal processing. > HRESULT was 80070005 from line 44 of > d:\srvtm\com\complus\src\eventsystemobj.cpp > Please Contact Microsoft Product Support Services. > > > So now I have no network connections in Control Panel, Network Service > won't > start (hangs) and subsequently cannot see the network, AD, or cluster. > > > HELP!!!
Make sure and run the SQL install to clean Node 2 from the SQL installation
or you will not be able to install SQL to the replacement node later on. It will fuss that it cannot find the target node, but it still has to run to clean out references to it from the working node(s). -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message news:C075B8D7-D64A-4BA8-86E1-BB4E06DEC7B5@microsoft.com... > Have evicted node2 from the cluster but unable to run cleanup as the > network > cannot see it, and it cannot see any other machines. Have removed node2 > from > AD, and am rebuilding it from scratch. > > Will see what happens. > > Thanks very much for all of your assistance & suggestions throughout. > >
You are referring to a CLUSTER.EXE command option. I am referring to the
SQL installer procedure that removes node 2 from the SQL installation information store. Even if you evict node 2, SQL still thinks it is is a valid node for the SQL instance. You have to run the SQL installer on node 1 and remove node 2. This is all detailed in BOL under Maintaining a Failover Cluster | Removing a node from an existing Failover cluster. Until this is done, you cannot apply a service pack or add the node back to the SQL virtual server. SQL thinks the node still exists and tries to update the local binaries, even ifthe node has been evicted from the cluster. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message news:4C36D14B-4874-4633-9B01-3B603FAFBC6E@microsoft.com... > By CLEAN do you mean CLUSTER NODE NODE2 /FORCECLEANUP ?? > > "Geoff N. Hiten" wrote: > >> Make sure and run the SQL install to clean Node 2 from the SQL >> installation >> or you will not be able to install SQL to the replacement node later on. >> It >> will fuss that it cannot find the target node, but it still has to run to >> clean out references to it from the working node(s). >> >> -- >> Geoff N. Hiten >> Senior Database Administrator >> Microsoft SQL Server MVP >> >> "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message >> news:C075B8D7-D64A-4BA8-86E1-BB4E06DEC7B5@microsoft.com... >> > Have evicted node2 from the cluster but unable to run cleanup as the >> > network >> > cannot see it, and it cannot see any other machines. Have removed >> > node2 >> > from >> > AD, and am rebuilding it from scratch. >> > >> > Will see what happens. >> > >> > Thanks very much for all of your assistance & suggestions throughout. >> > >> > >> >> >>
Geoff...
While rebooting Node1, the same thing happened with the network connectivity loss. As well, the freshly re-built Node02 (new name) lost connectivity after adding to the AD domain, only this time I can't get in at all... domain or local accounts. I've succumbed to the likliehood that it's an AD / GPO problem now, as I can PING the box successfully until the Windows startup changes from PREPARING NETWORK CONNECTIONS to APPLYING COMPUTER SETTINGS, then it dies (DESTINATION HOST UNREACHABLE). Thanks again for all of your assistance & Guidance. In case you want to follow where we go with this, the new thread I've started in the 2003 AD forum is http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.active_directory Regards, Kevin [quoted text, click to view] "Geoff N. Hiten" wrote:
> You are referring to a CLUSTER.EXE command option. I am referring to the > SQL installer procedure that removes node 2 from the SQL installation > information store. Even if you evict node 2, SQL still thinks it is is a > valid node for the SQL instance. You have to run the SQL installer on node > 1 and remove node 2. This is all detailed in BOL under Maintaining a > Failover Cluster | Removing a node from an existing Failover cluster. Until > this is done, you cannot apply a service pack or add the node back to the > SQL virtual server. SQL thinks the node still exists and tries to update > the local binaries, even ifthe node has been evicted from the cluster. > > -- > Geoff N. Hiten > Senior Database Administrator > Microsoft SQL Server MVP > > "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message > news:4C36D14B-4874-4633-9B01-3B603FAFBC6E@microsoft.com... > > By CLEAN do you mean CLUSTER NODE NODE2 /FORCECLEANUP ?? > > > > "Geoff N. Hiten" wrote: > > > >> Make sure and run the SQL install to clean Node 2 from the SQL > >> installation > >> or you will not be able to install SQL to the replacement node later on. > >> It > >> will fuss that it cannot find the target node, but it still has to run to > >> clean out references to it from the working node(s). > >> > >> -- > >> Geoff N. Hiten > >> Senior Database Administrator > >> Microsoft SQL Server MVP > >> > >> "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message > >> news:C075B8D7-D64A-4BA8-86E1-BB4E06DEC7B5@microsoft.com... > >> > Have evicted node2 from the cluster but unable to run cleanup as the > >> > network > >> > cannot see it, and it cannot see any other machines. Have removed > >> > node2 > >> > from > >> > AD, and am rebuilding it from scratch. > >> > > >> > Will see what happens. > >> > > >> > Thanks very much for all of your assistance & suggestions throughout. > >> > > >> > > >> > >> > >> > >
Geoff...
I currently have/had them in their own OU (which I was suspecting was actully causing the problems), but have since tried moving them back into the generic/built-in COMPUTERS OU, but to no avail. [quoted text, click to view] "Geoff N. Hiten" wrote:
> An AD issue would explain the problems. Personally, I have my DB servers in > their own OU, mainly to keep overly restrictive group policies from being > applied. You may want to try this approach if your networking people agree. > > -- > Geoff N. Hiten > Senior Database Administrator > Microsoft SQL Server MVP >
An AD issue would explain the problems. Personally, I have my DB servers in
their own OU, mainly to keep overly restrictive group policies from being applied. You may want to try this approach if your networking people agree. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message news:ECF0B89B-6679-4DBE-9BB9-833ADD3F9334@microsoft.com... > Geoff... > > While rebooting Node1, the same thing happened with the network > connectivity > loss. > > As well, the freshly re-built Node02 (new name) lost connectivity after > adding to the AD domain, only this time I can't get in at all... domain or > local accounts. > > I've succumbed to the likliehood that it's an AD / GPO problem now, as I > can > PING the box successfully until the Windows startup changes from PREPARING > NETWORK CONNECTIONS to APPLYING COMPUTER SETTINGS, then it dies > (DESTINATION > HOST UNREACHABLE). > > Thanks again for all of your assistance & Guidance. > > In case you want to follow where we go with this, the new thread I've > started in the 2003 AD forum is > http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.active_directory > > Regards, > Kevin > > "Geoff N. Hiten" wrote: > >> You are referring to a CLUSTER.EXE command option. I am referring to the >> SQL installer procedure that removes node 2 from the SQL installation >> information store. Even if you evict node 2, SQL still thinks it is is a >> valid node for the SQL instance. You have to run the SQL installer on >> node >> 1 and remove node 2. This is all detailed in BOL under Maintaining a >> Failover Cluster | Removing a node from an existing Failover cluster. >> Until >> this is done, you cannot apply a service pack or add the node back to the >> SQL virtual server. SQL thinks the node still exists and tries to update >> the local binaries, even ifthe node has been evicted from the cluster. >> >> -- >> Geoff N. Hiten >> Senior Database Administrator >> Microsoft SQL Server MVP >> >> "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message >> news:4C36D14B-4874-4633-9B01-3B603FAFBC6E@microsoft.com... >> > By CLEAN do you mean CLUSTER NODE NODE2 /FORCECLEANUP ?? >> > >> > "Geoff N. Hiten" wrote: >> > >> >> Make sure and run the SQL install to clean Node 2 from the SQL >> >> installation >> >> or you will not be able to install SQL to the replacement node later >> >> on. >> >> It >> >> will fuss that it cannot find the target node, but it still has to run >> >> to >> >> clean out references to it from the working node(s). >> >> >> >> -- >> >> Geoff N. Hiten >> >> Senior Database Administrator >> >> Microsoft SQL Server MVP >> >> >> >> "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message >> >> news:C075B8D7-D64A-4BA8-86E1-BB4E06DEC7B5@microsoft.com... >> >> > Have evicted node2 from the cluster but unable to run cleanup as the >> >> > network >> >> > cannot see it, and it cannot see any other machines. Have removed >> >> > node2 >> >> > from >> >> > AD, and am rebuilding it from scratch. >> >> > >> >> > Will see what happens. >> >> > >> >> > Thanks very much for all of your assistance & suggestions >> >> > throughout. >> >> > >> >> > >> >> >> >> >> >> >> >> >>
PROBLEM SOLVED.
Reboot into SAFE MODE W/ NETOWRKING (this gets the NIC back online and caches your creedntials for a bit. Mainly lets you see the event log) Uninstall/Disable any & all AntiVirus scanning services on all cluster nodes. And here's the big one: Disable the IPSEC Service Reboot and VOILA! back online. Went back through the littany of rights and user settings that I found the first time through for SQL installation & Virtual Server & Clustering, and the setup from Node 1 to Node 2 was successful not only on the first try, but in about 12 minutes (incl SP3a)... pervious install run was about 45-50 mins. Thanks again for the assistance.
Antivirus Software May Cause Problems with Cluster Services
http://support.microsoft.com/kb/250355/ This doesn't get a lot of visibility because it won't show up in a SQL Server specific KB search. I totally didn't consider it either. I should have cought it sooner. I know how troublesome AV can be on a cluster. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message news:70A5F181-2AA8-4873-A703-4A8464EE0979@microsoft.com... > PROBLEM SOLVED. > > > Reboot into SAFE MODE W/ NETOWRKING (this gets the NIC back online and > caches your creedntials for a bit. Mainly lets you see the event log) > > Uninstall/Disable any & all AntiVirus scanning services on all cluster > nodes. > > And here's the big one: > > Disable the IPSEC Service > > Reboot and VOILA! back online. > > Went back through the littany of rights and user settings that I found the > first time through for SQL installation & Virtual Server & Clustering, and > the setup from Node 1 to Node 2 was successful not only on the first try, > but > in about 12 minutes (incl SP3a)... pervious install run was about 45-50 > mins. > > Thanks again for the assistance. > > Kevin
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 |