Non-Yielding on Scheduler 0.

I have a server with Windows 2003 Server with SQL Server 2000 Cluster Server.
What could cause the error listed below with SQL Server 2000.
Thanks
Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
non-yielding on Scheduler 6
Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
non-yielding on Scheduler 0.
Hi Joe K,
I once had a similar problem with SQL Server, in my case it was caused by
the fact that we used highend SAN’s that allocated disk space to quickly.
(Imagine that, problems caused by disks being to fast instead of to slow)
The KB article related to this problem is
http://support.microsoft.com/kb/810885.
Unfortunately your post didn’t contain the actual error code so I can’t
verify if the problem described in the KB article is the one you are
experiencing. However if the KB article does describe the problem you are
facing installing SQL Server 2000 SP4 would probably solve it.
Let me know if this helps,
Kind regards Leon Krancher.
P.s. Most Servers I know that use a high-end storage device contain more
than 4Gb of ram. If this is also the case in your scenario you might also
want to take a look at http://support.microsoft.com/kb/899761. This KB
article describes a problem with AWE on SQL Servers with SP4 installed and
points to the additional fix that has to be installed to cure this.
"Joe K." wrote:

> I have a server with Windows 2003 Server with SQL Server 2000 Cluster Server.
> What could cause the error listed below with SQL Server 2000.
> Thanks
> Process 174:0 (cb8) UMS Context 0x000006FBFE8C88B1 appears to be
> non-yielding on Scheduler 6
> Process 140:0 (700) UMS Context 0x000006FBFE8A7230 appears to be
> non-yielding on Scheduler 0.
|||And it's fixed in SP4
Nik Marshall-Blank MCSD/MCDBA
"Leon" <Leon@.discussions.microsoft.com> wrote in message
news:92979375-B688-4CD1-9B67-3EE1EDAD273E@.microsoft.com...[vbcol=seagreen]
> Hi Joe K,
> I once had a similar problem with SQL Server, in my case it was caused by
> the fact that we used highend SAN's that allocated disk space to quickly.
> (Imagine that, problems caused by disks being to fast instead of to slow)
> The KB article related to this problem is
> http://support.microsoft.com/kb/810885.
> Unfortunately your post didn't contain the actual error code so I can't
> verify if the problem described in the KB article is the one you are
> experiencing. However if the KB article does describe the problem you are
> facing installing SQL Server 2000 SP4 would probably solve it.
> Let me know if this helps,
> Kind regards Leon Krancher.
> P.s. Most Servers I know that use a high-end storage device contain more
> than 4Gb of ram. If this is also the case in your scenario you might also
> want to take a look at http://support.microsoft.com/kb/899761. This KB
> article describes a problem with AWE on SQL Servers with SP4 installed and
> points to the additional fix that has to be installed to cure this.
>
> "Joe K." wrote: