Cluster Upgrade SP2 2005

Have recently performed an in-place upgrade of a 2 instance sql cluster from 2000 to 2005. The upgrade process went relatively smoothly. However, I am running into problems installed sp2. The first problem that I run into is that I have resrcmon.exe locked. I can click next, which is fine, but once I get past that point I get stuck during the installation process. I am updating DatabaseServices and Integration Services. It gets stuck on 'Awaiting first complete passive cluster node SQL-Test'. Does anyone have any ideas?
Thanks,
TimFor what it's worth I'm experiencing the same issue as described above. I'm using VMWare Server and have a Windows 2003 Enterprise Edition cluster with SQL Server 2005 Standard Edition clustered on top. This works well but in trying to apply SP2 it is stuck "Awaiting first complete passive cluster node". Slight difference from that described above, I had no locked files.

Any info that anyone could provide would be greatly appreciated.

Cheers,

Ian
|||Unbelievable. Typically just as I finish writing the above, the process moved on. However it failed at the "Database Services" product. Everything else seemed to go okay but I'll have to check and will come back with any info I find.

Cheers,

Ian
|||I got my issue resolved...after talking to MS Support for half of a day. There are a lot of things that you have to make sure is just right. For example, when you install the services, it is easier to have the first node control both instances. From there, make sure you install the client tools on the default instance first. You also cannot have remote connections to the 2nd node in the cluster (will cause it to fail). Mine failed on installed the database services as well. Another thing we had to change was that when the network guys setup the cluster, the distributed transaction coordinator wasn't created as a clustered resource...it needs to be. let me know if this helps any.
Tim|||Tim,

Did you manage to continue with resrcmon.exe locked or did you find a way to stop it (it's part of the cluster so, short of stopping the cluster services I wasn't sure how else to stop it)?

We've got the DTC in place in our production cluster but I forgot to add it with my virtual one. I've done this now and will give it another go shortly.

Cheers,

Ian
|||At first I seen that resrcmon.exe was locked, and it did concern me. However, I don't think that it really matters if it is locked or not. If it is locked, you can still go through with the install, but it will prompt you to reboot later in the process. Try to kill all remote connections to either cluster node, place both instances on one node, and try to install that way. That will likely unlock resrcmon.|||I actually only have one instance, it is on the node from which I'm running the SP. WRT remote connections, I can't see anything apart from the clustering services that would be connecting remotely to the second node.

That said, I've only got resrcmon.exe locked now so am gonna proceed with the SP and see where I get - beauty of VMs is that I can just roll 'em back any time I like :-)
|||

I had the exact same issue. Installing the client tools on both nodes, and then moving the inst1 over to the passive node and running the SP2 from there seemed to do the trick.

|||I've finally had some level of success with this on my virtual cluster. But it was kinda forceful. I basically downed node 2, installed the SP onto node 1 (twice as it had "reboot required" on the SQL Server engine the first time). Then brought up node 2, failed over and downed node 1. Did the same to node 2 (twice) and brought node 1 back up. Testing seems to confirm this has gone okay. However, as we're in the process of trying to get a test cluster (for exactly this kind of thing - good as VMWare is, it's not the real thing) I'm not going to apply this to production until that's happened.

Cheers,

Ian
|||

Hi Ian,

Please help - when you downed the one node - was it shutdown or did you stop cluster service on the node or did you pause the node?

Thanks in advance :-)

|||

Hi there,

Basically I did the following.

Node 1 was up, node 2 was shutdown completely. I upgraded node 1 to SP2, then brought node 2 back online and failed over by shutting down node 1. I then upgraded node 2 to SP2, brought node 1 back online, failed over manually to confirm all as expected and left it at that. Bear in mind this was on virtual machines so is not a perfect test. I've yet to do this on our production cluster and am currently trying to get a proper physical test cluster in place to run through this for real.

Hope this helps!

Cheers,

Ian