Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sarat
Constraint Violating Yak Guru
265 Posts |
 Posted - 2004-01-15 : 11:59:12
|
| Hi, Can anyone help me interpret this message?2004-01-15 01:50:07.79 server Error: 17883, Severity: 1, State: 02004-01-15 01:50:07.79 server The Scheduler 0 appears to be hung. SPID 113, ECID 0, UMS Context 0x04708930.Also, I have am index job which runs wednesday night per schedule but got stuck. the text file showed me the table which was last indexed but when i ran the script in qa in a different database, it ran fine.Is the server or script a problem? Since this is a custom stored proc, nothing is written to the error log.Thanks,Sarat.**To be intoxicated is to feel sophisticated, but not be able to say it.** |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-15 : 12:21:42
|
| I suggest restarting the SQLServerAgent service. I have never seen that error message, but to me a restart would be the first step. Just because it is a custom stored proc, that doesn't mean info is not written to the error log. If your stored procedure for example did BACKUPs, that info would go into the error log.Tara |
 |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2004-01-16 : 14:40:18
|
| The Scheduler in this context refers to the User Mode Scheduler (UMS) rather than SQLAgentINF: New Concurrency and Scheduling Diagnostics Added to SQL Server[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;319892[/url] |
|
|
|
|
|
|
|
|
Error Msg related to Scheduler