I have a active/passive cluster with W2K Adv. and SQL 2000.
I was having the issue with setting up SQL on the second node. I fixed issue by installing directly onto the second node. But their is no option with the sp3a to install onto the second node locally. The same issue that happened with trying to remote install with the primary node. The install failed because of a timeout issue. Error 121. All of my settings and correct accounts are setup. The person who told me to install directly on the second node to
install SQL stated that this was actually a known problem. What is the fix for the service packs if you cannot install remotely? It looks like sp3a installed correctly because when I ran query analyzer the version that showed up was sp3a. Any comments would be appreciated.

Thanks,
dcaldwell


---
Posted using Wimdows.net NntpNews Component -

Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

There is no 'first node' and 'second node' concept in SQL 2000 clustering.
All nodes are equal. The only difference is what node is currently hosting
the instance. Adding and removing nodes is a different process and is well
documented in BOL. It sounds like you built the cluster on a single node or
applied the service pack with one node offline. Normal installation of SQL
Service packs will update all nodes at the same time if it is run from teh
node currently hosting the instance. If you need to reapply a service pack
to update binaries on a newly added or replaced node, you must run the
Service Pack from the 'new' node while hte SQL instance is hosted on an
'old' node. This is documented in the Service Pack readme file.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"SqlJunkies User" <User@-NOSPAM-SqlJunkies.com> wrote

with the sp3a to install onto the second node locally. The same issue that
happened with trying to remote install with the primary node. The install
failed because of a timeout issue. Error 121. All of my settings and correct
accounts are setup. The person who told me to install directly on the second
node to
installed correctly because when I ran query analyzer the version that
showed up was sp3a. Any comments would be appreciated.

What do you mean by "I fixed issue by installing directly onto the second
node. "

Did you install a local, non-clustered installation on the second node?

Perhaps now is a time to uninstall that local copy, and reinstall back as a
virtual SQL Server. You can find a clustering installation white paper at:

http://www.microsoft.com/technet/pro.../failclus.mspx

Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.

This posting is provided "as is" with no warranties and confers no rights.