syscomments

RocketScientist's Miscellaneous Ramblings
posts - 76, comments - 354, trackbacks - 3

Error 17883

Here's one you hope you never see. "The Scheduler 0 appears to be hung". On SQL Server 2000, there's no fix, and there's not much you can do about it. My favorite part is that it logs the SPID involved (SPID 63 in my case) but it doesn't log what the SPID was doing. Given that my server was locked up so tight I couldn't even get in locally using command-line ISQL, I have no idea what caused the problem. Excellent diagnostic help there!

Print | posted on Monday, October 06, 2003 12:46 PM |

Feedback

Gravatar

# re: Error 17883

Would the hotfix (build 857 I think) which has new trace flags be of any help to you. Microsoft wanted us to apply it for the caching controller errors we were experiencing.
10/7/2003 11:37 PM | Lance Harra
Gravatar

# re: Error 17883

Possibly. I'm starting to get Error 3624 in my log also, which is from what I've read usually caused by some data corruption. Wonderful.

I'm not real fond of installing hotfixes on my servers. Anybody know when the next sp is due out?
10/9/2003 10:04 AM | RocketScientist
Gravatar

# re: Error 17883

I once compiled a pascal program on a HP-3000. The compiler came back with "Incorrect Magic Number"

No one ever diagnosed that one.
10/23/2003 12:33 AM | Tim
Gravatar

# re: Error 17883

I HAVE THE NEXT ERROR IN SQL LOG

Process 1:0 (c70) UMS Context 0x127F29A8 appears to be non-yielding on Scheduler 0.

ARE YOU KNOW WHAT IS THIS
1/5/2006 1:20 PM | FEDERICO SIXTO
Gravatar

# re: Error 17883

Please check if you have started SQL Server Agent - if Agent is not running then this error appears.
2/1/2006 11:03 AM | Mukesh Kumar
Gravatar

# re: Error 17883

eror c70 blick
2/28/2006 3:31 AM | orca
Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET