Setup and Installation FAQ

Troubleshooting SQL Server

previous page next page
Troubleshooting

Setup and Installation FAQ

What operating systems support SQL Server 2000?

Answer:

Operating system and other software requirements vary, depending upon the edition of SQL Server 2000 and the components that you choose to install. For more information, see Hardware and Software Requirements for Installing SQL Server 2000.

What are the minimum hardware requirements for installing SQL Server 2000?

Answer:

Hardware requirements vary, depending upon the edition of SQL Server 2000 and the components that you choose to install. For more information, see Hardware and Software Requirements for Installing SQL Server 2000.

Can I install SQL Server 2000 on a server that already has SQL Server 7.0 installed?

Answer:

Yes. You can install SQL Server 2000 as a named instance and run both SQL Server 7.0 and SQL Server 2000 at the same time.

How can I install only SQL Server Books Online?

Answer:

You can select the SQL Server Books Online option during a custom installation of SQL Server.

How do I install only the client and SQL Profiler?

Answer:

During a custom installation, under components, select Client Connectivity and Management Tools. With Management Tools selected, select Profiler under Sub-Components.

When I run SQL Server Setup, why do I get a message asking me to close all ODBC components?

Answer:

SQL Server 2000 Setup installs Microsoft Data Access Components (MDAC) 2.6, which installs newer ODBC components. Therefore, all applications that use ODBC must be shut down so that the MDAC installation can be successful. Applications that use ODBC include Microsoft Internet Information Services (IIS), Microsoft Systems Management Server, Microsoft Access, and Oracle database applications.

When installing SQL Server 2000 on a computer running Windows 98, Windows NT 4.0, or Windows 2000, do I need to install the Windows 95 Winsock2 update?

Answer:

No, you only need to install the Windows 95 Winsock2 update if you are planning to install SQL Server 2000 client connectivity components on a computer running Windows 95. Regardless of the platform on which you are installing SQL Server 2000, the Winsock2 update for Windows 95 will be listed when you select Install SQL Server 2000 Prerequisites during setup. However, this prerequisite applies only to computers running Windows 95, not to computers running Windows 98, Windows NT 4.0, or Windows 2000.

Can I install the MDAC 2.6 that comes with SQL Server 2000 without actually installing SQL Server 2000?

Answer:

Yes. MDAC 2.6 has a separate installation and can be installed without installing SQL Server 2000. Run the program Mdac_typ.exe located in the MSEQ\x86\ODBC directory on the SQL Server 2000 compact disc.

Is it possible to have SQL Server start automatically on computers running Windows 98?

Answer:

Yes. In the SQL Server Service Manager, there is an option called AutoStart Service When OS Starts that you can use to start SQL Server.

Can I perform a remote installation?

Answer:

Yes. The Computer Name screen of SQL Server Setup gives you the option of selecting the local computer, a remote computer, or, when installing clustering, a virtual server. All prerequisites must first be installed on the remote computer before beginning the installation.

Do I need Microsoft Internet Explorer 5.0 to install only the client connectivity tools on my clients?

Answer:

No. If you want to install only the client connectivity tools, you do not need Internet Explorer 5.0, but you do need Internet Explorer 4.01 with Service Pack 2. Note that if you intend to install the management tools or the SQL Server 2000 Books Online, you do need Internet Explorer 5.0.

What do I need to do if I have an unsuccessful installation?

Answer:

If you have an unsuccessful installation of SQL Server 2000, you can examine two files to help determine what the failure was. The first file is the Sqlstp.log file in the Windows directory. The Sqlstp.log file gives detailed information on what setup is doing and contains all errors encountered during setup. Reviewing this file will give you a better understanding as to where Setup is failing and why.

During the configuration portion of setup, SQL Server Setup runs an application named Cnfgsvr.exe to configure the SQL Server. This application starts SQL Server, connects to it, and runs the initial installation scripts. Any error encountered during this process is written to the Sqlstp.log file. In addition, you should review the SQL Server error log, named Errorlog with no file name extension, located by default in the Program Files\Microsoft SQL Server\Mssql\Log directory. This error log will contain errors that SQL Server encounters when setup attempts to start SQL Server.

If you are unable to determine the cause of the Setup failure, save the files mentioned earlier, and call Microsoft Product Support Services (PSS) to contact a SQL Server Support Professional who will help you to resolve your problem. If the Setup application fails, it rolls back all changes to the file system, including removing any copied files, and removes any changes that were made to the registry.

How do I rebuild the registry?

Answer:

To rebuild the SQL Server registry entries, run setup, select Advanced Options, and then select Rebuild Registry. Alternately, you can also use the Regrebld.exe utility, located in the Program Files\Microsoft SQL Server\Mssql\Binn directory by default.

After SQL Server Setup is finished, the registry is rebuilt automatically using Regrebld.exe. This utility creates an image of all the SQL Server registry entries with file names of Mssql*.rbk.

Running Regrebld.exe with the -Restore option places the registry key images into the registry. If the keys exist, they are replaced. If changes are made to the SQL Server installation after the initial setup, the backup copy of the registry keys is not updated automatically. If changes are made after installation, run Regrebld.exe manually to update the registry key information. If Regrebld.exe is run without any parameters, as is the case when performing a registry rebuild from the Setup menu, SQL Server program icons will also be rebuilt.

Why won't SQL Server 2000 install on a computer that has a Cyrix chip installed?

Answer:

Earlier versions of Cyrix chips do not support the complete Pentium instruction set. SQL Server 2000 makes use of some of these instructions, so the Setup program detects and refuses to install SQL Server on a computer with earlier versions of Cyrix chips.

Can I install SQL Server 2000 on a server running Windows NT 4.0, Terminal Server Edition?

Answer:

No. Currently, SQL Server 2000 is not supported on Windows NT 4.0 Terminal Server; however, it is supported on Windows 2000 Terminal Server.

previous page start next page