I have a SQL Server 2005 Cluster with SP2 and CU2 (KB936305 Build 3175)
Now I've added an additional Node. The Windows part went through like a
charm and the new node is recognized by the MSCS.
The addition of the new node to the SQL Server Ressource through
Add/Remove Programs (as described in SQL Books Online) installed the SQL
Server binaries from build 1399 (RTM) on the new node.
Starting SQL Server 2005 SP2 setup on the "new" node shows Database Engine
(1399) and offers the upgrade. It then first tries to update the passive
"old" node and failes with the errormessage: No passive nodes were
successfully patched, Exit Code Returned: 11009
Then the SP2 setup stops without updating the "new" node.
Re-Applying SQL Server 2005 SP2 on the "old" node is not possible as the
dialog states that the Database Engine (3175) is already newer.
Someone experienced the same and has a fix for this?
Regards
Daniel
**********************************************************************
This e-mail may contain confidential material. It is intended only for the person or entity which it is addressed to. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this e-mail in error, please immediately notify the sender or The Swiss Raiffeisen Group and delete the material from any and all computers it may be stored on. Any views or opinions expressed in this e-mail are those of the sender and do not necessarily coincide with those of The Swiss Raiffeisen Group. Therefore this e-mail does not represent a binding agreement nor an offer to deal. E-mail transmission cannot be guaranteed to be secure or error-free. Information could be intercepted, corrupted, lost, destroyed, incomplete or may contain viruses. Neither The Swiss Raiffeisen Group nor the sender can accept any liability for any kind of damage as the result of viruses or transmission errors.
**********************************************************************
MS Sql Server LazyDBA home page