September 22, 2005 at 11:27 am
Hi,
I posted this problem in the past and these errors keep happening. One of our developers who did some research into the problem stated that if we apply SP4, it would fix it. The errors are still continuing and here's what I got this morning:
09:25:17
Sleeping until external dump process completes.
Process 126:0 (157c) UMS Context 0x002A5A38 appears to be non-yielding on Scheduler 2.
Error: 17883, Severity: 1, State: 0
Stack Signature for the dump is 0x00000000
09:25:35
Resuming after waiting on external debug process for 14 seconds.
09:33:35 - 09:40:35
Process 84:0 (1290) UMS Context 0x05E9B898 appears to be non-yielding on Scheduler 3.
Error: 17883, Severity: 1, State: 0
Process 105:0 (508) UMS Context 0x05E94680 appears to be non-yielding on Scheduler 2.
Error: 17883, Severity: 1, State: 0
Process 76:0 (ba8) UMS Context 0x05E98F70 appears to be non-yielding on Scheduler 1.
Error: 17883, Severity: 1, State: 0
During the time of these errors, we could not access our SQL server. I got a message that SQL server could not be accessed due to network problems and our developer was in the middle of something and just hung. Our sever is responsive now, but I need to know what these errors mean and how do I go about troubleshooting them? Any one seen these errors before?
Thanks!
Isabelle
Thanks!
Bea Isabelle
September 22, 2005 at 12:08 pm
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply