FIX: Error message when you run a query that uses a join condition in SQL Server 2005: "Non-yielding Scheduler"

Article translations Article translations
Article ID: 949595 - View products that this article applies to.
Bug #: 50002512 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario. You run a query that uses a join condition in Microsoft SQL Server 2005. Additionally, the query fires a trigger. In this scenario, the Nested Loops operator and the WITH PREFETCH clause appear in the Argument column in the execution plan of the query. Additionally, a minidump file is generated, and the following error message is logged in the SQL Server error log:
Date Time Server ***Unable to get thread context - no pss
Date Time Server * ******************************************************************************
Date Time Server *
Date Time Server * BEGIN STACK DUMP:
Date Time Server * Date Time spid 0
Date Time Server *
Date Time Server * Non-yielding Scheduler
Date Time Server *
Date Time Server * *******************************************************************************
Date Time Server Stack Signature for the dump is 0x000002D9
Date Time Server External dump process return code 0x20000001.
External dump process returned no errors.
Date Time Server Process 89:0:0 (0x4f8) Worker 0x809C40E8 appears to be non-yielding on Scheduler 1. Thread creation time: 12844458479828. Approx Thread CPU Used: kernel 0 ms, user 74546 ms. Process Utilization 28%. System Idle 69%. Interval: 75000 ms.

