Chapter 7 - Troubleshooting SQL Server 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. 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, make sure you complete all of the steps in "Before Installing: Checklist" in Microsoft SQL Server Introduction.

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/98, these files are located in the system directory. 

  If you cannot remove the read-only attribute on the ODBC* files, SQL Server produces 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. 

Setup Troubleshooting: Checklist

1. Read the error message. SQL Server Setup translates most error codes received from the operating system.

2. With the error dialog box showing, open Sqlstp.log in the \Windows or \WinNT directory. Check the last few events in the log to see if any problems occurred before the error message was generated. 

3. If this is a custom installation and the component that failed to install properly is the Full-text Search (MSSearch) service, check the Mssearch.log in the \Temp directory to see if any problems occurred. 

4. Continue past the error message dialog box. Some error messages are just warnings. The Setup program may still finish successfully. 

5. If the Setup program fails, and you cannot diagnose and fix the problem yourself, make a copy of Sqlstp.log and Setup.iss from the \Windows or \WinNT directory and, if you installed Full-text Search, make a copy of the Mssearch.log from the \Temp directory.

Note SQL Server Setup may encounter problems installing MS DTC on computers with multiple network cards or SPX installed. If SQL Server Setup stops responding, check the Sqlstp.log in the \Windows or \WinNT directory to see if MS DTC is being installed. If this is the problem, uninstall one of the network cards or SPX, and then retry SQL Server Setup.

Testing an Installation of SQL Server 7.0

Before a server installation is complete, SQL Server Setup starts and connects to the server multiple times. When the installation is complete, you can test the installation yourself and connect to it locally by running the osql utility from the server.

SQL Server Setup Frequently Asked Questions

Here are some of the frequently asked questions regarding SQL Server Setup.

What do I need to do if I have an unsuccessful installation or I find an error in the Setup program? 

If your installation fails and you are unable to determine the cause, or you find an error in the Setup program, find and save:

• The Sqlstp.log file, located in your \Windows or \WinNT directory. 

• The Setup.log files, located in your \Windows or \WinNT directory.

• Any other files left in the target program directory (by default, \Mssql7).

• The Cnfgsvr.out file located in the \Install directory of the target program directory (by default, \Mssql7\Install). 

• Any error logs located in the \Mssql7\Log directory.

If the Setup program fails, changes to the operating system are rolled back, including removal of any copied files and removal of changes to the registry.

Why aren't some directories deleted on uninstall? Why does the final uninstall report always report that it cannot remove folders? 

The UnInstallshield installer removes only what it installs.

Files created after installation is complete, such as tempdb, are not part of the installation record and will be unknown to UnInstallshield. Therefore, UnInstallshield is not able to remove these files or their associated directories. Sqlsun.dll, which runs after UnInstallshield is complete, removes files such as tempdb and their associated folders. Sqlsun.dll will not remove error logs, trace files, user data, or their associated folders if they are generated in the original directory structure.

See Also 

In Other Volumes 

"Running SQL Server Setup" in Microsoft SQL Server Introduction 

Informational Files Created by SQL Server Setup

These informational files are generated to locate any problems during setup:

• The Sqlstp.log file, located in your \Windows or \WinNT directory. For example, C:\WinNT\Sqlstp.log. 

• The most recent error log, located in the \Log directory of the target installation directory (by default, \Mssql7). For example, C:\Mssql7\Log\Errorlog. 

• The Cnfgsvr.out file, located in the Install directory of the target installation directory (by default, Mssql7). For example, C:\Mssql7\Install\Cnfgsvr.out. 

Contents of the Sqlstp.log file

If SQL Server Setup fails, locate and view the Sqlstp.log file. This file is located in your \Windows or \WinNT directory. For example, C:\WinNT\Ssqlstp.log.

This topic uses an Sqlstp.log file (generated from a Microsoft SQL Server installation on a server running Microsoft Windows NT) to illustrate the actions taken during an installation of SQL Server. The indentation, font variations, and spacing are for illustration purposes and are not representative of what you would see in the actual Sqlstp.log file. Comments have been added to aid in readability and appear as bold text inside parentheses.

In this log file, the Setup program:

1. Checks for prerequisites. Setup checks for Microsoft Internet Explorer version 4.0 and Windows NT version 4.0 with Service Pack 4 (SP4). 

   Note This information is provided for illustrative purposes only. Your values may vary. 

   17:54:00 Begin Setup
   

