Select the product you need help with

FIX: A "Non-yielding on Scheduler" error occurs if you use Service Broker to run a distributed query in SQL Server 2012

Article ID: 2672531 - View products that this article applies to.

Symptoms

Consider the following scenario:

You have an application that uses Microsoft SQL Server Service Broker to send messages.
The application sends a message to run a distributed query in Microsoft SQL Server 2012.
Service Broker starts a stored procedure to handle this message.

In this scenario, the stored procedure might fail. Additionally, the following error message is logged in the SQL Server error log:

Date Time spid## Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.

Date Time Server Using 'dbghelp.dll' version '4.0.5'

Date Time Server ***Unable to get thread context for spid 0

Date Time Server * *******************************************************************************

Date Time Server *

Date Time Server * BEGIN STACK DUMP:

Date Time Server * Date Time spid spid

Date Time Server *

Date Time Server * Non-yielding Scheduler

Date Time Server *

Date Time Server * *******************************************************************************

Date Time Server Stack Signature for the dump is 0x000000000000039C

Date Time Server Process 0:0:0 (0x25b0) Worker 0x00000040FB480160 appears to be non-yielding on Scheduler 4. Thread creation time: 12971983687281. Approx Thread CPU Used: kernel 0 ms, user 70138 ms. Process Utilization 7%. System Idle 85%. Interval: 70138 ms.

Date Time Server External dump process return code 0x20000001.

Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:

2679368

(http://support.microsoft.com/kb/2679368/ )

Cumulative update package 1 for SQL Server 2012

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 2012 fix release. We recommend 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:

2692828

(http://support.microsoft.com/kb/2692828/ )

The SQL Server 2012 builds that were released after SQL Server 2012 was released

Back to the top | Give Feedback

Status

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

Back to the top | Give Feedback

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

(http://support.microsoft.com/kb/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

(http://support.microsoft.com/kb/822499/ )

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

(http://support.microsoft.com/kb/824684/ )

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

Back to the top | Give Feedback