Installing SP4 on New node in cluster on Win2K3

We have a single node cluster using SQL2K EE running on Win2K EE, and this
has been running fine for a year or so. We finally have our new data centre
completed, and the additional hardware installed for us to install the second
node.
1) I installed Cluster services and added the second node to the cluster.
2) Ran COMClust to add DTC as a cluster resource
3) On the Active Node installed SQL2K, and selected advanced options,
Maintain SQL Server . . . .
4) Checked SQL Server resources in Cluster Manager, every thing looks good.
5) Tried to install SP4 from the new passive node - Failed doesn't own
resources in the Cluster
6) Tried installing SP4 from the active node . . . Got a bit further but the
install fails with a 'Setup was unable to complete the operation on all nodes
in the cluster'
At this point I am really stumped Looking at the SQLSP.log file it ends with
16:38:12 Begin SDPassword Dialog
16:38:12 Begin: CheckSAPassword
16:38:12 WARNING : No Blank SA Pwd
16:38:12 End: CheckSAPassword
16:38:12 Begin: SdShowSp3WrngDlg
and searching the net threw up a reference to this
http://support.microsoft.com/kb/815431/] KB article. Although this is not
strictly relevant I am wondering if there is an issue with installing a non
SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
what SP level its at and rejecting it as it doesn't have SP3 Installed.
So then What I did, was to try failing the cluster over so that I could
apply the fix from the new node. While the cluster group fails over, the SQL
group makes and attempt, but then SQL Server fails to start and it all fails
back to the other node.
I then removed SQL Server (from the active node) on the Passive node.
Rebooted the new passive node, and Installed SQL2K SP3a on the new node
successfully. I then tried to install SP4 (From the Active Node), and that
failed with the same error.
Any one have any Ideas?
Regards
Tony
Slipstream sql server sp4 and then try to do the install from the active
node. Also make sure that nobody else is logged onto the active and passive
nodes.
AS
"BC DBA" wrote:

> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data centre
> completed, and the additional hardware installed for us to install the second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but the
> install fails with a 'Setup was unable to complete the operation on all nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the SQL
> group makes and attempt, but then SQL Server fails to start and it all fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
|||16:38:12 Begin: SdShowSp3WrngDlg
Yes, this is your problem. However, you've indicated that you are running
on Win2K EE, which doesn't exist (only Advanced Server), plus, this security
dialog only presents itself on a Windows Server 2003.
So, let's assume that you are running Windows 2000 Advanced Server on the
active (original) node and Windows Server 2003 EE on the new node.
Your steps through the installation process is correct; however, you will
need to get the new node to the same SP level as the old before the cluster
will successfully move resources to the new node.
There are three issues. The dialog above requires you to apply SP3 or later
before resources will run on new node; however, there is a bug in the SP4
installation package that misreads the new 4 digit Build number 2039 as 203
or 039, both of which are less than the 760 Build for SP3.
You must run service packs from the node that currently owns the cluster
resources, and since you cannot move resources to the new node yet, you must
reapply SP3 on the active (original) node. The installation will detect
that it will be a Binary Only installation to the new node.
Lastly, there is one other security issue in that until the new node has
been updated to SP3, TCP/IP protocol has been disabled. To work around this
issue, on BOTH cluster nodes, you must create NAMED PIPE aliases to the
Virtual SQL Server instance. Since the RTM installation uses this protocol,
this issue does not occur, but it does for any SP installations.
Once SP3 has been applied, you will still not be able to move resources to
new node. You must reapply SP4 plus any additional hot fixes. If you use
AWE, you will definitely want to apply the 2040 HF; moreover, you may want
to consider applying the latest publicly available HF, as it is the most
current build supported, Build 2187.
After this, you should be able to move resources successfully between both
nodes; however, Microsoft only limitedly supports mixed cluster
environments. At this point, you should uninstall the original node from
the cluster, evict the node, and rebuild it as a Windows Server 2003
installation. Then, you will need to follow the procedures above to
reintroduce this node as a clustered member. (As an aside, on Win2K3, you
do not have to run the COMCLUST utility anymore).
One final word of advice, SQL Server 2000 mainstream support expires in
April 2008. You should seriously consider upgrading to SQL Server 2005 as
soon as possible. Moreover, CTP2 for SQL Server 2008 was just released in
this month, with a target EOY 2007 1st QTR 2008 launch expectation, which
means even SS2K5 mainstream support does not have a long expected lifespan.
So, get moving.
Sincerely,
Anthony Thomas

"BC DBA" <BCDBA@.discussions.microsoft.com> wrote in message
news:88FBFA1A-2239-4E19-833F-83A55858ACCC@.microsoft.com...
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data
centre
> completed, and the additional hardware installed for us to install the
second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks
good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but
the
> install fails with a 'Setup was unable to complete the operation on all
nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends
with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a
non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to
see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the
SQL
> group makes and attempt, but then SQL Server fails to start and it all
fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony