|
Home > Archive > MS SQL Server > June 2005 > Error: 17883 - problem with Scheduler
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error: 17883 - problem with Scheduler
|
|
| imarchenko 2005-06-28, 8:23 pm |
| Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
Igor
| |
| Mike Epprecht \(SQL MVP\) 2005-06-28, 8:23 pm |
| Hi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" < igormarchenko@hotmai
l.com> wrote in message
news:eidXJjBfFHA.1416@TK2MSFTNGP09.phx.gbl...
> Hello!
>
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
>
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
>
>
> Thanks,
>
> Igor
>
>
| |
| imarchenko 2005-06-28, 8:23 pm |
| Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@TK2MSFTNGP12.phx.gbl...
> Hi
>
> We had the issue as our SANs are very fast.
>
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
>
> The problems do not occur anymore.
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program: http://www.microsoft.com/mvp
>
> Blog: http://www.msmvps.com/epprecht/
>
> "imarchenko" < igormarchenko@hotmai
l.com> wrote in message
> news:eidXJjBfFHA.1416@TK2MSFTNGP09.phx.gbl...
>
>
| |
|
| I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" < igormarchenko@hotmai
l.com> wrote in message
news:%23hTvPqDfFHA.2152@TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
>
> Thanks,
> Igor
>
>
> "Mike Epprecht (SQL MVP)" <mike@epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@TK2MSFTNGP12.phx.gbl...
>
>
| |
| imarchenko 2005-06-29, 1:23 pm |
| Thanks,Mike!
Igor
"ME" <ME@hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
>
> "imarchenko" < igormarchenko@hotmai
l.com> wrote in message
> news:%23hTvPqDfFHA.2152@TK2MSFTNGP14.phx.gbl...
>
>
|
|
|
|
|