August 11, 2009 at 3:30 am
Hi all,
I had to install Sp3 on our 2005 cluster production box.
We have three instances on the server.
During the setup the the wizard was waiting a long time at the passive node.
We connected to the passive node and found out a window asking for the file sqlrun.msc. We tried to select our SQL dvd location for the same. However the installation reported failure. We failed to the passive node and tried the set up again. This time also the wizard reported failure. But we found the passive node instances were patched with the version 4035.
Now what we have is one node( the node which patched) still is running 3042
but the second node all instance are patched 4035.
Please help if you have any idea why the setup was asking for the msc file?
August 11, 2009 at 3:50 am
I had a similar issue a few years ago when installing SP3 for SQL Server 2000. The installation failed on the passive node on a few occasions, saying it was unable to access one of the installation files.
In the end, I diagnosed a faulty CD and/or CD Drive. I copied the contents of the CD to disk, and ran the installation from there without any further problems.
I didn't end up with node on differing versions though.
August 11, 2009 at 8:58 am
Roshan,
I agree with the last poster (in part), you definately have to have the SP3 exe local (to your active) when running.
When you talk about active and passive, is this where sql was? If so the engine itself should now be patched in which case just run the patch on the passive node (whille sql is active on the other).
All you should be missing is some services and local stuff on one nodes (but not engine). If in SSMS it reports its self as 9.0.4035 then the engine has been patched. So just run SP3 install on the node with the different version (while sql is active on the other).
Hope that made senc, almost confused myself. Let me know if any probs. 😉
Adam Zacks-------------------------------------------Be Nice, Or Leave
August 11, 2009 at 11:10 pm
Check the following information before you install SP3 on a failover cluster instance:
?Do not stop the cluster service before you run the SP3 Setup program, or while the installation program is running
?Do not end any running processes before you run the SP3 Setup program. The SP3 Setup program will stop and start the SQL Server service.
?Run the SP3 Setup program on the primary node of the failover cluster instance.
?You must restart all failover cluster nodes after SP3 is finished installing.
?To ensure that SQL Server 2005 SP3 will be installed on all nodes of failover cluster instance verify that TASK Scheduler is running on all passive nodes of your cluster instance
? If any resources have been added that have dependencies on SQL Server resources, those dependencies must either be removed or taken offline before you install SP3. If you do not remove the dependencies, the installation of SP3 will take those resources offline.
?Run the SP3 executable package file from the active node that owns the group containing the failover cluster instance you plan to upgrade. This installs the service pack files on all nodes of the cluster.
? You can not install SP3 from any Passive node in the failover cluster.
?On the feature selection page of the SP3 setup wizard, select the failover cluster instance that you plan to upgrade. Setup will prompt you for the login credentials that are used to connect to other nodes in cluster.
?Keep all nodes of the cluster online during setup. This ensures that the upgrade is applied to each cluster node.
?Setup might require you to restart the failover cluster nodes. This restart replaces the files that are in use during setup.
Prepare for a SQL Server 2005 SP3 Installation
You must do the following before you install the SP3:
?Backup all the system databases and user databases.
?Copy the mdf and ldf files of system and user databases to a separate location.
?Verify that system databases have enough free space(Min 500KB)
?Verify that SQL Server 2005 service accounts are not disabled and can be started
?Setup might fail if the service startup type for the MSSQLServer and ReportServer
Services is set to Disabled
Rollback Strategy
You must do the following if the SP3 installation fails:
?Uninstall the SQL Server 2005.
?Install the New SQL Server 2005 instance and apply SP2.
?Stop the services and overwrite the new mdf and ldf files with old mdf and ldf files
?Start the service.
August 13, 2009 at 12:25 am
Thank you all.
@ Adam : Yes the I was refering to sql service when i said active/ passive. Now all instances in one node is patched and the second is not.
I ran @@version in each instance after making the nodes active one by one.
Now I am thinking to remove the second node out of the sql cluster and try to patch it independently and add it again.
Is this a feasible option, Is there anything I need to plan beforehand?
August 13, 2009 at 1:09 am
I have never before removed a node from a cluster and as for adding it back after, i have never heard of this.
When you did the @@version on each node (whil it was active) what did you get?
Just to confirm that you have a single instance active/passive cluster so once the instance is patched (master, msdb, model etc), all that is left is local services and the client.
So what is not patched? Please list the services/objects that didnt patch. (maybe a log if you still have them).
Adam Zacks-------------------------------------------Be Nice, Or Leave
August 13, 2009 at 2:28 am
Adam,
I have three instances in active / passive cluster setup.
The current version is as follows
Node1 Node2
instance1 3042 4035
instance2 3042 4035
instance3 4035 4035
This is strange no?
All client components are patched.
August 13, 2009 at 2:54 am
joeroshan (8/13/2009)
Node1 Node2instance1 3042 4035
instance2 3042 4035
instance3 4035 4035
This is strange no?
Yes very starnge. Can you do the following as a test:
Test1:
Node1 - Instance1 (active) - Patch
Node2 - Instance 2/3 (active)
Test2:
Node1 - Instance2 (active) - Patch
Node2 - Instance1/3 (active)
This way we are only trying to patch one instance at a time. Once done re-do your tests and let me know. Also please attach any patch summary logs.
Adam Zacks-------------------------------------------Be Nice, Or Leave
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply