Re: Can't get SQL 2000 installed on new node in Cluster
From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 05/11/04
- Next message: Billy: "RE: Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b"
- Previous message: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- In reply to: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- Next in thread: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- Reply: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 11 May 2004 13:44:14 -0400
Here are the necessary instruction cut directly from BOL:
----snip-----
How to remove a node from an existing failover cluster (Setup)
1.. On the Welcome screen of the Microsoft SQL Server Installation Wizard,
click Next.
2.. On the Computer Name screen, click Virtual Server and specify the name
of the server from which to remove the node. Click Next.
3.. You may see an error message saying that one (or more) of the nodes of
the Microsoft® Windows NT® 4.0 or Microsoft Windows® 2000 cluster are
unavailable. This may be because the node(s) you are attempting to remove is
damaged. The node(s) still can be removed. Click OK.
4.. On the Installation Selection screen, click Advanced Options. Click
Next.
5.. On the Advanced Options screen, click Maintain a virtual server for
failover clustering. Click Next.
6.. On the Failover Clustering screen, click Next.
You do not need to modify any IP address(es).
7.. On the Cluster Management screen, select the node and click Remove.
Click Next.
8.. On the Remote Information screen, enter login credentials for the
remote cluster node that has administrator privileges on the remote node(s)
of the cluster. Click Next.
9.. On the Setup Complete screen, click Finish.
If you are instructed to restart the computer, do so now. It is important
to read the message from SQL Server Setup when you are done with
installation. Failure to restart any of the specified nodes may cause
failures when you run the Setup program in the future on any node in the
failover cluster.
----snip-----
-- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org "Pat Hall" <anonymous@discussions.microsoft.com> wrote in message news:2893F359-FD01-49DB-8CB1-475BA25C4C5B@microsoft.com... > Uh Oh. > When I was working with MS Support they said all I had to do was evict the node from the cluster. They checked with SQL support before responding to me. All we did was evict the node from the cluster. When I go thru the procedure and get to the screen where I select the node to join the SQL cluster, I do not see the old node just the new node. > > Maybe I need to go back to MS Support for help in getting this straightened out. I didn't realize it would be this difficult. > > All ids involved meet the criteria you stated. > > Thanks for the info on SQL cluster still available whilie I add the new node to the SQL cluster. > > Pat Hall > Sr. DBA > Gilbarco Veeder-Root
- Next message: Billy: "RE: Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b"
- Previous message: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- In reply to: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- Next in thread: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- Reply: Pat Hall: "Re: Can't get SQL 2000 installed on new node in Cluster"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
