May 24, 2011 at 2:05 pm
Recently tried to apply 2005 SP4 and now the instances are different versions on the nodes. The major issue is, if we fail over instance 1 to Node2 it fails since it's a different version. We tried reapplying SP4 and it failed. I don't have the exact error, but it was something like "failed to install KB####". Any thoughts on how we can fix?
Here are the specs:
Sql version 2005 32bit
Windows version 2003 SP2
Active/Active cluster
2 Instances
Node1 Instance1 = version 9.00.4035
Node1 Instance2 = version 9.00.4035
Node2 Instance1 = version 9.00.5000
Node2 Instance2 = version 9.00.4035
May 24, 2011 at 2:20 pm
Have you tried to rollback the SP?
Can you get the exact error?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
May 24, 2011 at 8:14 pm
When you say you cannot failover the instance - which instance are you failing over and what is the current node hosting that instance?
When I had a similar problem on an earlier SP upgrade, the upgrade completed successfully for the instance on the active node - failed on the passive node. I was able to fail that instance over to the passive node because the Edition's are the same (you should be able to failover from SP4 to the SP3 node).
The fix for this was to failover to the non updated node (all instances), shut down the now passive node which was updated then perform the service pack update again. This allows the upgrade to move forward because it doesn't try to update the passive node that has already been upgraded.
Once the service pack is completed - start the passive node, failover and restart the other node.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 31, 2011 at 10:17 am
I found the error in the hotfix folder. Do I just have to add the service acct to the windows group? See below for error and acct info...
Error information:
Error 29512. SQL Server Setup was unable add user service_Instance1User@domain to local group domain\Instance1Group.
Product: Microsoft SQL Server 2005 - Update 'Service Pack 4 for SQL Server Database Services 2005 ENU (KB2463332)' could not be installed. Error code 1603.
------------------------
Acct information:
Instance1 service acct = service_Instance1User
Windows group and sql sysadmin = Instance1Group
May 31, 2011 at 12:47 pm
**UPDATE**
After researching, it may have errored because of the '@domain.local' after the service acct user name. This user is part of an AD group, so when the SP runs, it looks for a LOCAL group rather than the AD group.
June 1, 2011 at 6:45 am
I do not know if error message 29512 is deliberately displaying the account name in the form account@domain or merely showing the account in the form in which it has been found.
I do know that SQL Server install does not like accounts to be in the form account@domain, and needs accounts to be specified in the legacy domain\account format. If you have used the Windows Service applet to chnge a service account and specified the new name in the form account@domain, then although SQL Server will work OK, you may find you have a problem when you apply a fix.
If this is your problem, then use the Windows Service applet to change the format in which the account name is stored. The SP install may than work OK.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
June 1, 2011 at 6:47 am
Thank you so much for your reply. The fix is this weekend, so I will update my post after that.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply