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

In Microsoft SQL Server 2000 Service Pack 4 (SP4), new diagnostics do not capture the thread stack when the SQL Server User Mode Scheduler (UMS) experiences a nonyielding thread. Additionally, the thread context variable is not populated with the expected thread stack information. When this problem occurs, an error message that is similar to the following is logged in the SQL Server error log:

Back to the top

This problem occurs because no thread ID is associated with the idle thread that is considered to be the nonyielding thread.

Back to the top

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

•	The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture. Note This issue does not occur on systems that use the Intel Itanium processor architecture.
•	The system is running a 64-bit version of the Microsoft Windows Server operating system.
•	The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may 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 immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

•	SQL Server 2000 SP4 For information about how to obtain SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base: 290211 (http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack

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 those 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 tool in Control Panel.

SQL Server 2000 32-bit versions

File name	File version	File size	Date	Time	Platform
Dtsui.dll	2000.80.2166.0	1,593,344	21-Oct-2005	01:26	x86
Impprov.dll	2000.80.2166.0	102,400	21-Oct-2005	01:26	x86
Mssdi98.dll	8.11.50523.0	239,104	06-Jun-2005	22:46	x86
Ntwdblib.dll	2000.80.2166.0	290,816	21-Oct-2005	01:26	x86
Odsole70.dll	2000.80.2166.0	69,632	21-Oct-2005	01:26	x86
Pfclnt80.dll	2000.80.2166.0	430,080	21-Oct-2005	01:26	x86
Replprov.dll	2000.80.2166.0	237,568	21-Oct-2005	01:26	x86
Semexec.dll	2000.80.2166.0	856,064	21-Oct-2005	01:26	x86
Sqlagent.exe	2000.80.2166.0	323,584	21-Oct-2005	00:02	x86
Sqldiag.exe	2000.80.2166.0	118,784	21-Oct-2005	00:34	x86
Sqldmo.dll	2000.80.2166.0	4,362,240	21-Oct-2005	01:26	x86
Sqlfth75.dll	2000.80.2166.0	102,400	21-Oct-2005	00:01	x86
Sqlservr.exe	2000.80.2166.0	9,158,656	21-Oct-2005	01:30	x86
Sqlsort.dll	2000.80.2166.0	589,824	21-Oct-2005	01:26	x86
Stardds.dll	2000.80.2166.0	176,128	21-Oct-2005	01:26	x86
Svrnetcn.dll	2000.80.2166.0	110,592	21-Oct-2005	01:26	x86
Ums.dll	2000.80.2166.0	35,328	21-Oct-2005	01:26	x86
Sqlevn70.rll	2000.80.2166.0	45,056	21-Oct-2005	01:26	Not applicable

SQL Server 2000 64-bit versions

File name	File version	File size	Date	Time	Platform
Impprov.dll	2000.80.2166.0	244,736	21-Oct-2005	01:29	IA-64
Mssdi98.dll	8.11.50523.0	758,784	06-Jun-2005	22:46	IA-64
Odsole70.dll	2000.80.2166.0	150,528	21-Oct-2005	01:27	IA-64
Pfclnt80.dll	2000.80.2166.0	1,187,840	21-Oct-2005	01:42	IA-64
Replprov.dll	2000.80.2166.0	538,624	21-Oct-2005	01:31	IA-64
Sqlagent.exe	2000.80.2166.0	1,061,376	21-Oct-2005	01:45	IA-64
Sqldiag.exe	2000.80.2166.0	334,336	21-Oct-2005	01:44	IA-64
Sqldmo.dll	2000.80.2166.0	13,860,352	21-Oct-2005	01:57	IA-64
Sqlfth75.dll	2000.80.2166.0	246,784	21-Oct-2005	01:28	IA-64
Sqlservr.exe	2000.80.2166.0	24,935,936	21-Oct-2005	05:40	IA-64
Sqlsort.dll	2000.80.2166.0	617,472	20-Oct-2005	23:58	IA-64
Svrnetcn.dll	2000.80.2166.0	427,520	21-Oct-2005	01:41	IA-64
Sqlevn70.rll	2000.80.2166.0	35,328	21-Oct-2005	05:36	Not applicable

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

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, click the following article number to view the article in the Microsoft Knowledge Base: 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 the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top