![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#3
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#4
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#5
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#6
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#7
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#8
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#9
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
#10
| |||
| |||
|
|
Hi, The error 'No passive nodes were successfully patched' is talked about in the kb below: http://support.microsoft.com/kb/929151 "Andrea Gallazzi" wrote: Hello, I cannot install SP2 on a new node that was added after SP2 applied to the primary. 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 recent updates." 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. Setup logs: 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: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sql sedll\instance.cpp Line: 3422 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. Thank you! Andrea |
![]() |
| Thread Tools | |
| Display Modes | |
| |