Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After every few days of faultless operation, the following information event pops up in my database server's event log:

Process 0:0:0 (0x890) Worker 0x5C55A0D8 appears to be non-yielding on Scheduler 0.
Thread creation time: 12945965386972. Approx Thread CPU Used: kernel 0 ms, user 0 ms.
Process Utilization 0%%. System Idle 98%%. Interval: 70427 ms.

The non-yielding worker process, whatever it is, causes the following connection timeout exception for all my applications' databases:

Exception message: Timeout expired. The timeout period elapsed prior to completion of
the operation or the server is not responding.

This message is repeated ad infinitum until I restart the SQL Service. However, the service won't stop, so I have had to forcefully kill the SQLServr.exe process, which is bad. Everything then starts up as normal and the service recovers.

How do I diagnose the cause of this problem?

share|improve this question

You should start here - under "Investigating a 17883 Error".

share|improve this answer
I still don't know the cause. From what I've been able to gather, it's a bug in SQL Server 2008, so I'm installing Service Pack 2. – pate Apr 11 '11 at 21:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.