SQL Server Performance Forum – Threads Archive

Error: 17883 :

Last night 3 sql Servers (out of more than 100 sql servers) in my organization hung with Error: 17883. Process 17:0 (0) UMS Context 0x11D40128 appears to be non-yielding on Scheduler 1. When I looked at MS support site , I found the following article. This article talks about the scheduler error and a fix in MS03-031. We are already running MS03-031 on all our SQL Servers. http://support.microsoft.com/default.aspx?scid=kb;en-us;815056#kb4 Another article talks about the same being fixed in SP4. http://support.microsoft.com/kb/810885/ Another aspect was that it was not just SQL Servers , there were other 2 windows servers that crashed last night as well. 3 were SQL server out of the 5 servers that crashed. I dont have access to the other 2 windows servers, but I reviewed event log on the SQL boxes and dint find anything signigicant. Has anyone encountered this error ?? I am trying to understand the cause and fix for this issue. Anything that you can add is greatly appreciated. Thanks Much.
Priya

Did you change anything in the environment recently (rollout of a Virus Scan update, windows updates, etc)? MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.

Try switching off parallelism and check whether this alert comes out right after a scheduled job.
Collect PERFMON stats 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.

No. Nothing changed on these environments lately, no new patches, no virus scans.

Check SP_CONFIGURE value for ‘max degree of parallelism’ on the servers. 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 all your responses. It turned out to be because of some new software that our data security had pushed out to the boxes. we have disabled that now.

The reason behind this is nothing but that new software was trying to access the same location of hard disk where the SQL Server is trying to access, in similar situation at my end it was Parallelism. 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.

]]>