Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

One of our SQL2005 Enterprise Servers running on Win2003 became unresponsive and on reboot I saw these errors logged before it went down.


Date 17/09/2009 10:16:22 Log SQL Server (Archive #1 - 17/09/2009 10:17:00)

Source spid111

Message Timeout occurred while waiting for latch: class 'ACCESS_METHODS_SCAN_RANGE_GENERATOR', id 000000002A761760, type 4, Task 0x000000000E609EB8 : 14, waittime 600, flags 0x1a, owning task 0x000000000E6129B8. Continuing to wait.


Anyone know what this error points or relates to? Many thanks in advance.

share|improve this question
    
Also, around the same time it created a mini stack dump with a "Non-yielding Scheduler" message. –  Chirag Sep 17 '09 at 10:46
    
Does the log file show anything after that? Microsoft has some info at msdn.microsoft.com/en-us/library/ms175066.aspx. –  user3914 Sep 17 '09 at 13:30
    
Plus some more information here: sqlservercentral.com/Forums/Topic647696-146-1.aspx –  user3914 Sep 17 '09 at 13:31
    
Thanks for the pointers Randolph, but we have been unable to either reproduce the problem or find the root cause. –  Chirag Oct 2 '09 at 19:29

1 Answer 1

up vote 0 down vote accepted

There is a cumulative update fix for the "Non-yielding Scheduler" condition.

share|improve this answer
    
Many Thanks jl, found the KB for the fix, it is available for: SQL 2005: SP3 + CU6 SQL 2008: SP1 + CU5 or just CU8 if SP1 isn't applied –  Chirag Dec 13 '09 at 22:14
    
The fix is described in KB support.microsoft.com/kb/974205 –  Chirag Dec 13 '09 at 22:15

Your Answer

 
discard

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.