November 12, 2007 at 8:32 am
I am seeing the following error in the SQL Server Error Log so many times,
Process 57:0 (ea8) UMS Context 0x002D78E0 appears to be non-yielding on Scheduler 0.
This is a developement box and is even not being utilized much. Is there any any reason why these errors are being raised?
November 12, 2007 at 2:55 pm
I had a similar issue ... Never got to solve it though ... I think it is related to IO problems ...
November 13, 2007 at 10:56 am
There are a lot of references to this message in Microsoft's Knowledgebase (http://support.microsoft.com/search/?adv=1&spid=2852). You might try searching for articles that fit your particular version and patch level.
Greg
Greg
November 14, 2007 at 11:42 am
If you have not installed 2000 SP4, do so. Then the error willl not lockup your server or the db. If you have installed it then the error does not appear to lock up the server or the db.
November 14, 2007 at 12:47 pm
I have collected some info about this error a month ago. Share with you here. I do not know your server setup and activities at that monment.
1. MS says:
Error 17883....A scheduler that has stopped responding is generally a bug with the SQL Server product or an external component (XProc, COM object, and so on).
http://support.microsoft.com/kb/319892
2. and check this as well: http://support.microsoft.com/kb/890637
"Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4."
http://support.microsoft.com/kb/909734/en-us
"We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244..." http://support.microsoft.com/kb/909734/en-us
3. However, I do see the problem happens on build 2187. so applying the lastest patch may not get ride of this problem.
http://sql-server-performance.com/Community/forums/p/8795/49409.aspx
4. some user points to hardware issue:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1279964&SiteID=1
Hope this help you somehow.
November 14, 2007 at 3:06 pm
don_goodman (11/14/2007)
If you have not installed 2000 SP4, do so. Then the error willl not lockup your server or the db. If you have installed it then the error does not appear to lock up the server or the db.
I seem to be having nothing but problems with SP4, specifically reporting of locks (io waits) that slow down certain queries tremendously. From everything I saw posted indicates that this is normal behavior ?
November 15, 2007 at 7:30 am
We have SQL 2K SP4 installed and we encountered this problem with the machine locking up and becoming unresponsive. My initial research said to contact MS and obtain a hotfix. So, I called them and told them what was going on. Of course, they did all sorts of research on our system, but it seemed like they had no idea of what was causing the problem (I spoke to 3 different people). They told us that it was a hard drive issue, as there were errors in the logs relating to our disks (SAN) and that we would have to contact our SAN vendor to resolve the issue. So, I went and did more research and realized that the hardware events in the viewer were not even present at the time of the reported error. They occurred days after the initial event. It was only after this, and a few more days of researching, they sent us a hotfix. They never really said what they discovered, and I only trusted them and installed the hotfix because they are MS - the vendor for this product.
November 15, 2007 at 7:35 am
Christopher, What is the hotfix for this?
November 15, 2007 at 8:09 am
There is no one hotfix; it depends. The error is caused by several different reasons, so there are several different hotfixes. Besides, you can't obtain a hotfix 'til you contact MS anyway, right? So they'll issue you the right one. Thanks.
Chris
November 15, 2007 at 8:13 am
I had the same issue and SP4 resolved it, but it caused other issues such as io waits and long running transactions.
November 15, 2007 at 8:19 am
I had the same problem and am planning to apply SP4 2187. I saw other user had the same problem with 2187 so I am questioning whether there is something more than 2187 needed.
Do you mind sharing what is your current @@version after applying the hotfix?
November 15, 2007 at 8:32 am
After the hotfix was applied, we're currently at 8.00.2232.
Thanks...Chris
February 6, 2008 at 10:36 am
I applied 2187 but no use. Finally opened a case with MS.
KB http://support.microsoft.com/?id=916653 applies to our case. Either performance optimization or hotfix 2189.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply