INF: Frequently Asked Questions - SQL Server 7.0 - SQL Setup
This article was previously published under Q195759
This article has been archived. It is offered "as is" and will no longer be updated.
This article is meant to address frequently asked questions regarding the setup and installation of SQL Server 7.0.
- Q. What are the minimum hardware requirements for installing SQL Server 7.0?
A. SQL Server 7.0 requires the following minimum hardware:
- Computer: DEC Alpha AXP and compatible systems, or Intel or compatible (Pentium 166 MHz or higher, Pentium PRO, or Pentium II)
- Memory: 32 MB of RAM
- Disk Drive: A CD-ROM drive, plus a hard disk drive with at least 80 MB of free disk space for a minimal installation. The following table shows the minimum amounts of disk space required for the different installation types:
Installation option Disk space Full 210 MB Typical 185 MB Management tools 90 MB Minimum 80 MB
- Q. What are the installation limitations of installing SQL Server 7.0 Desktop Edition on a computer running Windows 95 or Windows 98?
A. The following features of SQL Server 7.0 Desktop are not available on a computer running either Windows 95 or Windows 98:
- Incoming named pipe connections
- Windows NT Authentication
- Asynchronous I/O
- Transaction-based publishing
- Full text search
- Automatic detection of Unicode files
- Q. Can I install SQL Server if the Windows NT machine name contains a hyphen (-)?
A. Yes, SQL Server now supports all machine names that are valid under Windows NT.
- Q. When I try to start SQL Server 7.0 on Windows NT or from a Windows 9x Command prompt, I receive the following error: Your SQL Server installation is either corrupt or had been tampered with (unknown package id) Please rerun setup.When I attempt to start SQL Server 7.0 on Windows 9x using the SQL Server Service Manager, nothing happens. What causes this and how can I resolve it?
A. This error message appears if you have renamed the Windows computer on which you installed SQL Server 7.0. SQL Server 7.0 uses the Windows computer name internally; if you change the Windows computer name, SQL Server detects a different name and generates the error message.
NOTE: Your data has not been corrupted or damaged in any way.
To resolve this error and start SQL Server again, do either of the following:
- Run SQL Server 7.0 Setup from the original product CD. Doing so will not reinstall SQL Server or any components; however, it will update SQL Server 7.0 internally to reflect the new Windows computer name. You also need to update SQL Server's internal servername by running the following two stored procedures: If SQL Server is configured to listen on either the Multiprotocol or NWLink IPX/SPX network libraries, you'll need to remove them, and then add them back using the SQL Server Network Utility.
sp_dropserver <old_name> go sp_addserver <newname>, local go
- Change the Windows computer name back to the original name it had when you first installed SQL Server 7.0.
- Run SQL Server 7.0 Setup from the original product CD. Doing so will not reinstall SQL Server or any components; however, it will update SQL Server 7.0 internally to reflect the new Windows computer name. You also need to update SQL Server's internal servername by running the following two stored procedures:
- Q. Can I install SQL Server 7.0 on a server that already has SQL Server 6.x installed?
A. Yes, but you cannot run both SQL Server 6.x and SQL Server 7.0 at the same time. SQL Server Setup adds a version switch, which you can use to switch between SQL Server 6.x and SQL Server 7.0.
CAUTION: If you are installing SQL Server 7.0 alongside SQL Server version 6.x on the same computer, do not install SQL Server 7.0 in the same directory as SQL Server 6.x.
- Q. How can I order a printed copy of the SQL Server Books Online?
A. To order the 12-volume set of SQL Server product documentation, call toll-free (800) 360-7561. The Part Number for the documentation is 228-00340. The content is identical to the SQL Server 7.0 Books Online that is included in the SQL Server 7.0 product CD.
- Q. How can I install only the SQL Server Books Online?
A. You can select only the SQL Server Books Online as an option in Custom Setup. Also, you can run the SQL Server Books Online without installing it on the computer by selecting it from the Autorun menu.
- Q. How do I install just the client and Profiler?
A. In Custom Setup, select the Client Connectivity and Profiler options.
- Q. Do I need Microsoft Internet Explorer 4.01 Service Pack 1 to install only the client connectivity tools on my clients?
A. No. If you want to install only the client connectivity tools, you do not need Internet Explorer 4.01 Service Pack 1. However, if you intend to install the management tools or the SQL Server 7.0 Books Online, you do need Internet Explorer 4.01 Service Pack 1.
- Q. Why do I get the following error message when I try to install the client connectivity tools on a computer running Windows 95? Based on your selection setup has determined the following systems requirements are not met. Exit setup and install the missing requirements from the CD or change your selections. Distributed Component Object Model (DCOM) for Microsoft Windows 95
A. This message occurs if the required DCOM components are not installed on your Windows 95 computer. You can install DCOM from the SQL Server 7.0 CD. To do this and continue with SQL Server 7.0 Setup, perform the following steps:
- Browse the SQL Server 7.0 CD and locate the Processor_Type\Other folder, where Processor_Type is your computer's type of architecture (for example, Alpha or Intel x86).
- Run the Dcom95.exe executable file.
- After you have finished installing DCOM for Windows 95, restart your computer and then run SQL Server 7.0 Setup again.
- Q. Can I perform a remote installation?
A. Yes. The first screen of SQL Server Setup gives you the option to do a remote installation, but note that all prerequisites must first be installed on the remote computer.
- Q. How do I invoke an unattended setup?
A. To invoke an unattended installation, you must first generate an .iss file. You can create this file by starting SQL Server Setup with the -r option and then going through Setup and interactively making the selections you want. After the installation completes successfully, you will have a Setup.iss file in your Windows directory. You can copy or move this file to another location if you want. On subsequent installations, you can start SQL Setup and specify a previously generated .iss file as input by using the -f1 setup command-line option.
- Q. When I run SQL Server Setup, why do I get an error asking me to close all ODBC components?
A. SQL Server 7.0 Setup installs Microsoft Data Access Components (MDAC) 2.1, 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 Server, Microsoft System Management Server, Microsoft Access, and ORACLE.
- Q. Whenever I type information into a dialog box, click Back, and then click Next again, the information that I originally typed in the dialog box is lost. Why does this happen?
A. This is currently a limitation of InstallShield dialog boxes.
- Q. What do I need to do if I have an unsuccessful installation?
A. If you have an unsuccessful installation of SQL Server 7.0, there are several files that can help you determine what went wrong. The first file is the Sqlstp.log file in the Windows directory. The Sqlstp.log file gives detailed information on what Setup is doing. Reviewing this file will give you an idea of where Setup is failing.
If the Setup process is failing in the Configuration part, review both the SQL Server error log in the MSSQL7\Log directory and the Cnfgsvr.out file in the MSSQL7\Install directory. SQL Server Setup runs an application called 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 Cnfgsvr.out file. When SQL Server starts, it generates an error log that contains errors SQL Server may encounter. This file, called errorlog, is in the MSSQL7\Log directory.
If you are unable to determine the cause of the Setup failure, save the files mentioned above and call Microsoft Product Support Services to contact a SQL Server Support Professional, who will help you to resolve your problem. Note that if the Setup application fails, it will roll back changes to the file system, including removing any copied files, and also remove changes to the registry.
- Q. Why does Microsoft Distributed Transaction Coordinator (MS DTC) activate my dial-up service to the Internet when I start (or restart) my computer?
A. By default, MS DTC is configured to start automatically when a Windows NT or Windows 98 system starts. To prevent MS DTC from automatically starting after restarting a Windows 98 computer, you can make a change to the system registry.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756 How to back up and restore the registry in Windows
To prevent MS DTC from automatically starting, use Registry Editor to find the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices key.
When you find this key, you can delete the value entry named MSDTC. If you want to enable automatic startup of MS DTC again, use Registry Editor to create a value entry named MSDTC with the string value msdtcw -start under the registry key noted above.
- Q. Is it possible to have SQL Server start automatically on computers running Windows 95 or Windows 98?
A. Yes. In the SQL Service Manager there is an option called AutoStartService When OS Starts.
- Q. How do I uninstall SQL Server 7.0?
A. To uninstall SQL Server 7.0, use any one of the following options:
- On the Start menu, point to Programs, point to Microsoft SQL Server 7.0, and click Uninstall SQL Server 7.0.
- Use Add/Remove Programs in Control Panel to remove SQL Server 7.0.
- Run a scripted uninstall.
- Q. How do I start an unattended uninstallation?
A. When SQL Server 7.0 is successfully installed, an uninstall script file, Uninst.isu, is created. This file is located in the directory you specified for your program files. To start an unattended uninstallation, run the UnInstallShield executable, Isuninst.exe, and point it at your uninstall script file.
- Q. How do I rebuild the master database?
A. There is a new utility to rebuild the master database. It is called Rebuildm.exe, and it is located in the Mssql7\Binn directory.
NOTE: Rebuilding the master database also rebuilds the Model and MSDB databases as well.
- Q. How do I rebuild the registry?
A. There is a new utility to rebuild the registry entries for SQL Server 7.0. This utility is called Regrebld.exe, and it is located in the Mssql7\Binn directory.
After SQL Setup ends, the registry is rebuilt automatically using Regrebld.exe. This utility creates an image of all the SQL Server registry entries, with file names of Mssql7*.rbk.
Running Regrebld.exe with the -Restore option places the registry key images into the registry. If the keys already 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, it will also rebuild the SQL Server icons.
- Q. How do I reconfigure my server network protocols?
A. In the SQL Server program group, there is a new utility called the Server Network utility. You can use it to reconfigure your server network protocols.
- Q. Why do I have to close the SQL Service Manager before I uninstall?
A. You must shut down the SQL Service Manager to ensure that no SQL Server-related services are running. In earlier versions of SQL Server, Setup would attempt to shut down these services, but it was unable to completely guarantee success.
- Q. Why does the final uninstall report always state that it cannot remove folders?
A. The UnInstallShield installer only removes what it installs. Some files, such as tempdb, are created outside the bounds of the InstallShield installation routine. When the InstallShield uninstaller runs, it tries to delete the folders that it created (MSSQL7, Binn, Data, and Log) and finds that these folders are not empty. However, the .dll file that is run after UnInstallShield is complete (Sqlsun.dll) removes files such as Tempdb and these folders.
NOTE: Any error logs, trace files, or user data that may remain in these directories are not removed.
- Q. I receive one the following error messages when trying to install SQL Server 7.0. What do these messages mean?The Enterprise Edition server component cannot be installed on Windows NT Server using this CD. Only client components will be available for installation.-or-The Standard Edition server component cannot be installed on Windows NT Workstation using this CD. Only client components will be available for installation.-or-The Standard Edition server component cannot be installed on Windows 98 using this CD. Only client components will be available for installation.-or-The Standard Edition server component cannot be installed on Windows 95 using this CD. Only client components will be available for installation.-or-The Enterprise Edition server component cannot be installed on BackOffice Small Business Server using this CD. Only client components will be available for installation.A. Any of the preceding messages indicate that you are attempting to install a version of SQL Server 7.0 that is not supported on the operating system on which you are attempting the install. In order to successfully install SQL Server, select the appropriate SQL Server edition for the operating system you are running.
SQL Server 7.0 has the following editions available for the operating systems noted:
- SQL Server 7.0 Enterprise Edition: This edition may only be installed on a computer running Microsoft Windows NT Server Enterprise Edition.
- SQL Server 7.0 Standard Edition: This edition may be installed on a computer running Microsoft Windows NT Server, Windows NT Server Enterprise Edition, or Microsoft BackOffice Small Business Server.
- SQL Server 7.0 Small Business Edition: This edition may only be installed on a computer running BackOffice Small Business Server.
- SQL Server 7.0 Desktop Edition: This edition may be installed on a computer running Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows NT Workstation, Windows NT Server or Windows NT Server Enterprise Edition.
- Q. How do I upgrade from SQL Server 7.0 Beta 3 to the released version of SQL Server 7.0?
A. If you currently have the Beta 3 version of Microsoft SQL Server 7.0 on your computer, you can upgrade the installation to SQL Server version 7.0 rather than uninstall the Beta version and install a clean copy of SQL Server.
The benefit of upgrading from the Beta 3 version is that SQL Server retains the system and user databases, saving you the time involved in re-creating system settings and reloading data.
- Q. Why won't SQL Server 7.0 install on a computer that has a Cyrix chip installed?
A. Older versions of Cyrix chips to not support the complete Pentium instruction set. SQL Server 7.0 makes use of some of these instructions so the Setup program detects and refuses to install on those older chips.
- Q. Can I manage SQL Server 6.5 databases from a SQL Server Enterprise Manager 7.0?
A. Yes, you can if you had previously installed the SQL Server 6.5 utilities on your client computer and upgraded it to version 7.0. When you attempt to connect to SQL Server 6.5 using the SQL Server Enterprise Manager 7.0, it will open the 6.5 version of SQL Enterprise Manager.
- Q. Which SQL Server 6.5 service pack is required to upgrade?
A. Service Pack 3 or greater is required in order to switch back and forth between the two versions, although Microsoft Product Support Services recommends that you be on the latest service pack.
- Q. Can I install SQL Server 7.0 on a server running Windows NT 4.0, Terminal Server Edition?
A. SQL Server 7.0 is supported on Windows NT 4.0 Terminal Server Edition after SQL Server 7.0 Service Pack 1 is installed.
- Q. Can I run multiple copies of SQL Server at the same time on one computer?
A. No, except if you have an active/active failover configuration hosting separate SQL Server 7.0 virtual servers on a Microsoft Cluster Server (MSCS) and one of the nodes fails.
Although you can use the SQL Server 7.0 Vswitch.exe utility to switch back and forth between a single copy of SQL Server 6.5 and a single copy of SQL Server 7.0 on one computer, only one version can be active at a time. This utility was not intended to allow both versions to be actively used on a server; it was intended to provide you with the ability to switch from one version to another when necessary.
- Q. What do I do if my SQL Server 7.0 Beta 3 license expires before I have an opportunity to upgrade to the release version of SQL Server 7.0?
A. If your SQL Server 7.0 Beta 3 installation has expired before you have upgraded to the release version of SQL Server 7.0, you should perform the following steps:
- Back up all the .mdf, .ndf, and .ldf files from the Mssql\Data directory of your Beta 3 installation by copying them to another directory or other safe location.
- Use the Add/Remove Programs utility in Control Panel to remove your Beta 3 installation.
- Install the release version of SQL Server 7.0.
- Use the sp_attach_db stored procedure to reattach your databases. For more information on sp_attach_db, see the SQL Server 7.0 Books Online.
- Q. Can I upgrade the Evaluation version to the retail version?
A. For additional information, please click the article number below to view the article in the Microsoft Knowledge Base:237303 INF: Upgrading From SQL Server 7.0 Evaluation to Retail Version
faq prodsql IE SP SP1 sqlfaq dash Shield RTM rename
Article ID: 195759 - Last Review: 12/05/2015 09:43:03 - Revision: 8.0
Microsoft SQL Server 7.0 Standard Edition
- kbnosurvey kbarchive kbinfo KB195759