September 12, 2011 at 6:07 am
Hi,
Not a "Newbie" but definitely new to this issue. A year or so ago, a third party vendor set up a SQL 2005 2-node cluster for a security product that our hospital uses. This product needs to be on-line 24/7 so it's been difficult for me to find a good time to try and fix what's wrong. I had a small window of opportunity this past weekend and was not able to resolve my issue. Problem is that the vendor left us with 2 different versions of SQL running on the 2 nodes : node 1 has SQL 2005 Standard edition SP2 ; node 2 has SQL 2005 Standard edition base product. A while ago when one of our Windows engineers decided to apply Windows updates, they failed over to node 2 and applied patches to node 1. The Maintenance plans created on node 1 would not run on node 2 and indications were that it had something to do with the difference in SQL versions. We have been running on node 1 all along. I failed node 1 over to node 2 because I knew I had to apply the SP to the active node. When I tried to apply SP2 to node 2, I had no luck. After several attempts, I finally gave up. It acts like it's going to apply and then issues a message that it is "Rolling Back" the action but I don't know why. Is there a certain spot in the LOG file that I can look to help understand what's wrong ? Usually don't have problems applying SPs. Thanks.
September 13, 2011 at 12:24 am
watson_mike (9/12/2011)
Hi,Not a "Newbie" but definitely new to this issue. A year or so ago, a third party vendor set up a SQL 2005 2-node cluster for a security product that our hospital uses. This product needs to be on-line 24/7 so it's been difficult for me to find a good time to try and fix what's wrong. I had a small window of opportunity this past weekend and was not able to resolve my issue. Problem is that the vendor left us with 2 different versions of SQL running on the 2 nodes : node 1 has SQL 2005 Standard edition SP2 ; node 2 has SQL 2005 Standard edition base product. A while ago when one of our Windows engineers decided to apply Windows updates, they failed over to node 2 and applied patches to node 1. The Maintenance plans created on node 1 would not run on node 2 and indications were that it had something to do with the difference in SQL versions. We have been running on node 1 all along. I failed node 1 over to node 2 because I knew I had to apply the SP to the active node. When I tried to apply SP2 to node 2, I had no luck. After several attempts, I finally gave up. It acts like it's going to apply and then issues a message that it is "Rolling Back" the action but I don't know why. Is there a certain spot in the LOG file that I can look to help understand what's wrong ? Usually don't have problems applying SPs. Thanks.
check the log files for errors. ...\Microsoft Sql Server\90\Setup Bootstrap\log\summary.txt
start there, then drill down into the log files in the hotfix directory below that contains the error. start at the bottom and work your way up.
September 13, 2011 at 7:58 am
Thanks for the heads up on the summary.txt file. It displays the error :
MSI (s) (A0!8C) [19:04:09:615]: Product: Microsoft SQL Server 2005 -- Error 29512. SQL Server Setup was unable add user GHS2000\GESQL to local group GHS2000\GESQLSvcGrp.
Error 29512. SQL Server Setup was unable add user GHS2000\GESQL to local group GHS2000\GESQLSvcGrp.
The MicroSoft workaround is :
To work around this problem, add the SQL Service Account to the domain-level group for the Microsoft Full-Text Engine for SQL Server (MSFTESQL) service before you install SQL Server 2005 SP1.
What's now confusing me is, when I look at the domain group, the user is already there. So, was the SP trying to add it but failed because it already existed ? And yet the MS workaround reads to me that the user has to be there for the SP to install ?
The MS article I got the workaround from is described as :
When you try to upgrade Microsoft SQL Server 2005 to SQL Server 2005 Service Pack 1 (SP1), the cluster setup may fail.
Is there really something else going on here that makes this all so confusing to me ? What's the install trying to do with the cluster ?
Thanks again for your help.
September 13, 2011 at 7:59 am
Can you go straight to SP3 or SP4 while you're at it ? SP2 is old & buggy too.
September 15, 2011 at 6:54 am
Homebrew1, thanks for the question back. I checked with the vendor and just recently they approved SP3. Maybe that's what we need to do to get around this problem. I also told the vendor they should be cleaning up their own mess instead of the customer. This is the only cluster we have that is 2005, we have several 2008s. When we apply SP3 to the active node, is it supposed to update the passive node also or does the SP have to be applied to both as active nodes ? I can tell form the summary.txt and log files that are on the two nodes that the vendor rep had problems with applying SP2 when he was here almost 3 years ago but apparently he didn't know or he intentionally left us in the state we're in now. Thanks for any help you can provide.
September 15, 2011 at 11:28 am
Sorry, I don't know much about clustering.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply