A few days ago i encountered the below mentioned error message in SQL error logs in one of our production environments
Process 0:0:0 (0x1ebc) Worker 0x00000005393F61A0 appears to be non-yielding on Scheduler 15. Thread creation time: 13022573770856.
I found the following KB Article on MSDN to throw light on this issue. As per the article there was a stack dump that we found in the server.
What caused the schedulers to be non-responsive:
As per the article the cause of the issue is:
“This issue occurs because the profiling session is not closed correctly. The profiling session is used to calculate the cost of an object to be cached, and is based on memory usage and CPU usage”.
Resolution as Provided by MS in the Kb article for SQL server 2008 is:
Apply CU6 for SP 3.
Our patch level in the environment is beyond that and still this issue happened, so literally there is no solution provided by MS. We would wait and see if this error comes back too often and open a case with MS support.
Tagged: CPU, Scheduler, SQL Server, Stack Dump
Hi, Have you fix this error? We are on SQL 2012 SP3 CU8, still seeing that error on all our servers time to time. Please do let us know if you know the fix of this problem (could save us the time to open up microsoft case)
LikeLiked by 1 person
We didn’t get any from MS. We upgraded to SQL 2012. Post that we didn’t see this error.