17:54:00 7.00.517 17:54:00 Mode=Normal 17:54:01 (Begin Action: CheckRequirements) 17:54:01 System: Windows NT Server Enterprise Edition (Detect operating system) 17:54:01 Version: 4.0.1381 17:54:01 SQL Server ProductType: Standard 17:54:01 Processor Architecture: x86 (Pentium) 17:54:02 Scatter Gather I/O check succeeded. (This is for the mini-service pack.) 17:54:02 Service Pack: 768 (Detects service pack.) 17:54:02 NT Mini-Service Pack has been detected 17:54:02 File Version - C:\WINNT\System32\shdocvw.dll: 4.72.2106.7 17:54:02 ComputerName: SEATTLE1 17:54:02 User Name: andrewf 17:54:02 Domain: ACCOUNTING 17:54:02 C:\TEMP_ISTMP29.DIR\odbcinst.exe -IsLocked -Silent 1 -SourceDir D:\sql97SRV\x86\ODBC -LogFile (Check to see if ODBC files are in use.) C:\WINNT\sqlodbci.log 17:54:03 Process Exit Code: (0) 17:54:03 OS Language: 0x409 17:54:03 End Action CheckRequirements 17:54:03 Begin Action: Detection 17:54:03 Previous SQL Server version: 65 17:54:03 Previous Version SQL Path: E:\MSSQL 17:54:03 Previous Version SQL Data Path: E:\MSSQL 17:54:03 C:\TEMP_ISTMP29.DIR\scm.exe -Silent 1 -Action 6 -Service SQLExecutive (Stop the SQLServerAgent service.) 17:54:08 Process Exit Code: (0) 17:54:08 C:\TEMP_ISTMP29.DIR\scm.exe -Silent 1 -Action 6 -Service MSSQLServer (Stop the MSSQLServer service.) 17:54:13 Process Exit Code: (0) 17:54:13 End Action Detection

2. Displays dialog boxes. 

   17:54:13 Begin Action: ShowDialogs
   

17:54:13 Begin Action: DialogShowSdWelcome (Welcome screen) 17:58:38 End Action DialogShowSdWelcome 17:58:38 Begin Action: DialogShowSdLicense (User Licence) 17:58:39 End Action DialogShowSdLicense 17:58:39 Begin Action: DialogShowSdRegisterUserEx 17:58:43 End Action DialogShowSdRegisterUserEx 17:58:43 Begin Action: DialogAskSvrOptions 17:58:45 End Action DialogAskSvrOptions

3. Chooses setup type and target directories.

   17:58:45 Begin Action: DialogShowSdSetupType (Choose setup type)
   

17:58:47 [SetupTypeSQL] 17:58:47 szDir=C:\MSSQL7 (Path for binary files) 17:58:47 Result=12 17:58:47 szDataDir=C:\MSSQL7 (Path for data files) 17:58:47 End Action DialogShowSdSetupType 17:58:47 Begin Action: DialogAskSvrOptions 17:58:48 End Action DialogAskSvrOptions 17:58:48 Begin Action: DialogShowSdSetupType 17:59:05 [SetupTypeSQL] 17:59:05 szDir=f:\mssql 17:59:05 Result=301 17:59:05 szDataDir=f:\mssql 17:59:05 End Action DialogShowSdSetupType

4. Selects components. 

   17:59:05 Begin Action: DialogShowSdComponentMult
   

17:59:05 End Action DialogShowSdComponentMult 17:59:05 Begin Action: DlgCpSortUnicode 17:59:05 Charset/SortOrder values obtained from existing server: 1252/52 (If upgrade, read sort order and char set) 17:59:06 [DlgCpSortUnicode] 17:59:06 SortId=52 17:59:06 LCID=1033 17:59:06 CompStyle=196609 17:59:06 Result=38147736 17:59:06 End Action DlgCpSortUnicode 17:59:06 Begin Action: DlgNetwork 17:59:06 [DlgServerNetwork] 17:59:06 NetworkLibs=4095 17:59:06 TCPPort=1433 (TCP/IP listen on port) 17:59:06 TCPPrxy=Default 17:59:06 NMPPipeName=\.\pipe\sql\query (Named pipe listen on connection) 17:59:06 Result=1194052 17:59:06 End Action DlgNetwork 17:59:06 Begin Action: DlgServices 17:59:09 [DlgServices] 17:59:09 Local-Domain=986895 17:59:09 AutoStart=61455 17:59:09 Result=1 17:59:09 End Action DlgServices

5. Begins file copy. 

   17:59:09 Begin Action: DialogShowSdStartCopy (Start copying files)
   

17:59:10 End Action DialogShowSdStartCopy 17:59:10 End Action ShowDialogs 17:59:10 Begin Action ProcessBeforeDataMove: 17:59:10 DeinstallStart returned (f:\mssql): 0 17:59:10 End Action ProcessBeforeDataMove: 17:59:10 Begin Action ProcessComponentSelection: 17:59:10 End Action ProcessComponentSelection 17:59:10 Begin Action LogSelectedComponents: 17:59:10 SQLProg 17:59:10 SQLProg\SQLServr 17:59:10 SQLProg\SQLServr\Help 17:59:10 SQLProg\UpgTools 17:59:10 SQLProg\UpgTools\UpgSys 17:59:10 SQLProg\ReplSupp 17:59:10 SQLProg\ReplSupp\ReplSys 17:59:10 SQLProg\ReplSupp\ReplDat 17:59:10 SQLProg\Install 17:59:10 SQLProg\System 17:59:10 SQLProg\SvrExt 17:59:10 SQLProg\SvrExt\Help 17:59:10 SQLProg\DTS 17:59:10 SQLProg\DTS\Help 17:59:10 SQLProg\Dat 17:59:10 SQLProg\DatSmpl 17:59:10 SQLProg\BaseSys 17:59:10 SQLProg\BaseBinn 17:59:10 SQLProg\BaseInst 17:59:10 MgtTool 17:59:10 MgtTool\SEM 17:59:10 MgtTool\SEM\HTML 17:59:10 MgtTool\SEM\MSD98 17:59:10 MgtTool\SEM\MSD98SYS 17:59:10 MgtTool\SEM\MSD98Res 17:59:10 MgtTool\SEM\MSD98Hlp 17:59:10 MgtTool\SEM\Help 17:59:10 MgtTool\Profiler 17:59:10 MgtTool\Profiler\Help 17:59:10 MgtTool\Qryanlz 17:59:10 MgtTool\Qryanlz\Help 17:59:10 MgtTool\DTCCLi 17:59:10 MgtTool\Wzcnflct 17:59:10 MgtTool\Wzcnflct\Wzcnsys 17:59:10 MgtTool\Wzcnflct\WzcnHlp 17:59:10 MgtTool\UtilSys 17:59:10 MgtTool\UtilBinn 17:59:10 Connect 17:59:10 Connect\ConnSys 17:59:10 Connect\ConnBinn 17:59:10 Books 17:59:10 Books\Bookso 17:59:10 Books\BooksCD 17:59:10 Core 17:59:10 CoreSys 17:59:10 ODBC 17:59:10 OLEDB 17:59:10 Repostry 17:59:10 RepstSys 17:59:10 CoreMisc 17:59:10 Jet 17:59:10 NetCore 17:59:10 NetExt 17:59:10 CoreInst 17:59:10 End Action LogSelectedComponents 17:59:10 Begin Action MoveFileData: 17:59:10 Begin Action: Overwrite6xCliLibs 17:59:10 End Action Overwrite6xCliLibs 18:01:30 End Action MoveFileData 18:01:30 Begin Action ProcessAfterDataMove: 18:01:30 DeinstallSetReference (f:\mssql\sqlservr.exe) returned: 0 18:01:30 End Action ProcessAfterDataMove

6. Installs packages. 

   18:01:30 Begin Action InstallPkgs:
   

