I get the following message: Process 58:0 (0) UMS Contex 0x1238c4a0"

[nb45]

The following message appear in the SQL Logs:

2004-06-08 06:17:49.82 server Process 58:0 (0) UMS Context 0x1238C4A0 appears to be non-yielding on Scheduler
2004-06-08 06:17:49.82 server Error: 17883, Severity: 1, State: 0

What is the meaning of this messages?

Thanks

 

[JayKusch]

It means a process is not letting other processes have their share of needed resources.

Thanks

J. Kusch

 

[mpipolo]

I have got the same problem since last week with a SQL Server 2000 SP4. Previous to SP4 and with SP3 this error was never raised in log SQL...We have huge SQL DBs and AS Dbs with several cubes...We run into this problem with a server OS 2K SP3 with 2 CPUs, 3.8 GB RAM.
Here the extract from SQL log:

2005-06-12 23:28:49.65 server Error: 17883, Severity: 1, State: 0
2005-06-12 23:28:49.65 server Process 57:0 (658) UMS Context 0x061D0048 appears to be non-yielding on Scheduler 3.
2005-06-12 23:29:49.65 server Error: 17883, Severity: 1, State: 0

Now waiting for a call from MS. They have got mem dumps + logs...I will write again if I know what it is...
Note: several issues already with SQL SP4

Cheers, Massimo

 

[mrdenny]

As Jay said 17883 is a new error message in SQL SP3. The problem happened before SP3 it just wasn't logged.

It is caused by any number of things. It's kind of a catchall for a lot of possible issues. It can mean that your disks are running to slow, or that they are running to fast (ironic I know), as well as a few other options.

Basically a query was run, and it completed, however the SQL server is still waiting for a response from the disk. The problem is that the SQL server won't get a response because the response has already been sent, and the SQL Server missed it.

There are a couple of hot fixes that Microsoft has available that can clear these up. You just need to call Microsoft to get them.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(Not quite so old any more.)

 

[mpipolo]

Hi all,

I have re-installed SQL Server with SP3 and everything seems to work normally now.
MS Support contacted 2 days ago. My case has been handled by HP (? didn't know they were also doing support for Microsoft) but my mem dumps could not debeg cause a problem with symbols (?)...This case seems now to be forwarded to real MS Support. Stiil waiting for a feedback.
Conclusion: I will for the moment not advice to installa SP4.

Cheers, Massimo