November 2, 2007 at 3:32 pm
Sql Server 2005, I get an error:
Unable to get thread context - no pss
BEGIN STACK DUMP:
Date Time spid 0
Non-yielding Scheduler
I did some research and found that it is a reported bug:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=279369
Does anyone has a workaround or solution for this problem?
Thanks!
November 4, 2007 at 2:58 am
Hi,
This looks like a SP1 issue and first port of call would be to install SP2 to see if problem still persist. This bascially means the CPU schedulers are not yielding to allow other threads to get CPU cycles.
Thanks,
Phillip Cox
November 4, 2007 at 9:46 am
I agree with Phillip and if you call MS, they'll almost certainly require SP2.
Is this an SP1 box or has this happened on SP2?
November 4, 2007 at 10:29 am
It has happened on a SP2 box. I have raised another bug with MS mentioning that it is also happening on SP2.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=308327
Meanwhile, if somebody could provide a workaround, that would be great! We have to restart our production server when this issue happens because the system just hangs.
Thanks!
November 6, 2007 at 5:36 am
we recently had some similar "Non-yielding Scheduler" errors on our servers.
I don't know your server's config but in our case these errors began when we configured some of our servers with the (processor) "Affinity Mask" server option to dedicate specific cpu to specific sql instances.
so we reversed back this option to resolve the pb and it's ok since.
some info on the schedulers :
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx#ELDAC
hope this will help you.
November 6, 2007 at 8:21 am
What build are you running? Cumulative update package 4 (build 09.00.3200) for SP2 is now available. Cumulative update package 3 (09.00.3186) for SP2 has been out for while now.
http://support.microsoft.com/kb/937137
Tommy
Follow @sqlscribeNovember 6, 2007 at 6:09 pm
Majbou, we did not make any changes to affinity mask. But thanks for the article link, it helped clear a lot of things.
Tommy, we do not have the latest build but I checked, this issue has not been fixed in the latest packages.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply