Tips of manually reinstall SQL Server 2000 Cluster instance

If the SQL Server Cluster instance is incompletely reinstalled or the SQL cluster resource is manually removed by mistake, we have to manually remove the installed SQL Server cluster instances and reinstall them again.

1. Before remving the origninal SQL cluster instances, please make sure:
a. Backup the Data foldr on the shared disk. This step is making you physically back up the original databases and will not have data loss after completely reinstallation.
b. Please run the following command to record your current SQL Server version.
Select @@version

2. To manually remove all SQL clsuter instance, we perfomed the steps on both nodes mentioned:
 a. Locate, and then delete the %drive%:/Program Files/Microsoft SQL Server/MSSQL/Binn folder (inclusing local disk and shared disk).
 b. Locate, and then delete these registry keys:
*HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/MSSQLServer
*HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft SQL Server
 c. Locate, and then delete these registry keys:
*HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSSQLServer
*HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/SQLSERVERAGENT
*HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSSQLServerADHelper

The three registry keys in step 3 correspond to the default instance of Microsoft SQL Server 2000. Named instances appear similar to those listed in step 3, along with $instance_name, because instance_name is the name given to your particular instance. After you locate the correct keys for the instance you are removing, select those keys, and then delete them.

* HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSSQLServer$InstanceName
* HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/SQLSERVERAGENT$InstanceName
* HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MSSQLServerADHelper
 d. If the instance of SQL Server you are removing was clustered, remove any cluster resources for the instance that may remain in the Cluster Administrator. SQL Server setup program willl create SQL IP address and SQl network Name resources automatically.

For more information, please refer to:
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/default.aspx?scid=kb;en-us;290991

3. We also removed MSSerch registries from both nodes to make sure the SQL Server cluster installation process will not be blocked by remaining registries of previous installation.
a. Delete the registry keys that are related to the instance of SQL Server where the full-text search will be reinstalled. To do so, follow these steps.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

a). Click Start, and then click Run.
b). In the Run dialog box, type regedit in the Open box, and then click OK. 
c). In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE/Software/Microsoft/Search/Install/Applications
d). In the right pane, delete the registry values that have the same name as your instance of SQL Server. For a default instance of SQL Server, the registry value is named SQLServer. For a named instance of SQL Server, the registry value is named SQLServer$ Instance Name .
b. If the MSSearch search service does not start on the node of your SQL Server cluster and you want to reinstall the full-text search service on the node, you must also remove the registry entries for a clean removal of the full-text search service. To do so, remove the following registry keys on both nodes of the SQL Server cluster:

*HKEY_LOCAL_MACHINE/Software/Microsoft/Search
*HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/MSSCNTRS
*HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/MSSEARCH 
*HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/MSSGATHERER
*HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/MSSGTHRSVC
*HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/MSSINDEX
 
-------------After removing operations, we need to reboot both nodes

4. Performed the following steps to stop all non-NT services during the installation on both nodes.

Stop all the non-default NT services, especially:
     a. Any anti-virus Services
     b. IIS Admin and WWW Service
     c. FTP Publishing
     d. One Point
     e. Microsoft Office Manager (MOM)
     f. Windows Management Instrumentation (WMI) Service

Essential Windows NT and Windows 2000 services include:

       - Alerter
       - Computer Browser
       - EventLog
       - License Logging
       - Messenger
       - Net Logon
       - NT LM Security Support Provider
       - Plug and Play
       - Protected Storage
       - Remote Procedure Call (RPC)
       - Server
       - Spooler
       - TCP/IP NetBIOS Helper
       - Workstation

5. Closed all unnecessary applicatons on the active node of the cluster system. expecially, SQL Server utilites. For example, service management, enterprise manager.
6. Make sure the Cluster service startup account and SQL Server service account are in the local administrator group in both nodes.
7. Using a domain account to login to the action node for installation. This domain account should be in local administrator group in both nodes as well.
8. Make sure all disk resources in the cluster should be online during SQL Server cluster installation.
9. We registered the gathercl.dll file from both nodes to make sure the dll is registred correctly. For more information, please refer to:
http://support.microsoft.com/default.aspx?scid=kb;en-us;KB811024
10. For each named instance installation for SQL cluster, please create a named piple alias as we the following articles mentioned then try to run the SQl setup program. For more informaiton, please refer to:
http://support.microsoft.com/default.aspx?scid=kb;en-us;815431

11. Then we performed the general setps to complete SQL Server cluster instance installation. Please refer to:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#EEAA

Thanks and regards,
Michael