|Subject:||SP2 on a new node|
|Posted by:||Andrea Gallazzi (AndreaGallaz…@discussions.microsoft.com)|
|Date:||Thu, 20 Dec 2007|
I cannot install SP2 on a new node that was added after SP2 applied to the
We had the following scenarios. Node A SP2, node B RTM.
Scenario 1) Resources moved to node A (also MSDTC and Cluster group). Setup
running on node A.
Setup warns (even in log) "The product instance XXX been patched with more
Since it sees that local instance is patched, setup don't go on. I cannot
select any clusterized instance.
Scenario 2) Resources moved to node B (also MSDTC and Cluster group). Setup
running on node B.
12/18/2007 13:13:55.175 Exit code for passive node: XXXXA = 11203
12/18/2007 13:13:56.972 The following exception occurred: No passive nodes
were successfully patched Date: 12/18/2007 13:13:56.972 File:
12/18/2007 13:13:57.440 Watson: Param1 = Unknown
12/18/2007 13:13:57.440 Watson: Param2 = 0x2b01
12/18/2007 13:13:57.440 Watson: Param3 = Unknown
12/18/2007 13:13:57.440 Watson: Param4 = 0x0
12/18/2007 13:13:57.440 Watson: Param5 = instance.cpp@3422
12/18/2007 13:13:57.440 Watson: Param6 = Unknown
12/18/2007 13:13:57.440 Watson: Param7 = SQL9
12/18/2007 13:13:57.440 Watson: Param8 = Hotfix@
12/18/2007 13:13:57.440 Watson: Param9 = x64
12/18/2007 13:13:57.440 Watson: Param10 = 3042
I undertstand, he cannot patch an already patched node (A). Setup stops
ignoring local node. So... how can I just patch a single node (B)?
I read uninstalling Setup Support Files and reinstalling them will help
faking an RTM node to the setup, but during uninstall I got the following
warning "Warning 26002: The following product(s) is dependent on Microsoft
SQL Server Setup Support Files (English), the key will be brokenâ€¦" and it
lists one of our instances (just one). We will test it virtually, we cannot
afford loosing that instance.