Home
%3CLINGO-SUB%20id%3D%22lingo-sub-383090%22%20slang%3D%22en-US%22%3EDiagnosing%2017883%2C%2017884%2C%2017887%2C%2017888%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-383090%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jun%2008%2C%202006%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EHave%20you%20ever%20seen%20an%20error%20like%3A%20%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3EProcess%2051%3A0%20(dbc)%20UMS%20Context%200x018DA930%20appears%20to%20be%20non-yielding%20on%20Scheduler%200.%3C%2FP%3E%0A%20%20%3CP%3EOr%20in%20SQL%20Server%202005%3A%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EProcess%2051%3A0%3A0%20(0xdbc)%20Worker%200x036BA0E8%20appears%20to%20be%20non-yielding%20on%20Scheduler%201.%20Thread%20creation%20time%3A%2012764721496978.%20Approx%20Thread%20CPU%20Used%3A%20kernel%2015%20ms%2C%20user%20171%20ms.%20Process%20Utilization%200%25.%20System%20Idle%2099%25.%26nbsp%3BInterval%3A%20325602683%20ms.%3C%2FP%3E%0A%20%20%3CP%3EIf%20you%20really%20want%20to%20get%20into%20the%20guts%20of%20SQL%20Server%20(specifically%20the%20scheduling%20parts)%2C%20there's%20a%20new%20whitepaper%20written%20by%20Robert%20Dorr%20in%20Product%20Support%20and%20Sameer%20Tejani%20in%20Product%20Development%20called%20'%20%3CEM%3E%20How%20to%20Diagnose%20and%20Correct%20Errors%2017883%2C%2017884%2C%2017887%2C%20and%2017888%20%3C%2FEM%3E%20'.%20You%20can%20download%20the%20paper%20at%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Ftechnet%2Fprodtechnol%2Fsql%2F2005%2Fdiagandcorrecterrs.mspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20http%3A%2F%2Fwww.microsoft.com%2Ftechnet%2Fprodtechnol%2Fsql%2F2005%2Fdiagandcorrecterrs.mspx%3C%2FA%3E%3C%2FP%3E%0A%20%20%3CP%3EIt%20provides%20great%20insight%20into%20the%20logic%20we%20have%20to%20detect%20'hang'%20situations%20and%20what%20you%20can%20do%20to%20resolve%20them%20(and%20it%20might%20make%20your%20brain%20hurt).%3C%2FP%3E%0A%20%20%3CP%3EEnjoy%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-383090%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jun%2008%2C%202006%20Have%20you%20ever%20seen%20an%20error%20like%3AProcess%2051%3A0%20(dbc)%20UMS%20Context%200x018DA930%20appears%20to%20be%20non-yielding%20on%20Scheduler%200.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-383090%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQLServerStorageEngine%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734749%22%20slang%3D%22en-US%22%3ERe%3A%20Diagnosing%2017883%2C%2017884%2C%2017887%2C%2017888%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734749%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20link%20is%20not%20working%3C%2FP%3E%0A%3CP%3EThere%20is%20more%20information%20on%20the%20topic%20in%20the%20following%20address%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fsql%2Fsql-server-2005%2Fadministrator%2Fcc917684(v%3Dtechnet.10)%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fsql%2Fsql-server-2005%2Fadministrator%2Fcc917684(v%3Dtechnet.10)%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft
First published on MSDN on Jun 08, 2006

Have you ever seen an error like:

Process 51:0 (dbc) UMS Context 0x018DA930 appears to be non-yielding on Scheduler 0.

Or in SQL Server 2005:


Process 51:0:0 (0xdbc) Worker 0x036BA0E8 appears to be non-yielding on Scheduler 1. Thread creation time: 12764721496978. Approx Thread CPU Used: kernel 15 ms, user 171 ms. Process Utilization 0%. System Idle 99%. Interval: 325602683 ms.

If you really want to get into the guts of SQL Server (specifically the scheduling parts), there's a new whitepaper written by Robert Dorr in Product Support and Sameer Tejani in Product Development called ' How to Diagnose and Correct Errors 17883, 17884, 17887, and 17888 '. You can download the paper at http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx

It provides great insight into the logic we have to detect 'hang' situations and what you can do to resolve them (and it might make your brain hurt).

Enjoy


1 Comment
R A
MVP

The link is not working

There is more information on the topic in the following address:

https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2005/administrator/cc917684(v=tech...