Error: 17884

I'm looking for more information on Error: 17884
Error: 17884, Severity: 1, State: 0
Potential deadlocks exist on all the schedulers
I have done a google and usenet search and not found alot on scheduler
deadlocks
other types of deadlocks are commen, not scheduler deadlocks
The following kb article is not alot of help either
http://support.microsoft.com/kb/319892
Error 17882 and 17884
These messages indicate that all the UMS schedulers have experienced yield
problems. This indicates a SQL Server system wide problem and SQL Server
will appear to have stopped responding. As with the 17881 and 17883
messages, consult the error log and Microsoft the Knowledge Base for more
information. If necessary, engage in extended support efforts.
I am wondering if someone may have more information on this so I can try a
few things before opening a ticket with MS. The last time I had to open a
ticket they were helpful, and did help us solve the problem, but it took
many weeks.
I have had problems with temp db and our disk system in the past, that was
resolved and it has been about a year of fairly smooth running until this
popped up. It seems to happen once a week, or once every two weeks with
seemingly no pattern.
If you think you may have some ideas and need more information I will try to
get it for you.
It is a heavily used 24x7 database with alot of stress on the disk system
sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in a
hardware raid10
thanks,
DaveVDave V wrote:
> I'm looking for more information on Error: 17884
> Error: 17884, Severity: 1, State: 0
> Potential deadlocks exist on all the schedulers
> I have done a google and usenet search and not found alot on scheduler
> deadlocks
> other types of deadlocks are commen, not scheduler deadlocks
> The following kb article is not alot of help either
> http://support.microsoft.com/kb/319892
> Error 17882 and 17884
> These messages indicate that all the UMS schedulers have experienced
> yield problems. This indicates a SQL Server system wide problem and
> SQL Server will appear to have stopped responding. As with the 17881
> and 17883 messages, consult the error log and Microsoft the Knowledge
> Base for more information. If necessary, engage in extended support
> efforts.
> I am wondering if someone may have more information on this so I can
> try a few things before opening a ticket with MS. The last time I had
> to open a ticket they were helpful, and did help us solve the
> problem, but it took many weeks.
> I have had problems with temp db and our disk system in the past,
> that was resolved and it has been about a year of fairly smooth
> running until this popped up. It seems to happen once a week, or once
> every two weeks with seemingly no pattern.
> If you think you may have some ideas and need more information I will
> try to get it for you.
> It is a heavily used 24x7 database with alot of stress on the disk
> system
> sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in
> a hardware raid10
>
> thanks,
> DaveV
Sounds like an internal problem with SQL Server related to your disk
subsystem. I would open a support ticket immediately.
--
David Gugick
Imceda Software
www.imceda.com|||Hi
If it is disk subsystem as David suggests, KB 810885 describes the issue.
It have only seen this on large EMC systems and your drive subsystem does
not seem to be fast enough to have this problem.
I would install Hotfix 878 as I have seen a lot of scheduler issues fixed in
that timeframe.
http://support.microsoft.com/default.aspx?scid=kb;en-us;838166
That hotfix is the highest publicly available hotfix you can download
without opening a support incident. If it does not help, open a case with
PSS.
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/
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:O6LzmtQ1EHA.936@.TK2MSFTNGP12.phx.gbl...
> Dave V wrote:
> > I'm looking for more information on Error: 17884
> >
> > Error: 17884, Severity: 1, State: 0
> > Potential deadlocks exist on all the schedulers
> >
> > I have done a google and usenet search and not found alot on scheduler
> > deadlocks
> >
> > other types of deadlocks are commen, not scheduler deadlocks
> >
> > The following kb article is not alot of help either
> >
> > http://support.microsoft.com/kb/319892
> >
> > Error 17882 and 17884
> >
> > These messages indicate that all the UMS schedulers have experienced
> > yield problems. This indicates a SQL Server system wide problem and
> > SQL Server will appear to have stopped responding. As with the 17881
> > and 17883 messages, consult the error log and Microsoft the Knowledge
> > Base for more information. If necessary, engage in extended support
> > efforts.
> >
> > I am wondering if someone may have more information on this so I can
> > try a few things before opening a ticket with MS. The last time I had
> > to open a ticket they were helpful, and did help us solve the
> > problem, but it took many weeks.
> >
> > I have had problems with temp db and our disk system in the past,
> > that was resolved and it has been about a year of fairly smooth
> > running until this popped up. It seems to happen once a week, or once
> > every two weeks with seemingly no pattern.
> >
> > If you think you may have some ideas and need more information I will
> > try to get it for you.
> >
> > It is a heavily used 24x7 database with alot of stress on the disk
> > system
> >
> > sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in
> > a hardware raid10
> >
> >
> > thanks,
> > DaveV
> Sounds like an internal problem with SQL Server related to your disk
> subsystem. I would open a support ticket immediately.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>sql