This article describes the following about this hotfix release:

•	The issues that are fixed by the hotfix package
•	The prerequisites for installing the hotfix package
•	Whether you must restart the computer after you install the hotfix package
•	Whether the hotfix package is replaced by any other hotfix package
•	Whether you must make any registry changes
•	The files that are contained in the hotfix package

Back to the top

You may experience one or more of the following symptoms in Microsoft SQL Server 2000:

•	You cannot connect to an instance of SQL Server. Or, you can connect to an instance of SQL Server. However, the connection is slow.
•	You cannot stop the SQL Server service.
•	Many minidump files are generated.
•	Many log files are generated in the SQL Server log folder.

Back to the top

This issue occurs because an access violation occurs when SQL Server tries to update the performance monitor counters.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix, you must have SQL Server 2000 Service Pack 4 installed. For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only the files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time
80sp4-tools.sql	Not Applicable	134,628	18-Feb-2006	10:40
Dtsui.dll	2000.80.2217.0	1,593,344	07-Sep-2006	14:33
Impprov.dll	2000.80.2217.0	102,400	07-Sep-2006	14:33
Msgprox.dll	2000.80.2217.0	94,208	07-Sep-2006	14:33
Msrpjt40.dll	4.10.9424.0	188,473	23-Jan-2006	17:13
Mssdi98.dll	8.11.50523.0	239,104	06-Jun-2005	07:46
Ntwdblib.dll	2000.80.2217.0	290,816	07-Sep-2006	14:33
Odsole70.dll	2000.80.2217.0	69,632	07-Sep-2006	14:33
Osql.exe	2000.80.2217.0	57,344	07-Sep-2006	12:59
Pfclnt80.dll	2000.80.2217.0	430,080	07-Sep-2006	14:33
Procsyst.sql	Not Applicable	552,068	16-Jun-2005	09:15
Replmerg.exe	2000.80.2217.0	163,840	07-Sep-2006	13:05
Replmerg.sql	Not Applicable	1,151,450	07-Sep-2006	12:51
Replprov.dll	2000.80.2217.0	237,568	07-Sep-2006	14:33
Replrec.dll	2000.80.2217.0	315,392	07-Sep-2006	14:33
Replsub.dll	2000.80.2217.0	270,336	07-Sep-2006	14:33
Replsys.sql	Not Applicable	1,096,075	31-Jul-2006	10:21
Repltran.sql	Not Applicable	1,000,634	02-Feb-2006	06:59
Rinitcom.dll	2000.80.2217.0	278,528	07-Sep-2006	14:33
Semexec.dll	2000.80.2217.0	856,064	07-Sep-2006	14:33
Sp4_serv_qfe.sql	Not Applicable	18,810	16-Jun-2005	09:15
Sqlagent.exe	2000.80.2217.0	323,584	07-Sep-2006	12:57
Sqldiag.exe	2000.80.2217.0	118,784	07-Sep-2006	13:30
Sqldmo.dll	2000.80.2217.0	4,362,240	07-Sep-2006	14:33
Sqlevn70.rll	2000.80.2217.0	45,056	07-Sep-2006	14:33
Sqlfth75.dll	2000.80.2217.0	102,400	07-Sep-2006	12:57
Sqlservr.exe	2000.80.2217.0	9,175,040	07-Sep-2006	14:32
Sqlsort.dll	2000.80.2217.0	589,824	07-Sep-2006	14:33
Stardds.dll	2000.80.2217.0	176,128	07-Sep-2006	14:33
Svrnetcn.dll	2000.80.2217.0	110,592	07-Sep-2006	14:33
Ums.dll	2000.80.2217.0	35,328	07-Sep-2006	14:33
Xpstar.dll	2000.80.2217.0	311,296	07-Sep-2006	14:33

Back to the top

To work around this issue, start the SQL Server service by using the –x startup parameter. The –x startup parameter does not allow for the performance monitor counters to be updated.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top