Welcome to dbForumz.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

UMS Context appears to be non-yielding on Scheduler

  
   Database Forums (Home) -> Server RSS
Next:  Database Loader, Explorer, Report system, ...  
Author Message
massimo70




Joined: Jun 13, 2005
Posts: 3



(Msg. 1) Posted: Mon Jun 13, 2005 11:13 am
Post subject: UMS Context appears to be non-yielding on Scheduler
Hi all,

Since a couple of days on our production server the following error:

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.

Some specs:
Intel Xeon 2CPU, 3.8GB 2.5GHz, HD 220GB
OS: Win 2K SP3
SQL Server 2000: Standard Edition SP4
AS 2000 SP4

Backups and complex queries are running and never ending...
SQL Server is stalled, low or no-responsive!!

1 weeks ago SP4 installed...
All info found on this topic did at the moment not help to solve this issue (i am aware about some missing fixes in SP4).
This morning MS Support contacted. Waiting for a call...
I just wanted to share my frustration and any help would be of course very appreciated.

Regards, Massimo

 >> Stay informed about: UMS Context appears to be non-yielding on Scheduler 
Back to top
Login to vote
phcahill




Joined: Jul 15, 2005
Posts: 2



(Msg. 2) Posted: Fri Jul 15, 2005 6:15 am
Post subject: Re: UMS Context appears to be non-yielding on Scheduler [Login to view extended thread Info.]
Any luck getting an answer? Dying here too.

 >> Stay informed about: UMS Context appears to be non-yielding on Scheduler 
Back to top
Login to vote
massimo70




Joined: Jun 13, 2005
Posts: 3



(Msg. 3) Posted: Fri Jul 22, 2005 5:09 am
Post subject: Re: UMS Context appears to be non-yielding on Scheduler [Login to view extended thread Info.]
No feedback from PSS after sending memdumps and logs files.
MS wanted to have a copy of prod db but customer did not allow us to do it. We have fixed the problem downgrading to SP3a. No everything works fine.
Cheers, Massimo
 >> Stay informed about: UMS Context appears to be non-yielding on Scheduler 
Back to top
Login to vote
phcahill




Joined: Jul 15, 2005
Posts: 2



(Msg. 4) Posted: Fri Jul 22, 2005 4:19 pm
Post subject: Re: UMS Context appears to be non-yielding on Scheduler [Login to view extended thread Info.]
We installed sp4 to try to help analyze some data corruption problems we were having. We had also turned off write caching on our controllers. I saw this happen directly after an auto grow.

We have moved to a new server and so far no corruption and no hangs of this type. So maybe it's caused by corruption checkdb() or slow disks on a large autogrow.

Paul
 >> Stay informed about: UMS Context appears to be non-yielding on Scheduler 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
External Scheduler Integration - Anyone have a simple script that might be used by an external scheduler such as Control-M to kick off .sql files and return back appropriate return codes and error messages. Spencer

no REPORTS option appears on management studio - installed reporting services on SQL 2005 instance but no REPORTS option appears on management studio. should be able to right click DATABASES from management studio to see this option :( thanks for any help Scott

Passing table variable as input parameter to stored proc - I understand you cannot pass a table variable as input parameter to a stored proc. But what is the alternative in my case? Current DB standards limit access of linked servers to the execution of stored procs and functions, no cross server joins. But...

Need Help in interpreting Lock:Timeout Error in SQL Profil.. - Hi, I need some help in interpreting trace from SQL profiler. I'm seeing a whole bunch of Lock:Timeout events in SQL Profiler Trace. >From the trace, it seems like for spid=118, database issues "SP:StmtStarting" event for opening a cursor f...

Urgent - General Network Error - Hi , I have a subscription that keeps failing to synchronise with the following error : "General Network Error. Check your network documentation" how can i check the cause & resolve ? kindly advise
   Database Forums (Home) -> Server All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]