SQL Server Performance Forum – Threads Archive
Find the cause of error 17883
We had one of our production SQL Servers lock up the other morning. A reboot fixed the problem but I noticed that at about 3:00 am, the following message came up in the log: Error: 17883, Severity: 1, State: 0The Scheduler 0 appears to be hung. SPID 12, ECID 0, UMS Context 0x252D2D08. I had a maintenance plan running between midnight and about 3:30 am so the one error didn’t surprise me that much. Then at about 8:00 am, it started to happen every few minutes until around 10:00 when the server just stopped responding. I know that if I install the hot-fix, it will improve the error message somewhat but, of course, it’s too late for this incident. Is there any good way to go back and figure out what processes were causing this error to be thrown? Thanks for any help you can offer.
it is a bug!!
http://www.kbalertz.com/kb_890637.aspx
I believe there is no chance to dig out and you may check the disk subsystem when this problem is occuring, collect PERFMON stats and SQLDIAG for more information. We have had this issue on one of the server and found to be faulty disk controller where the data file is located. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
Thanks for the responses. I don’t think that the article mentioned above applies to our error. The article specifically mentions that SPID 2 (LogWriter) would be mentioned in the error message. In our message it is SPID 12. If I find out more, I will post it here.
Also perform PERFMON capture during the occurence of these errors for further assessment. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
]]>