July 11, 2007 at 8:48 pm
we run sql srver 05 on 64 bit, we have migrated from 2000 two months ago and two days ago our system became very slow and then non-responsive, to the point where the users could not view or use the database at all from their client applications.
on reviewing the error logs etc i found the first error it generated was
it did a stack dump and produced the following error
Non-yielding Scheduler error
and after that the error below flooded the system
Process 62:0:0 (0x11a0) Worker 0x00000001371DE1C0 appears to be non-yielding on Scheduler 0. Thread creation time: 12828422717058. Approx Thread CPU Used: kernel 46 ms, user 31 ms. Process Utilization 0%. System Idle 98%. Interval: 6914916 ms
I tried to kill the process but could not open the view processess window ..as it had become non responsive and could not stop the services even , so restarted the server and that fixed the problem , but not sure what caused it and how i can avoid this happening again ,
please advise if you have seen or come accross this problem
thanks
avi
July 11, 2007 at 11:49 pm
Check the link below that might help.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=118712
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 11, 2007 at 11:53 pm
This is the old 17883 error under sql 7, 2000, and 2005. Please read here some useful explanations:
How To Diagnose and Correct Errors 17883, 17884, 17887, and 17888
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx
The fix for this is an OS (not SQL Server!) patch, unfortunately I cannot find the patch number just now; I would say to call Microsoft support. I've got this issue last year on a sql 2005 x64 sp1 (2047) enterprise, Win 2003 x64 sp1 and the OS patch recommended by the MS support team fixed the problem.
July 12, 2007 at 12:18 am
UMS error occurs because of a failure in CPU processor. As michael says there should be a OS patch available to recitfy this issue.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 12, 2007 at 6:10 am
There is some misconception arounf this Scheduler error message.
Simply said, one of the SQL Server thread was executing a function call and did not yield within 120 seconds.
The SQL 2000/2005 has more or less same scheduling behaviours
see
http://msdn2.microsoft.com/en-us/library/aa175393(SQL.80).aspx
to know more abuot UMS design.
now, to find out what that thread was doing, you need to open the dump file produced by SQL Server and find the function.
Microsoft SQL Server support team is the best team to guide you for the same.
There could be some OS issues contributing to the Scheduler problem. but it is to broad statement to be made.
HTH.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply