SYMPTOMS
To apply SQL Server 2000 Service Pack 1 (SP1) to a SQL Server 2000 client tools-only installation, run the Setup.bat script from either of these locations:
- The directory that contains the extracted service pack files from SQL2KSP1.exe.
- The service pack directory on the SQL Server 2000 SP1 CD.
On computers that have both SQL Server 2000 client tools and a default instance of Microsoft SQL Server 2000 Desktop Engine installed, the SQL Server 2000 SP1 setup of the tools-only installation fails with this error message:
MSSQLSERVER is not a SQL Server 2000 instance. Setup will now exit.
You may also see these error messages in the SQL Server 2000 SP1 Setup log file (Sqlsp.log):
16:09:23 Begin Action: DialogShowSdInstanceName
16:09:23 Begin Action: ShowDlgInstanceName
16:09:29 MSSQLSERVER is a MSDE instance. This setup will exit.
16:09:32 MSSQLSERVER is not a SQL Server 2000 instance. Setup will now exit.
16:09:33 End Action DialogShowSdInstanceName
16:09:33 End: ShowDialogs()
16:09:33 Action CleanUpInstall:
This problem also occurs on computers that have a named instance of Microsoft SQL Server 2000 Desktop Engine (MSDE).
For example, if the MSDE instance name is MYSQL and you apply SQL Server 2000 SP1 to the client tools, the installation fails with this error message:
MYSQL is not a SQL Server 2000 instance. Setup will now exit.
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