Push Binaries after installation SQL Server 2000 virtual server

I forget to set Client Network Utility to Create a Named Pipes Alias for
installation of a named instance of SQL Server 2000 virtual server on a
Windows 2003-based cluster fails to push binaries to the other node. SQL
Server 2000 virtual server installed fine on the present node but was unable
to push the binaries to the other node.
I have corrected the Named Pipes Alias problem. Is there away to push the
binaries to the other node that the cluster we recognize?
Thanks,
Treat it like a failed node. Run the installer to remove then re-add the
node. BOL topic 'Maintaining a Failover Cluster' has details.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:6F653B39-BBAA-4619-AEBA-3B8B6AD87037@.microsoft.com...
> I forget to set Client Network Utility to Create a Named Pipes Alias for
> installation of a named instance of SQL Server 2000 virtual server on a
> Windows 2003-based cluster fails to push binaries to the other node. SQL
> Server 2000 virtual server installed fine on the present node but was
unable
> to push the binaries to the other node.
> I have corrected the Named Pipes Alias problem. Is there away to push the
> binaries to the other node that the cluster we recognize?
> Thanks,
>
|||The need to create the named pipes alias has nothing to do with pushing the
binaries. Without the alias setup cannot connect to SQL Server to run the
necessary scripts. Without the alias I would be suspect that SQL Server
successfully installed on either node. I would run a complet setup again.
Rand
This posting is provided "as is" with no warranties and confers no rights.