Article ID: 2846378 - View products that this article applies to.
Microsoft SQL Server 2012 Service Pack 1 fixes have been released as one downloadable file. Given that the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 Service Pack 1 fix release.
Expand all | Collapse all

On This Page

Symptoms

When you insert a row in Microsoft SQL Server 2012, a "Non-yielding Scheduler" error may occur. When this issue occurs, a dump file is generated, and the following error message is logged in the SQL Server error log:

Date Time Server * *******************************************************************************
Date Time Server *
Date Time Server * BEGIN STACK DUMP:
Date Time Server * Date Time 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 0x0000000000000047
Date Time Server External dump process return code 0x20000001.
External dump process returned no errors.
Date Time Server Process 0:0:0 (0x41e8) Worker 0x000000017F41C160 appears to be non-yielding on Scheduler 4. Thread creation time: 13010778086858. Approx Thread CPU Used: kernel 0 ms, user 70216 ms. Process Utilization 12%. System Idle 84%. Interval: 70227 ms.

Resolution

Cumulative update information

Cumulative Update 4 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:
2833645 Cumulative update 4 for SQL Server 2012 SP1
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 SP1 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 go to the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

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 go to 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 go to the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to go to the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 2846378 - Last Review: May 31, 2013 - Revision: 1.0
Applies to
  • Microsoft SQL Server 2012 Service Pack 1
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Business Intelligence
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2846378

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