RE: Need help with proper cluster node uninstall...help needed!!

From: Uttam Parui[MS] (uttamkp_at_online.microsoft.com)
Date: 01/17/05


Date: Mon, 17 Jan 2005 22:58:13 GMT

You will need to remove the node (node B in your case) from the existing SQL Server 2000 virtual Failover Cluster by following these steps:

1) Run SQL Server 2000 EE Setup on the node where SQL Server is currently running. So, if it is running on Node A then run the setup on Node A.

2) On the Welcome screen of the Microsoft SQL Server Installation Wizard, click Next.

3) On the Computer Name screen, click Virtual Server and specify the name of the server (i.e your SQL Server network name/virtual name) from which to remove the node. Click Next.

4) 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.

5) On the Installation Selection screen, click Advanced Options. Click Next.

6) On the Advanced Options screen, click Maintain a virtual server for failover clustering. Click Next.

7) On the Failover Clustering screen, click Next. You do not need to modify any IP address(es).

8) On the Cluster Management screen, select the node (i.e. node B in your case) and click Remove. Click Next.

9) 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.

10) On the Setup Complete screen, click Finish.

NOTE: 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.

Once this is complete, you will have a single node SQL Server 2000 virtual instance.

Best Regards,

Uttam Parui
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx



Relevant Pages

  • RE: Problems upgrading SQL MSDE for Sharepoint
    ... Please try the following steps and then run the SQL Server 2000 setup again: ... Can we install SQL Server successfully at this time? ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: x64 2003 Cluster - SQL2000 named instance fail
    ... one the settings are not detected by the setup. ... > in the cluster log you will notice the a connection to the SQL Server ... > named instance cannot be established. ... >> Microsoft highly recommends that users with Internet access update their ...
    (microsoft.public.sqlserver.clustering)
  • RE: Action Pack SBS 2003 R2 Premium DVD: installing SQL Server 2005
    ... Microsoft CSS Online Newsgroup Support ... <SQL Server 2005 will not install using the setup page for the Premium ...
    (microsoft.public.windows.server.sbs)
  • RE: migrating from wmsde to sql server
    ... I understand that the SQL Server 2000 Setup Control ... > Microsoft CSS Online Newsgroup Support ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: weird sql server 2000 setup problem
    ... Its possible that some unnecessary service is affecting the setup. ... Before you begin the installation process, ... For a complete list of supported hardware, visit the following Microsoft Web site: ... *You have disabled NetBIOS for all private network cards before you start the SQL Server Setup program. ...
    (microsoft.public.sqlserver.clustering)

Loading