FIX: Error code 17883 or "Non-yielding Scheduler" error may occur when you use the OPENQUERY function on SQL Server 2005

Article translations Article translations
Article ID: 2468047 - View products that this article applies to.
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 install SQL Server 2005 on a computer.
  • You call the OPENQUERY function by using a linked server that is defined in an instance of SQL Server 2005. The OPENQUERY function retrieves the provider information for the linked server by accessing a registry for SQL Server 2005.
  • The OPENQUERY function requires a long time to respond. For example, the OPENQUERY function responds after 60 seconds or longer.

In this scenario, an error code 17883 or a "Non-yielding Scheduler" error may occur. Additionally, a mini-dump file is generated in the SQL Server 2005 application log folder, and the following error is logged in the SQL Server 2005 error log file:
<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 <ID>
<Date Time> Server *
<Date Time> Server * Non-yielding Scheduler
<Date Time> Server *
<Date Time> Server * *******************************************************************************
<Date Time> Server Stack Signature for the dump is 0x00000000000002B3

CAUSE

This issue occurs because the SQL Server scheduler does not switch the related thread to a preemptive mode.

Note If other tasks are assigned to the same scheduler after the OPENQUERY function runs, the other tasks are blocked. However, the SQL Server scheduler does not stop responding. When the OPENQUERY statement is completed or canceled, the scheduler runs as usual.
After you apply the following hotfix, the OPENQUERY function runs preemptively and does not block any other task that is assigned to the same scheduler.

RESOLUTION

SQL Server 2005 Service Pack 3

The fix for this issue was first released in Cumulative Update 13 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2438344 Cumulative update package 13 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 4

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2005 Service Pack 4. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2489409 Cumulative update package 2 for SQL Server 2005 Service Pack 4
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2485757 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 4 hotfix to an installation of SQL Server 2005 Service Pack 4. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

STATUS

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

REFERENCES

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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: 2468047 - Last Review: February 21, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Evaluation Edition
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2005 Service Pack 3
  • Microsoft SQL Server 2005 Service Pack 4
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2468047

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