Select the product you need help with
FIX: Error code 17883 or "Non-yielding Scheduler" error may occur when you use the OPENQUERY function on SQL Server 2005Article 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. On This PageSYMPTOMSConsider the following scenario:
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 CAUSEThis 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. RESOLUTIONSQL Server 2005 Service Pack 3The 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 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:
(http://support.microsoft.com/kb/2438344/LN/
)
Cumulative update package 13 for SQL Server 2005 Service Pack 3960598 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.
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released SQL Server 2005 Service Pack 4The 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 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:
(http://support.microsoft.com/kb/2489409/LN/
)
Cumulative update package 2 for SQL Server 2005 Service Pack 42485757 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.
(http://support.microsoft.com/kb/2485757/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor 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 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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 2468047 - Last Review: February 21, 2011 - Revision: 2.0 APPLIES TO
| Article Translations |
Back to the top
