Troubleshooting SQL Server Setup
For immediate help in diagnosing your setup problems, see the new online setup troubleshooter on the Product Support Web site. For more information, see Help with Setup.
SQL Server Setup is designed to be as problem-free as possible; however, there may be situations that will interfere with the installation of Microsoft SQL Server 2000. The most common errors are simple to diagnose and resolve. The resolution may involve freeing up disk space, shutting down other applications, or restarting the computer to unlock shared files.
To avoid problems, be sure to review Preparing to Install SQL Server 2000. If you intend to install a SQL Server 2000 failover cluster, review Before Installing Failover Clustering before you run Setup.
If the installation fails, the Setup program might remove all installed components.
Before running the Setup program or installing additional SQL Server components, be sure to:
- Shut down all services.
Use Services in Control Panel to shut down the MSSQLServer and SQLServerAgent services. Shut down the MSSearch service if you installed Full-text Search. Shut down the MSDTC service if you installed MS DTC.
- Be sure the SQL Server Service Manager icon in the taskbar is closed.
Any attempt to run SQL Server Setup with the SQL Server Service Manager icon present (or any services still running) may cause Setup to fail.
- Remove the read-only attribute for all ODBC* files. On computers running Microsoft Windows NT® these files are located in the \System32 directory. On computers running Microsoft Windows® 95 or Microsoft Windows 98, these files are located in the system directory.
If you cannot remove the read-only attribute on the ODBC* files, SQL Server provides a dialog box that allows you to retry the updating of the ODBC* files.
- Understand that servers running Windows NT require Named Pipes. Cleaning named pipes during SQL Server installation does not prevent installation of named pipes. Because servers running Windows NT require named pipes, there is no way to uninstall Named Pipes on a server running Windows NT.