Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

SP2 on a new node

  
   Database Forums (Home) -> Clustering RSS
Next:  makepipe and readpipe on cluster  
Author Message
Andrea Gallazzi

External


Since: Dec 20, 2007
Posts: 2



(Msg. 1) Posted: Thu Dec 20, 2007 2:41 am
Post subject: SP2 on a new node
Archived from groups: microsoft>public>sqlserver>clustering (more info?)
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\sqlsedll\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

 >> Stay informed about: SP2 on a new node 
Back to top
Login to vote
RichardT

External


Since: Apr 23, 2007
Posts: 7



(Msg. 2) Posted: Thu Jan 03, 2008 10:14 pm
Post subject: RE: SP2 on a new node [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
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\sqlsedll\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

 >> Stay informed about: SP2 on a new node 
Back to top
Login to vote
RichardT

External


Since: Apr 23, 2007
Posts: 7



(Msg. 3) Posted: Fri Jan 04, 2008 8:01 pm
Post subject: RE: SP2 on a new node [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Hi Andrea,

Tried the fix below and it made no difference. Have you made any progress.

Thanks, Richard

"RichardT" wrote:

> 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\sqlsedll\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
 >> Stay informed about: SP2 on a new node 
Back to top
Login to vote
Andrea Gallazzi

External


Since: Dec 20, 2007
Posts: 2



(Msg. 4) Posted: Sun Jan 06, 2008 1:27 pm
Post subject: RE: SP2 on a new node [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
> Tried the fix below and it made no difference. Have you made any progress.

Already considered that way, but the issue is different.
We contacted Microsoft PSS and found together a solution.
You have to let the patch think it is a mono node (or at least that every
available nodes are RTM).
To accomplish this you have to edit the properties of every resource
(resource not group!) and remove every SP2 node from the availables.
In this way the patch will not contact that node and have no failure.
The workaround cause a loss of availableness if you will put only a single
node available... but, instead of rebuilding the whole cluster, it is an
accettable solution!
The same workaround will work with every hotfix.

I asked an MVP friend to write something about this issue, Microsoft told me
they will soon publish an article. Hope this will help a lot of peolpe!
Bye,

Andrea
 >> Stay informed about: SP2 on a new node 
Back to top
Login to vote
RichardT

External


Since: Apr 23, 2007
Posts: 7



(Msg. 5) Posted: Sun Jan 06, 2008 6:50 pm
Post subject: RE: SP2 on a new node [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Thanks Andrea, worked a treat

"Andrea Gallazzi" wrote:

> > Tried the fix below and it made no difference. Have you made any progress.
>
> Already considered that way, but the issue is different.
> We contacted Microsoft PSS and found together a solution.
> You have to let the patch think it is a mono node (or at least that every
> available nodes are RTM).
> To accomplish this you have to edit the properties of every resource
> (resource not group!) and remove every SP2 node from the availables.
> In this way the patch will not contact that node and have no failure.
> The workaround cause a loss of availableness if you will put only a single
> node available... but, instead of rebuilding the whole cluster, it is an
> accettable solution!
> The same workaround will work with every hotfix.
>
> I asked an MVP friend to write something about this issue, Microsoft told me
> they will soon publish an article. Hope this will help a lot of peolpe!
> Bye,
>
> Andrea
 >> Stay informed about: SP2 on a new node 
Back to top
Login to vote
MikeyTheMap

External


Since: Nov 18, 2009
Posts: 1



(Msg. 6) Posted: Tue Nov 17, 2009 2:25 pm
Post subject: RE: SP2 on a new node [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Thank you some much for the work around. Have not found it on MS site as
promised by MS.

url:http://www.ureader.com/msg/11421048.aspx
 >> Stay informed about: SP2 on a new node 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
4 node cluster - Has anyone set up a 4 node cluster i.e. 3 active and 1 passive ? I only want to consider this as it may reduce cost. We have a lot of servers and the least i want to do is have an active passive 2 node cluster for every server thus doubling the server...

2 node SQL 2005 cluster - I am new to clustering. I will be setting up a 2 node cluster using W2k3 EE and SQL 2005. I have a Dell PE 2850 and Dell PE 1850 for the servers, each containing one 73 GB HD and a PowerVault 220 with 4-73GB HD’s for the shared Drive. I am uncertain...

Node Eviction - HI, I need to evict one node from a two node, two instance SQL Cluster. Beyond failing over all resources and ownership to the surviving cluster node, is there any other configuration change I need to make in SQL server before doing this? Thanks. --...

One node Cluster for SQL 2005 - Hi anyone know if you can cluster sql on a one node cluster in Windows 2003 ? Regards Craig

Please Help - Restore Node - Hi All, I really need some guidance on how to restore this. Your help will be very much appreciated. Setup: 2 node clustering on Windows 2000 Advance Server with MS SQL 2000 Enterprise Edition. Diaster: Both the hard disks in the RAID 1 configuratio...
   Database Forums (Home) -> Clustering All times are: Pacific Time (US & Canada)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]