RESOLUTION

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 Service Pack 2 installed to apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

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 item in Control Panel.
SQL Server 2005, 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.3231.068,63224-Feb-200823:36x86
Chsbrkr.dll12.0.7822.01,684,84022-Jun-200709:22x86
Chtbrkr.dll12.0.7822.06,112,61622-Jun-200709:22x86
Databasemailprotocols.dll9.0.3231.046,10424-Feb-200823:36x86
Distrib.exe2005.90.3231.070,68024-Feb-200823:36x86
Dts.dll2005.90.3231.01,102,36024-Feb-200823:36x86
Dtsconn.dll2005.90.3231.0250,39224-Feb-200823:36x86
Dtspipeline.dll2005.90.3231.0605,20824-Feb-200823:36x86
Fteref.dll12.0.7822.0446,46422-Jun-200709:22x86
Infosoft.dll12.0.7822.0468,32822-Jun-200709:22x86
Korwbrkr.dll12.0.7822.071,01622-Jun-200709:22x86
Langwrbk.dll12.0.7822.0136,55222-Jun-200709:22x86
Mergetxt.dll2005.90.3231.032,28024-Feb-200823:36x86
Microsoft.analysisservices.dll9.0.3231.01,217,56024-Feb-200823:36x86
Microsoft.sqlserver.connectioninfo.dll9.0.3231.0156,69624-Feb-200823:36x86
Microsoft.sqlserver.dtstransferprovider.dll9.0.3231.0115,73624-Feb-200823:36x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3231.0295,96024-Feb-200823:36x86
Microsoft.sqlserver.replication.dll2005.90.3231.01,628,18424-Feb-200823:36x86
Microsoft.sqlserver.servicebrokerenum.dll9.0.3231.042,00824-Feb-200823:36x86
Microsoft.sqlserver.smo.dll9.0.3231.01,606,68024-Feb-200823:36x86
Microsoft.sqlserver.smoenum.dll9.0.3231.0222,23224-Feb-200823:36x86
Microsoft.sqlserver.sqlenum.dll9.0.3231.0898,07224-Feb-200823:36x86
Msfte.dll12.0.7822.02,430,31222-Jun-200709:22x86
Msftefd.exe12.0.7822.066,92022-Jun-200709:22x86
Msftepxy.dll12.0.7822.095,59222-Jun-200709:22x86
Msftesql.exe12.0.7822.095,59222-Jun-200709:22x86
Msgprox.dll2005.90.3231.0200,21624-Feb-200823:36x86
Msir5jp.dll5.0.2130.03,159,91222-Jun-200709:22x86
Nlhtml.dll12.0.7822.0124,26422-Jun-200709:22x86
Nls400.dll5.0.4217.012,240,74422-Jun-200709:22x86
Odsole70.dll2005.90.3231.058,90424-Feb-200823:36x86
Osql.exe2005.90.3231.053,27224-Feb-200823:36x86
Query9x.dll12.0.7822.048,48822-Jun-200709:22x86
Rdistcom.dll2005.90.3231.0644,63224-Feb-200823:36x86
Replerrx.dll2005.90.3231.0114,71224-Feb-200823:36x86
Replisapi.dll2005.90.3231.0272,92024-Feb-200823:36x86
Replmerg.exe2005.90.3231.0320,53624-Feb-200823:36x86
Replprov.dll2005.90.3231.0552,98424-Feb-200823:36x86
Replrec.dll2005.90.3231.0785,43224-Feb-200823:36x86
Replsub.dll2005.90.3231.0408,08824-Feb-200823:36x86
Replsync.dll2005.90.3231.0101,40024-Feb-200823:36x86
Sac.exe9.0.3231.082,96824-Feb-200823:36x86
Sbmsmdlocal.dll9.0.3231.015,969,30424-Feb-200823:36x86
Sbmsmdredir.dll9.0.3231.04,022,80824-Feb-200823:36x86
Sqlaccess.dll2005.90.3231.0350,23224-Feb-200823:36x86
Sqladhlp.exe2005.90.3231.047,12824-Feb-200823:36x86
Sqlagent90.exe2005.90.3231.0349,72024-Feb-200823:36x86
Sqlbrowser.exe2005.90.3231.0242,71224-Feb-200823:36x86
Sqlcmd.exe2005.90.3231.0143,38424-Feb-200823:36x86
Sqlctr90.dll2005.90.3231.067,60824-Feb-200823:36x86
Sqldiag.exe2005.90.3231.01,074,20024-Feb-200823:36x86
Sqldumper.exe2005.90.3231.068,63224-Feb-200823:36x86
Sqlmaint.exe2005.90.3231.077,84824-Feb-200823:36x86
Sqlmergx.dll2005.90.3231.0194,07224-Feb-200823:36x86
Sqlmgmprovider.dll2005.90.3231.0236,56824-Feb-200823:36x86
Sqlsac.exe2005.90.3231.01,246,23224-Feb-200823:36x86
Sqlservr.exe2005.90.3231.029,216,28024-Feb-200823:36x86
Sqlsqm.exe9.0.3231.0128,02424-Feb-200823:36x86
Sqlwep.dll2005.90.3231.090,64824-Feb-200823:36x86
Sqlwtsn.exe9.0.3231.099,35224-Feb-200823:36x86
Sqsrvres.dll2005.90.3231.070,16824-Feb-200823:36x86
Ssradd.dll2005.90.3231.042,52024-Feb-200823:36x86
Ssravg.dll2005.90.3231.043,03224-Feb-200823:36x86
Ssrmax.dll2005.90.3231.040,98424-Feb-200823:36x86
Ssrmin.dll2005.90.3231.040,98424-Feb-200823:36x86
Ssrpub.dll2005.90.3231.030,23224-Feb-200823:36x86
Svrenumapi.dll2005.90.3231.0615,44824-Feb-200823:36x86
Tablediff.exe9.0.3231.087,06424-Feb-200823:36x86
Thawbrkr.dll12.0.7822.0206,18422-Jun-200709:22x86
Xmlfilt.dll12.0.7822.0197,99222-Jun-200709:22x86
Xmlsub.dll2005.90.3231.0194,58424-Feb-200823:36x86
Xpadsi90.exe2005.90.3231.050,71224-Feb-200823:36x86
Xpqueue.dll2005.90.3231.056,85624-Feb-200823:36x86
Xprepl.dll2005.90.3231.073,24024-Feb-200823:36x86
Xpstar90.dll2005.90.3231.0298,52024-Feb-200823:36x86

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 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 software update terminology, 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

Properties

Article ID: 949595 - Last Review: March 18, 2008 - Revision: 1.3
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Enterprise Edition
Keywords: 
kbautohotfix kbhotfixserver kbfix kbexpertiseadvanced kbqfe KB949595

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com