September 22, 2010 at 12:55 pm
Hi all,
We have a problem with our MS SQL Server 2000 - 8.00.2055 SP4 production instance on a Windows 2003 box.When i try to connect to the instance using SSMS/enterprise manager it just hangs.I have seen error logs and see the following error all the time.We have a SQL 2005 Sp2 enterprise editon instance on the same box and it runs fine.Both these instances are part of active node on a two node active /passive cluster.
Can anyone please suggest
Error: 17883, Severity: 1, State: 0
2010-09-11 02:01
:19.84 server Process 78:0 (17b8) UMS Context 0x05A81330 appears to be non-yielding on Scheduler 0.
September 22, 2010 at 3:32 pm
Oh dear. If you cannot get into SQL whilst experiencing that error the ONLY way out is to restart SQL.
How many CPUs have you got. For SQL to freeze there would normally the same 17883 error but for all schedulers (there is one per CPU). So if you have 4 CPUS you would see schedulers 0,1,2 and 3 hanging.
This is indicative of the box being stressed. I don't think you will resolve the root cause without involving MS support. There may be stack traces that provide more info.
---------------------------------------------------------------------
September 23, 2010 at 6:57 pm
Thanks George for your reply.We have 4 Cpu's.Errors stopped once we re-booted our system,need to find a permanent solution.
October 1, 2010 at 11:43 am
Check out this link, it might be useful:
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply