SQL Server 2005 Standard SP 4
-
Monday, February 04, 2013 5:45 PMI have a two node cluster. The service Pack 4 is installed on one node ("B") but will not install on "A" node. When trying to install, "A" is the active node and setup.exe (process hotfix.exe) hangs.
- Moved by Samuel Lester - MSFTMicrosoft Employee, Moderator Monday, February 04, 2013 6:34 PM
All Replies
-
Monday, February 04, 2013 7:13 PMModerator
Hello,
Try to apply the update on the passive node using the /passive switch.
http://support.microsoft.com/kb/973993
If the service pack fails to install, share the summary.txt and detail.txt log file with us. The following article may help you locate the file on disk:
http://technet.microsoft.com/en-us/library/ms143702(v=sql.90)
Please read the following resources also:
http://support.microsoft.com/kb/929151
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com- Proposed As Answer by Fanny LiuMicrosoft Contingent Staff, Moderator Thursday, February 07, 2013 5:05 AM
-
Monday, February 04, 2013 10:17 PMSounds like it was run incorrectly. To patch a 2005-based cluster in a normal scenario, you run Setup on the node that owns the resource group. That will patch all nodes. If it was just run on the node that doesn't own the resources, it will only patch the binaries. Not sure what you mean by hangs as it is meant to run on the node that owns the resources as I said.
Allan Hirt Blog: http://www.sqlha.com/blog Coming in 2013: Mission Critical SQL Server 2012 - the followup to Pro SQL Server 2008 Failover Clustering
-
Thursday, February 07, 2013 1:16 PMYou are correct. The patch was run successfully on the node that did not own the resource. You then cannot remove the patch. So I then tried running it on the node that does own the resource and now I'm getting a SCC Error. "The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine xxxxx Error:2148007941 (0x80080005).
- Edited by Preston_C Thursday, February 07, 2013 1:16 PM
-
Thursday, February 07, 2013 1:19 PMI tried running it in passive and am now getting: "The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine xxxx Error:2148007941 (0x80080005)".
- Edited by Preston_C Thursday, February 07, 2013 1:20 PM
-
Thursday, February 07, 2013 1:33 PMModerator
Hello,
Please read the following resource:
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/c5d16f29-6f2d-48cf-a17d-42ab1bb77c9b/
Hope this help.
Regards,
Alberto Morillo
SQLCoffee.com -
Thursday, February 07, 2013 4:25 PM
I tried those scripts. Still got the same WMI error.
I'm thinking of manually uninstalling the SQL Server, repairing the node OS, re-join the cluster and then install SQL Server through the cluster.
- Marked As Answer by Fanny LiuMicrosoft Contingent Staff, Moderator Friday, March 08, 2013 4:33 AM

