July 26, 2008 at 9:11 am
We have a server with the following configuration
SQL Server 2000 with SP4 (2040)
select @@version, gives the below output
Microsoft SQL Server 2000 - 8.00.2040 (Intel X86)
May 13 2005 18:33:17
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
I found the below errors in SQL Server Error Log
2008-07-20 01:01:34.45 spid65 DBCC CHECKDB (msdb) executed by dmn\user found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes
9 seconds.
2008-07-20 01:38:04.66 server Sleeping until external dump process completes.
2008-07-20 01:38:34.87 server Resuming after waiting on external debug process for 3 seconds.
2008-07-20 01:38:34.87 server Stack Signature for the dump is 0x00000000
2008-07-20 01:38:34.90 server Error: 17883, Severity: 1, State: 0
2008-07-20 01:38:34.90 server Process 63:0 (d8c) UMS Context 0x03D75218 appears to be non-yielding on Scheduler 0.
2008-07-20 01:39:34.95 server Error: 17883, Severity: 1, State: 0
2008-07-20 01:39:34.95 server Process 63:0 (d8c) UMS Context 0x03D75218 appears to be non-yielding on Scheduler 0.
By considering the Microsoft KB Aritcle http://support.microsoft.com/kb/890730
We need to install SP4 with latest hotfix available in Microsoft
already the server has SP4 with hot fix 2040.
Here my question is
1) Why I am getting the below error even though I have SP4.
2008-07-20 01:38:34.90 server Error: 17883, Severity: 1, State: 0
2008-07-20 01:38:34.90 server Process 63:0 (d8c) UMS Context 0x03D75218 appears to be non-yielding on Scheduler 0.
2) What is the steps I should take when I see the above errors.
Rajesh Kasturi
July 26, 2008 at 10:07 am
You could have another bug in there.
The scheduler in SQL Server manages threads just like the scheduler in the OS does, but this one managers the SQL processes. If you have a thread that's non-yielding, it can hold up other processes since I think certain processes get bound to a particular scheduler.
Did a backup run while CheckDB was running?
July 26, 2008 at 11:22 am
Does this happen Frequently or Rarely.
If it is a RARE kind of Deal, you can ignore this messages in the LOG.
As per Microsoft:
You may receive this error message when you use any of the following on a high-end disk subsystem:
# ALTER DATABASE ADD FILE
# CREATE DATABASE
# AUTOGROW of files (explicit or implicit)
-- You need to check your Database Files Growth % or MB and check to see they they are not auto Growing Frequently.. or work around the values. (concerns with DB size)
http://support.microsoft.com/kb/319892/
Maninder
www.dbanation.com
August 3, 2008 at 11:37 am
It is not frequent, If it comes again as you said I should look into the issue.
Rajesh Kasturi
August 3, 2008 at 11:41 am
No there was no backup while CHECKDB was running.
Rajesh Kasturi
August 3, 2008 at 1:54 pm
I found some more related links
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/890637#3a
Rajesh Kasturi
April 15, 2011 at 7:39 pm
Did you got the solution... I am too getting similar error
It will be really helpful
April 16, 2011 at 12:34 pm
this error is usually an indication the server is under stress. a change was made in SP4 so 17883 errors produce more info to aid troubleshooting (by microsoft).
but as SQL2000 is out of support you are not likely to get assistance with this type of issue.
---------------------------------------------------------------------
March 5, 2012 at 5:10 pm
Rajesh,
did you find any permanent solution for this issue?
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply