FIX: The Setup program may fail when you try to upgrade to SQL Server 2000 and Setup runs the Messages.sql script (300676)

SYMPTOMS

When you upgrade a server from Microsoft SQL Server 7.0 to SQL Server 2000, the setup may fail when it executes the Messages.sql script. To identify this issue, review these logs:

The Sqlstp.log log file.

The Sqlstp.log file (located on %SystemRoot%\ or C:\Winnt\) may contain a line just before the one that runs Messages.sql, which indicates the SQL Server services started and the exit code indicates success. However, the MSSQLServer service is not started.

For example:

scm.exe -Silent 1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m 08:55:27 Process Exit Code: (0)

Later, the Sqlstp.log file may contain lines that resemble the following:

08:55:27 \\ServerName\Progra~1\MSSQLS~1\Msss80\STANDA~1\x86\BINN\osql.exe  -S EG-ISDSQLQA-A01 -b -n -d master -o "D:\MSSQL7\install\messages.out" -i "D:\MSSQL7\install\messages.sql" -E
08:55:36 Process Exit Code: (1) 
08:56:06 Error running script: messages.sql (1)
... 08:56:06 Installation Failed.

The SQL Server error log. The current SQL Server error log shows that MSSQLServer started in a minimal configuration and then immediately shut down. The time stamp of the last entry in the SQL Server error log is just before the failure of Messages.sql in the Sqlstp.log file.

The Messages.out file. The Messages.out file located on C:\MSSQL7\Install\ may contain the following:

[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen (Connect()).

CAUSE

A race condition occurs between the startup process of SQL Server and the process that initiates the Messages.sql script.

During the setup, SQL Server must start and complete a standard recovery of user databases. The portion of the code that starts and stops the server during the upgrade script processing does not wait for the Start or Stop operation to complete fully, which leads to sporadic failures. As a result, the setup runs scripts during stop or startup events, which causes the failure condition.

RESOLUTION

This issue is isolated to the original Release To Manufacturing (RTM) version of SQL Server only. It does not apply to any service pack setup (because an upgrade of databases cannot take place during a service pack installation). As a result, this fix will not be included in any service packs.

The English version of this fix should have the following file attributes or later:

   Date        Time      Version     Size     File name   Platform
   ---------------------------------------------------------------

   6/21/2001   7:32 PM   8.00.0305   400 KB   Setup.ins   x86

To use the fix, use these steps:

Download s80305i.exe. The following file is available for download from the Microsoft Download Center:

Download the s80305i.exe package now.

For more information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
To install SQL Server 2000 using the new Setup.ins file, copy all of the files on the SQL Server 2000 CD to a directory on your drive.
Replace the existing Setup.ins in the \x86\Setup\ folder with the Setup.ins file that you downloaded in the fix.
Rerun the SQL Server 2000 setup.