Non yielding schedulers
Error: 17883, Severity: 1, State: 0 server Process 162:0 (0) UMS Context 0x11DE8B68 appears to be non-yielding on Scheduler 1.
I was browsing past Technet when I just happened to notice this KB being in the most recent trouble shooting posts. http://support.microsoft.com/kb/922658/en-us
Actually quite strange as this is dated February, so not really recent.
The non yielding schedulers is something I’ve run up into a few times at other client sites and to be honest I can’t remember exactly the outcome but if I recollect correctly I think I wanted to apply sp2 to w2k3 but as it was an o/s change I was not able to get the change applied.
I’m also pretty sure I encountered this with x64 SQL2005, however there were a number of issues with the x64 boxes so this probably got overlooked. I’m sure there are some specific x64 fixes in sp2 ( for w2k3 ), funny how it’s often easy to get a SQL Server service pack or patch applied but a real problem to get a change to an operating system.
What is interesting is that this bug manifests itself as a lack of activity on the server;
“In most cases, you may notice that the value in the "Batch Requests/sec" counter of the SQLServer:SQLStastics performance object drops significantly in the System performance monitor. Sometimes, the counter value drops to 0. Additionally, you may notice a similar decrease in CPU utilization and in disk utilization. “
now that’s a tricky situation to monitor!