FIX: An error message is logged, and new diagnostics do not capture the thread stack when the SQL Server User Mode Scheduler (UMS) experiences a nonyielding thread in SQL Server 2000 Service Pack 4 (909734)



The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Developer Edition 64 bit
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit

BUG #: 474667 (SQL Server 8.0) SQL Server 8.0:474667
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

SUMMARY

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

SYMPTOMS

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:
<Date> <Time> server Error: 17883, Severity: 1, State: 0
<Date> <Time> server Process 0:0 (0) UMS Context 0x002A7058 appears to be non-yielding on Scheduler 1.

CAUSE

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

RESOLUTION

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 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 nameFile versionFile sizeDateTimePlatform
Dtsui.dll2000.80.2166.01,593,34421-Oct-200501:26x86
Impprov.dll2000.80.2166.0102,40021-Oct-200501:26x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86
Ntwdblib.dll2000.80.2166.0290,81621-Oct-200501:26x86
Odsole70.dll2000.80.2166.069,63221-Oct-200501:26x86
Pfclnt80.dll2000.80.2166.0430,08021-Oct-200501:26x86
Replprov.dll2000.80.2166.0237,56821-Oct-200501:26x86
Semexec.dll2000.80.2166.0856,06421-Oct-200501:26x86
Sqlagent.exe2000.80.2166.0323,58421-Oct-200500:02x86
Sqldiag.exe2000.80.2166.0118,78421-Oct-200500:34x86
Sqldmo.dll2000.80.2166.04,362,24021-Oct-200501:26x86
Sqlfth75.dll2000.80.2166.0102,40021-Oct-200500:01x86
Sqlservr.exe2000.80.2166.09,158,65621-Oct-200501:30x86
Sqlsort.dll2000.80.2166.0589,82421-Oct-200501:26x86
Stardds.dll2000.80.2166.0176,12821-Oct-200501:26x86
Svrnetcn.dll2000.80.2166.0110,59221-Oct-200501:26x86
Ums.dll2000.80.2166.035,32821-Oct-200501:26x86
Sqlevn70.rll2000.80.2166.045,05621-Oct-200501:26Not applicable
SQL Server 2000 64-bit versions
File nameFile versionFile sizeDateTimePlatform
Impprov.dll2000.80.2166.0244,73621-Oct-200501:29IA-64
Mssdi98.dll8.11.50523.0758,78406-Jun-200522:46IA-64
Odsole70.dll2000.80.2166.0150,52821-Oct-200501:27IA-64
Pfclnt80.dll2000.80.2166.01,187,84021-Oct-200501:42IA-64
Replprov.dll2000.80.2166.0538,62421-Oct-200501:31IA-64
Sqlagent.exe2000.80.2166.01,061,37621-Oct-200501:45IA-64
Sqldiag.exe2000.80.2166.0334,33621-Oct-200501:44IA-64
Sqldmo.dll2000.80.2166.013,860,35221-Oct-200501:57IA-64
Sqlfth75.dll2000.80.2166.0246,78421-Oct-200501:28IA-64
Sqlservr.exe2000.80.2166.024,935,93621-Oct-200505:40IA-64
Sqlsort.dll2000.80.2166.0617,47220-Oct-200523:58IA-64
Svrnetcn.dll2000.80.2166.0427,52021-Oct-200501:41IA-64
Sqlevn70.rll2000.80.2166.035,32821-Oct-200505:36Not applicable
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

STATUS

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

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

319892 New concurrency and scheduling diagnostics have been added to SQL Server

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:

822499 New naming schema for Microsoft SQL Server software update packages

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:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbQFE kbfix kbbug kbpubtypekc KB909734 kbAudDeveloper kbAudITPRO