18:01:31 Setup is installing Microsoft Data Access Components (MDAC) ... 18:01:31 K:\sql97SRV\x86\Other\mdac_201.exe /q:a /c:"setup.exe /qtn" 18:02:00 Process Exit Code: (0) 18:02:00 Setup is installing Microsoft Management Console (MMC) ... 18:02:00 K:\sql97SRV\x86\Other\instmmc.exe /q:a /r:n 18:02:12 Process Exit Code: (0) 18:02:12 Setup is installing Microsoft Distributed Transaction Coordinator (MS DTC) ... 18:02:12 C:\TEMP_ISTMP29.DIR\cldtcstp.exe -SupportDir C:\TEMP_ISTMP29.DIR\ -DTCPkg K:\full\REL0517\sql97SRV\x86\Other\dtcsetup.exe -LogFile C:\WINNT\sqlstp.log 6/27/1998 18:2:12 This computer is not part of a cluster. 6/27/1998 18:2:22 Exit code from installing DTC on local machine: 3010 6/27/1998 18:2:22 DTC specific exit code: 0 6/27/1998 18:2:22 DTC specific error code: 0 6/27/1998 18:2:22 DTC specific completion comment: Source = DtcComplete, ExitType = Success, Successful Install 6/27/1998 18:2:22 Installation succeeded. 18:02:23 Process Exit Code: (1) 18:02:23 Setup is installing (HTML Help) ... 18:02:23 K:\sql97SRV\x86\binn\hhupd.exe /q:a /r:n 18:02:25 Process Exit Code: (0) 18:02:25 End Action InstallPkgs 18:02:25 Begin Action SelfRegister 18:02:52 Return code: 0 18:02:52 End Action SelfRegister

7. Builds the server. 

   18:02:52 Begin Action BuildServer:
   

18:02:52 f:\mssql\BINN\vswitch.exe -Silent 1 -NoCheck 1 -SwitchTo 70 (Switch to 7.0) 18:03:07 Process Exit Code: (0) 18:03:07 C:\TEMP_ISTMP29.DIR\scm.exe -Silent 1 -Action 7 -SvcAccount LocalSystem -ExePath "f:\mssql\binn\sqlservr.exe" (Start MSSQLServer) 18:03:07 Process Exit Code: (0) 18:03:13 Path successfully updated. 18:03:13 %SystemRoot%\system32;%SystemRoot%;F:\BINN;f:\mssql\BINN 18:03:13 f:\mssql\binn\cnfgsvr.exe -Silent 2 -NoSampleDB 0 -SQLPath "f:\mssql\" -SQLDataPath "f:\mssql\" -SortID 52 -LCIDCompStyle "1033-196609" -User sa -Pwd (Configure the server) 18:04:43 Process Exit Code: (0) 18:04:43 End Action BuildServer 18:04:43 Begin Action SetupRegistry: 18:04:43 Transferring SQLExecutive settings ... (Setup or copy the SQL Executive settings) 18:04:43 Return Code: 0, Registry Value: NonAlertableErrors, Registry Data: 1204,4002 18:04:43 Return Code: 0, Registry Value: RestartSQLServer, Registry Data: 1 18:04:43 C:\WINNT\System32\unlodctr.exe MSSQLServer 18:04:43 Process Exit Code: (0)

8. Sets up the registry. 

   18:04:44 End Action SetupRegistry
   

18:04:44 Begin Action PostSetupRegistry: 18:04:44 C:\TEMP_ISTMP29.DIR\scm.exe -Silent 1 -Action 7 -Service SQLExecutive -SvcStartType 1 18:04:44 Process Exit Code: (0) 18:04:44 C:\TEMP_ISTMP29.DIR\scm.exe -Silent 1 -Action 7 -Service MSSQLServer -SvcStartType 2 -SvcAccount LocalSystem 18:04:44 Process Exit Code: (0) 18:04:44 C:\TEMP_ISTMP29.DIR\scm.exe -Silent 1 -Action 7 -Service MSDTC -SvcStartType 1 -SvcAccount LocalSystem 18:04:44 Process Exit Code: (0) 18:04:44 C:\TEMP_ISTMP29.DIR\scm.exe -Silent 1 -Action 5 -Service SQLServerAgent -Dependencies MSSQLServer -ExePath "f:\mssql\binn\sqlagent.exe" 18:04:44 Process Exit Code: (0) 18:04:45 SetupSQLExecSecurity returned: 0 18:04:45 C:\WINNT\System32\lodctr.exe "f:\mssql\BINN\sqlctr.ini" 18:04:46 Process Exit Code: (0) 18:04:46 f:\mssql\BINN\dcomscm.exe /Register 18:04:46 Process Exit Code: (0) 18:04:46 C:\Program Files\Common Files\Microsoft Shared\Database Replication\wzcnflct.exe /RegServer 18:04:47 Process Exit Code: (0) 18:04:47 End Action PostSetupRegistry

9. Sets up the folders. 

   18:04:47 Begin Action SetupFolders:
   

18:04:48 Microsoft SQL Server 7.0 Folder refreshed. 18:04:48 End Action SetupFolders 18:04:48 Action CleanUpInstall: 18:04:48 Uninstall command: C:\WINNT\IsUninst.exe -ff:\mssql\Uninst.isu -c"f:\mssql\sqlsun.dll" -m 18:04:48 K:\full\REL0517\sql97SRV\x86\binn\regrebld.exe -Backup f:\mssql\BINN 18:04:48 Process Exit Code: (0) 18:04:48 Registry successfully backed up.

10. Displays completion message. 

    18:04:48 Installation Succeeded
    

11. Creates the Cnfgsvr.out file. 

    Starting Service ...
    

Connecting to Server ... driver={sql server};server=.;UID=sa;PWD=;database=master Remapping Server Databases ... [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully detached database 'model'. [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator. [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully attached database 'model'. [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully detached database 'msdb'. [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator. [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully attached database 'msdb'. [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully detached database 'pubs'. [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator. [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully attached database 'pubs'. [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully detached database 'Northwind'. [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator. [Microsoft][ODBC SQL Server Driver][SQL Server]Successfully attached database 'Northwind'. Disconnecting from Server ...

Stopping Service ...

Starting Service ...

Connecting to Server ... driver={sql server};server=.;UID=sa;PWD=;database=master

Configuring Server ... [Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to 'BUILTIN\Administrators'. [Microsoft][ODBC SQL Server Driver][SQL Server]'BUILTIN\Administrators' added to role 'sysadmin'. [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator. [Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option changed. Run the RECONFIGURE statement to install. [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator. [Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option changed. Run the RECONFIGURE statement to install. Disconnecting from Server ... Stopping Service ... SQL Server has been successfully configured!

Scripting

When running an unattended installation, return error codes may be returned. Here is a list of the error codes and a description.

Troubleshooting the SQL Server Upgrade Wizard

The SQL Server Upgrade Wizard is designed to be as problem-free as possible; however, there are situations that may interfere with upgrading Microsoft SQL Server version 6.x databases to SQL Server 7.0. The most common upgrade error is the failure to create an object in SQL Server 7.0. In many cases, the problem is simple, such as running out of disk space. In any case, the SQL Server Upgrade Wizard creates detailed logs specifying the problem.

Completing the SQL Server Upgrade Wizard

The SQL Server Upgrade Wizard performs a version upgrade using the options you specified. The Microsoft SQL Server version 6.x server and data are left intact throughout the version upgrade process.

During the SQL Server Upgrade Wizard process:

• User stored procedures are verified against the contents of syscomments for inconsistencies. 

• All logins, users, and permissions are validated. 

If the SQL Server Upgrade Wizard detects any problems, a dialog box is displayed with this text:

One or more warnings have been logged. Please read the next screen carefully before you begin your upgrade.

For more information about specific errors, see the \Mssql\Upgrade\<servername>_<date>_<time> directory for *.err files.

The Summary of Warnings dialog box displays inconsistencies found in the user objects of accounts. Users should not continue until these are resolved. This output file is located in the \Mssql\Upgrade\<SQLServer_date_time> directory. The file name is associated with the database name and ID, "check65-<dbid><dbname>_err.out" (for example, "check65-007mypubs_err.out"). If the user continues without fixing the listed errors, check the relevant files for objects, logins, and invalid permissions.

If stored procedures have been renamed using sp_rename, the source stored in syscomments must be changed. Drop and re-create the procedure using the new name in the CREATE PROCEDURE syntax.

Upgrade Log Files

Each time you run the SQL Server Upgrade Wizard, a subdirectory is created in the C:\Mssql7\Upgrade directory. The subdirectory name consists of the server name and the current date and time to distinguish multiple runs of the SQL Server Upgrade Wizard (for example, SQLCONV1_092198_151900).

Inside this subdirectory are a number of descriptively named log files describing each of the upgrade steps. Also inside is another subdirectory for each upgraded database, including the master database. Inside each database folder are log files indicating the success of the creation of different types of objects in that database. Files that end in .ok indicate that all instances of that type of object were created successfully. Files that end in .err indicate that at least one instance of that type of object was not created successfully. The error files list each failed object creation statement and the reason the object was not created successfully.

Any log files that indicate a problem are listed at the end of the SQL Server Upgrade Wizard for easy access.

The \WinNT directory contains these files.

The \Mssql7\Upgrade directory contains these files and directories.

Object directories contain these files and directories. The SQL Server Upgrade Wizard names some files with either an .out or an .err extension, depending on the success of the task.

Database-specific directories contain these files.