Microsoft KB Archive/198680

= INF: Manually Removing SQL 6.5 After Failed Install =

Article ID: 198680

Article Last Modified on 10/26/2007

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q198680



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
The best way to remove SQL Server from a computer is by using the uninstall option in SQL Server Setup. However, after a failed installation, it is possible that the setup option may not be available. In this case, you need to get the system to a clean, stable install point before attempting to reinstall. The steps in this article will help you accomplish this.



MORE INFORMATION
IMPORTANT: If you currently have data that needs to be saved, before using the following steps, make sure you have a known good backup of the data or a copy of all data and log files that need to be saved in a directory other than the MSSQL directory tree.

To get the system to a clean, stable install point, you must first remove any possible conflicting software. Please see the following article in the Microsoft Knowledge Base for more details:

183692 PRB: SQL Server Setup Appears to Stop Responding

Next, verify through the Windows NT Event logs that no hardware problems are currently being detected.

Finally, use these steps to manually remove SQL Server 6.5:

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.

 Select Start, point to Settings, choose Control Panel, and then select Services. If either the MSSQLServer or SQLExecutive services are running, stop them. Use Regedt32.exe to remove the following keys in the registry:

HKEY_LOCAL_MACHINE Software Microsoft MSSQLServer HKEY_LOCAL_MACHINE System CurrentControlSet Services MSSQLServer HKEY_LOCAL_MACHINE System CurrentControlSet Services SQLExecutive

Remove MSSQLServer and SQLExecutive for each ControlSet key present under HKEY_LOCAL_MACHINE\System.

NOTE: It is possible that a ControlSet key may contain only one of the services, or neither service. The goal is to clean both the MSSQLServer and SQLExecutive services out of every ControlSet key, so delete either of the services present. Right-click My Computer:

 Choose properties. Select the Environment tab.</li> Select the path variable in the box below System Variables and review it in the box to the right of Value. Remove any references to the SQL Server directories from the path statement along with verifying there are no double semi-colons present. If double semi-colons are present, change them to single semi-colons .</li></ol> </li> Copy any .out files to a directory other than the MSSQL directory tree. These files can provide further information about the reasons for the failed setup; hence they should be examined thoroughly and all reported problems should be resolved before attempting to rerun setup.</li> Remove the SQL Server directory tree completely.</li></ol>

SQL Server should now be completely removed from the system.

Note that setup is based on a very specific install order, all server type applications must be installed first and all user applications must be installed last. For further information, please see the following article in the Microsoft Knowledge Base:

192710 INF: Installation Order for Windows NT Server and SQL Server

Keywords: kbproductlink kbinfo KB198680

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.