UMS Scheduler Hang

[kmounkhaty@yahoo.com]

Hi Guru,

Our HR sql 2000 production server is 800.760 built (SP3a) with 2GB of
RAM and 2 CPU hiper threading. This server is very low activity where
processor runs average 1-3 during the day. However, in the last two
months, I've seen the following message occurred a few times on this
server.

Error: 17883, Severity: 1, State: 0
The Scheduler 2 appears to be hung. SPID 0, ECID 0, UMS Context
0x0381F660.

I did extensive research and read both KB 815056 and 10885 but I could
not correlate these KBs in to my issue. The reason is, I don't think
our server is very busy to cause the checkpoint process to be delayed.
The database keeps growing only 5-10MB in a week and I allocated the
space during off hour.

What is the solution to fix this issue? Will I fix this issue by
applying the hotfix MS03-031?

Thanks so much,
Silaphet,

[Erland Sommarskog]

Re: UMS Scheduler Hang

kmounkhaty@yaho o.com (smounkhaty@bre mer.com) writes:[color=blue]
> Our HR sql 2000 production server is 800.760 built (SP3a) with 2GB of
> RAM and 2 CPU hiper threading. This server is very low activity where
> processor runs average 1-3 during the day. However, in the last two
> months, I've seen the following message occurred a few times on this
> server.
>
> Error: 17883, Severity: 1, State: 0
> The Scheduler 2 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0381F660.
>
> I did extensive research and read both KB 815056 and 10885 but I could
> not correlate these KBs in to my issue. The reason is, I don't think
> our server is very busy to cause the checkpoint process to be delayed.
> The database keeps growing only 5-10MB in a week and I allocated the
> space during off hour.
>
> What is the solution to fix this issue? Will I fix this issue by
> applying the hotfix MS03-031?[/color]

The message is not an error in itself, but a "service engine soon"
message, so as long as you don't notice any other problems on the
server, you could ignore it for now. Then again, on most occasions
when I've seen this, the server has been in really poor condition.

Some things to look for:
1) Any anti-virus on the machine?
2) Could there be any process that is trying to do GUI interaction
from xp_cmdshell or an OLE object?
3) If you already haven't, set the configuration parameter "max
degree of parallelism" to the number of physical processors. (SQL
Server rarely benefits from parallelism over HT processors, rather
the opposite.)

It is possible that the hotfix or SP4 could resolve the issue, but
that is far from certain.

If you are losing sleep over this, you may consider to open a case
with Microsoft for further investigation.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

Books Online for SQL Server 2005 at

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

Books Online for SQL Server 2000 at

http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx