Microsoft KB Archive/304711

= FIX: SQL Server 2000 Service Pack 1 Setup Fails with No Errors =

Article ID: 304711

Article Last Modified on 10/17/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q304711



SYMPTOMS
After you run the SQL Server 2000 Service Pack 1 Setup, the SQL Server components are still the RTM 8.00.194 version components. The SQL Server version is not updated, and no error was generated in the Sqlsp.log file. The following Transact-SQL command: select @@version returns:  Microsoft SQL Server 2000 - 8.00.194 In addition, the system databases are not updated. If you check the Sqlsp.log file, no upgrade scripts appear to have been executed during the Service Pack 1 Setup. On a Microsoft Windows NT 4.0 or Microsoft Windows 2000 server, the Sqlsp.log file is located in the Windows folder (C:\WINNT). Also, the files in the list that follows are not created in the Install folder where the SQL Server instance is installed. For example, C:\Program Files\Microsoft SQL Server\SQL_Instance_Name\Install.
 * sp1_serv_uni.out
 * 80sp1-tools.out
 * sp1_repl.out



CAUSE
There is a registry key value missing from the problematic server. The following key is used in tracking the server component GUIDs. However, the key either does not contain values or it is missing on the problematic computer.

For a default SQL Server 2000 instance the key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Tracking

For SQL Server 2000 named instances, the key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\%Named_Instance%\Tracking



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack



WORKAROUND
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

To work around this problem, from another computer that is running SQL Server that has a valid key value, export the preceding key and then either import or restore the key value on the problematic computer.

A valid key looks similar to this:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MyInstance\Tracking]

&quot;{E07FDDA4-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDA6-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{6DC86044-0C71-11d3-9E18-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDA8-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDA9-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDAA-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDAB-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDAC-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDAD-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDAF-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDB2-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDBE-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDC0-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;

&quot;{E07FDDBF-5A21-11d2-9DAD-00C04F79D434}&quot;=&quot;&quot;



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Additional query words: sql setup sp1 install fail tracking registry

Keywords: kbbug kbfix kbsetup KB304711

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.