Non Yielding scheduler

Can anyone review please and recommend for this
Current time is 00:51:59 07/29/14.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.0.2531.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Xeon(R) CPU E5530 @ 2.40GHz.
Bios Version is HP - 2
8 X64 level 8664, 14 Mhz processor (s).
Windows NT 6.0 Build 6002 CSD Service Pack 2.
Memory
MemoryLoad = 49%
Total Physical = 36852 MB
Available Physical = 18786 MB
Total Page File = 70733 MB
Available Page File = 53469 MB
Total Virtual = 8388607 MB
Available Virtual = 8350654 MB
***Unable to get thread context for spid 0
* BEGIN STACK DUMP:
* 07/29/14 00:51:59 spid 7332
* Non-yielding Scheduler

Hi Shanky,
This forum is one of my best teacher,but to clear confusion about this thread, earlier I posted for Non-yielding resource monitor bugcheck dump and this is for Non-yielding scheduler.
Thanks a lot.
All are almost same IMO in sense they point to bug in SQL Server. As you said you got three different SQL dumps in your 3 different environement but 2 of them were not updated to latest SP. One you confirmed as even after updating service pack
you still got error. If issue subsides after applying SP its good if it does not I strongly recommend you to open case with Microsoft. I agree it would require shedding some bucks but atleast you would get solution and have a relax mind. IMO only a Microsoft
engineer can analyze dumps in most accurate way. I am saying this with experience. So take your shot and ask MS guys to analyze it.
If you want to give it a shot refer link posted by Ashwin.
You are most welcome to post questions on forum.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Similar Messages

How to duplicate the Non-Yielding scheduler case?

I want to do some debugging practices for the Non-Yielding scheduler situation by windbg, so may I know is there any way to duplicate the issue?
Please click the Mark as Answer button if a post solves your problem!

I want to do some debugging practices for the Non-Yielding scheduler situation by windbg, so may I know is there any way to duplicate the issue?
Please click the Mark as Answer button if a post solves your problem!
Its very hard to duplicate the issue.See what causes the issue is when some poorly written query run from application and is such a complex one that it takes sceduler and does not gives it back.When query is submitted it is assigned thread to run and schedulers
run this thread.After query is completed this scheduler moves to run other thread now if query is such that it keeps on running and does not finishes your scheduler will be busy.So if you want to reproduce this issue (
Which could be dangerous and can lead to shutdown of SQL Server)
you need to submit a query which works in a way that it hogs scedulers.
I would advise to you not to run this on production( I guess you must be aware about this situation)
What you can also do is on this forum search for Non Yeilding schedulers and look for post where OP has posted Scheduler dump copy it to your environment and test it one such sceduler dump is in below thread
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/fbf1ad50-b9ae-4388-b03d-08374da85974/nonyielding-scheduler?forum=sqldatabaseengine
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
Thank you
Shanky.
I understand the theory for the Non-Yielding scheduler ,The reason I need to duplicate the issue in the test environment is just to study the debugging skills if I meet the Non-Yielding
scheduler situation later.
Please click the Mark as Answer button if a post solves your problem!

Non-yielding Resource Monitor - Issue on PROD server

Hi
My PROD server frequently restarting after generating below dump.
Pls help me to resolve the issues
=====================================================================
       BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5000.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current time is 11:33:40 01/23/12.
8 Unknown CPU 9., 3 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 99%
Total Physical = 65533 MB
Available Physical = 505 MB
Total Page File = 121256 MB
Available Page File = 46 MB
Total Virtual = 8388607 MB
Available Virtual = 8321060 MB
**Dump thread - spid = 0, PSS = 0x0000000000000000, EC = 0x0000000000000000
***Stack Dump being sent to E:\MSSQL2K5\MSSQL.1\MSSQL\LOG\SQLDump0111.txt
* BEGIN STACK DUMP:
*   01/23/12 11:33:40 spid 0
* Non-yielding Resource Monitor
* Short Stack Dump

Hi, everyone.
Do you have a solution for the mentioned problem? My dump looks like the dump in the first message. Server that runs ms sql server instance stops responding to any input, and I should reboot it. And yes I have MAX memory for the sql server set to 49152
My dump:
This file is generated by Microsoft SQL Server
version 11.0.3128.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Xeon(R) CPU X5650 @ 2.67GHz.
Bios Version is INTEL - 0
BIOS Date: 09/30/09 12:52:30 Ver: 08.00.10
24 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.2 Build 9200 CSD .
Memory
MemoryLoad = 99%
Total Physical = 73663 MB
Available Physical = 63 MB
Total Page File = 137151 MB
Available Page File = 61709 MB
Total Virtual = 8388607 MB
Available Virtual = 8302677 MB
**Dump thread - spid = 0, EC = 0x0000000000000000
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0023.txt
* BEGIN STACK DUMP:
* 03/16/15 00:05:40 spid 844
* Non-yielding Resource Monitor
* Short Stack Dump
Thanks!

Find the error in non-preemptive scheduling

package test.nonpreemptive;
public class NonPreemptiveScheduling
     public int[] getWaitingList(int[] process, int[] arrival, int[] burst)
          if(arrival[0]!=0)
               return new int[]{0};
               if(process.length!=arrival.length & process.length!=burst.length & arrival.length!=burst.length)
                    return new int[]{0};
          for(int i=0;i<burst.length;i++)
                    if(burst>=10 | burst[i]<=0)
                         return new int[]{0};
               for(int i=0;i<arrival.length;i++)
                    for(int j=i;j<arrival.length;j++)
                         if(arrival[i]>arrival[j])
                         return new int []{0};
               for(int i=0;i<arrival.length;i++)
                    for(int j=i+1;j<arrival.length;j++)
                         if(arrival[i]==arrival[j])
                              return new int []{0};
          int sum[] = new int[process.length];
          for(int i=0;i<process.length;i++)
               sum[i] = arrival[i]+burst[i];
          int temp1,temp2,temp3;
          for(int i=1;i<process.length;i++)
               for(int j=i;j<process.length;j++)
                    if(sum[i]>sum[j])
                         temp1 = process[i];
                         process[i] = process[j];
                         process[j] = temp1;
                         temp2 = arrival[i];
                         arrival[i] = arrival[j];
                         arrival[j] = temp2;
                         temp3 = burst[i];
                         burst[i] = burst[j];
                         burst[j] = temp3;
          int starttime[] = new int[process.length];
          int finaltime[] = new int[process.length];
          starttime[0] = arrival[0];
          finaltime[0] = burst[0];
          for(int i=1;i<process.length;i++)
               starttime[i] = finaltime[i-1];
               finaltime[i] = starttime[i]+burst[i];
          int waitingtime[] = new int[process.length];
          for(int i=1;i<process.length;i++)
               waitingtime[i] = finaltime[i] - (arrival[i]+burst[i]);
          int temp4,temp5;
          for(int i=0;i<process.length;i++)
               for(int j=i;j<process.length;j++)
                    if(process[i]>process[j])
                         temp4 = process[i];
                         process[i] = process[j];
                         process[j] = temp4;
                         temp5 = waitingtime[i];
                         waitingtime[i] = waitingtime[j];
                         waitingtime[j] = temp5;
          return waitingtime;
     // You could use this sample code to test your functions
     // Following main fucntion contains 3 representative test cases
     public static void main(String args[])
          //testcase 1:
          try
               int process[] = {1, 2, 3, 4};
               int arrival[] = {0, 2, 4, 5};
               int burst[] = {7, 4, 1, 4};
               int[] output = new NonPreemptiveScheduling().getWaitingList(process, arrival, burst);
               if(output!=null && output.length>0)
               for (int i = 0; i < output.length; i++)
                    System.out.print(output[i]+", ");
               System.out.println();
          catch (Exception e)
               e.printStackTrace();
          //testcase 2:
          try
               int process[] = {1, 2, 3};
               int arrival[] = {0, 4, 8};
               int burst[] = {6, 2, 1};
               int[] output = new NonPreemptiveScheduling().getWaitingList(process, arrival, burst);
               if(output!=null && output.length>0)
               for (int i = 0; i < output.length; i++)
                    System.out.print(output[i]+", ");
               System.out.println();
          catch (Exception e)
               e.printStackTrace();
          //testcase 3:
          try
               int process[] = {1, 2, 3, 4};
               int arrival[] = {2, 0, 4, 5};
               int burst[] = {7, 4, 1, 4};
               int[] output = new NonPreemptiveScheduling().getWaitingList(process, arrival, burst);
               if(output!=null && output.length>0)
               for (int i = 0; i < output.length; i++)
                    System.out.print(output[i]+", ");
               System.out.println();
          catch (Exception e)
               e.printStackTrace();
     //     testcase 4:
          try
               int process[] = {1, 2, 3, 4, 5, 6, 7};
               int arrival[] = {0, 2, 4, 5, 6, 7, 8};
               int burst[] = {7, 4, 1, 4, 6, 7, 2};
               int[] output = new NonPreemptiveScheduling().getWaitingList(process, arrival, burst);
               if(output!=null && output.length>0)
               for (int i = 0; i < output.length; i++)
                    System.out.print(output[i]+", ");
               System.out.println();
          catch (Exception e)
               e.printStackTrace();
I have been told that this code of non-preemeetive sheduling does not work for all the test cases... can u please help me out... if there is any problem regarding the code ?

anshul_bhandari wrote:
i am getting the correct output as desired...
but the person to whom i have to submit this code is refusing to accept it .. he says this code won't work for all the possible inputs...
what else can be the possible inputs for which this code won't work..Those statements contradict each other in terms of your other posts in this thread.
You have a set of test cases. Do you in fact know what the results of those cases should be? Or are you assuming that because you got some output that it is correct?
Or is there another set of test cases which you do not have access to?

How to stop SQL Server 2008 R2 generating SQLDump.mdmp files constantly?

Something went wrong with local SQL Server 2008 R2 and it constantly generates SQLDump.mdmp files. It generated 40Gb(!) of SQLDump.mdmp this morning. Server rebooted, but didn't help.
Any ideas what happened with SQL Server and how to stop SQLDump.mdmp files generation?
SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP |
My Blog about Information Management |
My twitter

Memory Dumps are generated automatically by the SQL Server under various circumstances - most of which indicate potential problems in the Instance or the machine. Some that I can recall right now are:
Database Corruption
Non-yielding scheduler
Non-yielding resource monitor
AV (Access Violation)
There can be several other reasons as well. SQL Server generates the dumps, so that these dumps can be analyzed to find out potential problems in the SQL Server.
IMHO, rather than trying to find out ways to stop the dumps from being generated, please try to find out potential problems in the Instance or the machine and fix that. This will stop the dump generation anyway.
In case you need any assistance in analyzing the Dumps, please feel free to engage Microsoft Support.
Suhas De
Please mark solved if your question is completely answered; vote it as helpful to help others find a solution quicker.
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog: http://blogs.msdn.com/b/suhde

Bugcheck dump for 11.0.3128.0

Hi,
I have a bugcheck dump file. I don't know how to use it for troubleshooting. Can someone please guide me?
Its SQL server 2012 3128 build. I was troubleshooting a performance issue when SQL server rebooted itself. Later I found this dump file. I do have more error log files etc. Please advise where should I begin from.
Thanks,
Current time is 14:48:07 01/07/14.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 11.0.3128.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AMD Opteron(TM) Processor 6276 .
Bios Version is INTEL - 6040000
VMW71.00V.0.B64.1206220901
2 X64 level 8664, 14 Mhz processor (s).
Windows NT 6.2 Build 9200 CSD .
Memory
MemoryLoad = 84%
Total Physical = 8191 MB
Available Physical = 1299 MB
Total Page File = 12479 MB
Available Page File = 3989 MB
Total Virtual = 8388607 MB
Available Virtual = 8372937 MB
***Unable to get thread context for spid 0
* BEGIN STACK DUMP:
* 01/07/14 14:48:08 spid 3916
* Non-yielding Scheduler

Hello Mudit,
Follow the steps in
http://mssqlwiki.com/2012/08/21/non-yielding-iocp-listener-non-yielding-scheduler-and-non-yielding-resource-monitor-known-issues-and-fixes/ and check if the stack matches any of the existing issues.If you don't find the matching stack post the stack here,
we will let you know the cause. Remember most of the Non-yield dumps are because of external conditions and SQL Server becomes victim.
If you want to understand what is Non-yielding condition please
http://mssqlwiki.com/2012/08/17/how-to-analyze-non-yielding-scheduler-dumps/
Thank you,
Karthick P.K |My blogs|My Scribbles|Twitter|My Facebook
Group|
www.Mssqlwiki.com
Please click the Mark as answer button and vote as helpful if this reply solves your problem

SQL 2005 x64 exception

Recently We've migrated SQL 2005 x86 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3. We migrate users (with standard approach by Microsoft) and application databases
to new server. Everything is looking ok, applications working. But we've got some SQL exceptions like below.
Is there any known bug related to that? Could someone help us.
Memory
MemoryLoad = 15%
Total Physical = 32733 MB
Available Physical = 27752 MB
Total Page File = 64782 MB
Available Page File = 60344 MB
Total Virtual = 8388607 MB
Available Virtual = 8355366 MB
**Dump thread - spid = 84, PSS = 0x00000000D1A43ED0, EC = 0x00000000D1A43EE0
***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0005.txt
* BEGIN STACK DUMP:
*   04/25/14 12:54:30 spid 84
* ex_handle_except encountered exception C0000264 - Server terminating
* Input Buffer 255 bytes -
There is also some output from debugger:
0:000> .ecxr
rax=0000000077207080 rbx=0000000000000000 rcx=0000000016a37d50
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000440
rip=00000000772070bd rsp=0000000016a38240 rbp=000000000000003f
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000287 r12=00000000032fdab0 r13=0000000000000000
r14=00000000000019e4 r15=0000000049b8d00c
iopl=0         nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b             efl=00000206
kernel32!RaiseException+0x3d:
00000000`772070bd 4881c4c8000000 add     rsp,0C8h
0:000> kC 1000
Call Site
kernel32!RaiseException
sqlservr!DmpGetClientExport
sqlservr!_____SQL______Process______Available
sqlservr!_____SQL______Process______Available
sqlservr!_____SQL______Process______Available
sqlservr!SQLExit
kernel32!UnhandledExceptionFilter
ntdll!RtlpNotOwnerCriticalSection
ntdll!_C_specific_handler
ntdll!RtlIntegerToChar
ntdll!_C_specific_handler
ntdll!RtlRaiseStatus
ntdll!RtlpNotOwnerCriticalSection
ntdll!LdrGetProcedureAddress
sqlshield
sqlservr
0x0
0x0
0x0
0x0
0x0

Hi,
In last days we "close" our SQL to some scanning security applications which could also do some things on our SQL. But it's only a guess. About sqlshield we do the unregister and register DLL's again. Now at last two exception is not the same situation.
Can you see something from there with "Non-yielding Scheduler". Is it also possible that it something wrong with the hardware. We're using new Cisco rack 1U server for that SQL server. I've also read someting about upgrading the BIOS, related to errors
"Non-yielding Scheduler". At the end i can also tell, that the server is alive for a couple of days, if there is no a lot activity on the server, i mean on national holidays, through weekend, etc.
Any new idea?
Thanks,
Matjaž
=====================================================================
       BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5266.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is Cisco0 - 0
BIOS Date: 08/20/13 06:01:31 Ver: 04.06.05
Current time is 11:17:16 04/30/14.
12 Unknown CPU 9., 14 Mhz processor (s).
Windows NT 6.0 Build 6002 CSD Service Pack 2.
Memory
MemoryLoad = 17%
Total Physical = 32733 MB
Available Physical = 26900 MB
Total Page File = 64782 MB
Available Page File = 59543 MB
Total Virtual = 8388607 MB
Available Virtual = 8355342 MB
***Unable to get thread context - no pss
* BEGIN STACK DUMP:
*   04/30/14 11:17:16 spid 0
* Non-yielding Scheduler
Stack Signature for the dump is 0x00000000000003AD

High resident memory size when creating in-memory db

Capsule summary: an in-memory db created with a cache size of 8 Gb reports a resident size of 2 Gb without any data stored in it.
Details:
We have a need for creating an entirely "in-memory" database, i.e. without a backing file store.The application in question will be writing to and reading from the db frequently, and there is no need to incur the penalty of writing out to disk.
I read the white paper "Writing In-Memory Applications" published by Oracle, and modified our db creation code accordingly. More or less all I did was to allow "open" to be called with a NULL instead of file name.
This seems to work just fine, in that no file is created, and both writing and querying seem to work correctly. However, the resident memory size, even without anything written to the database, seems inordinately high. For example, if I set the cache size to be 8 Gb (the size of physical memory on my Linux FC11 machine), the resident size reported by "top" is 2.0 Gb:
Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.7%us, 0.3%sy, 0.0%ni, 98.3%id, 0.6%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8114752k total, 8054072k used, 60680k free, 45344k buffers
Swap: 11717624k total, 204896k used, 11512728k free, 3977788k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
12827 rao 20 0 2243m 2.0g 9.9m S 0.0 26.0 0:01.53 pypix
Running strace on the process shows that there are three calls to mmap as soon as "open" is called, one of them being responsible for a majority of the allocation.
Is this expected behavior? The documentation explicitly states the following:
"... Note that the size you specify for your cache is actually a maximum size; DB will only use memory as required so if you specify a cache size of 1 GB but your data set is only ever 10 MB in size, then 10 MB is what the DB will use...."
This does not appear to be consistent with what I am seeing.
Any ideas on what I might be doing wrong?
Thanks in advance.

Have you checked what script is causing the issue ? anything from application ? and OLAP things running on this instance ? how many sql instances are running ? anyother application like sharepoint etc runinning on this host ?
Check If your SQL Server instance encounters the following conditions then there is a possibility of
Non-yielding scheduler (SQL Server 2005 and above for the first occurrence. This is equivalent to a 17883 dump in SQL Server 2000.)
Non-yielding resource monitor (SQL server 2005 and above for the first occurrence)
Non-yielding IOCP listener (SQL server 2005 and above for the first occurrence)
Deadlocked Schedulers (SQL server 2005 and above. This is equivalent to a 17884 in SQL Server 2000.)
Exceptions/Assertions
Database Corruption
Latch Timeout
Other conditions (eg: when DUMPTRIGGER is used to generate a dump for a particular exception)
http://www.sqlskills.com/BLOGS/PAUL/post/How-to-download-a-sqlservrpdb-symbol-file.aspx
http://support.microsoft.com/kb/311503
http://blogs.msdn.com/b/sqlcat/archive/2009/09/11/looking-deeper-into-sql-server-using-minidumps.aspx
Diagnose and Correct Errors 17883, 17884, 17887, and 17888
http://technet.microsoft.com/en-us/library/cc917684.aspx
Raju Rasagounder Sr MSSQL DBA

SQL Server Assertion: File: "logmgr.cpp" , line=5512

Hi All,
We are using Sql Server 2005 Express ,
we got the below exception of Sql Server Assertion
2014-11-17 00:26:12.59 spid51 Error: 17066, Severity: 16, State: 1.
2014-11-17 00:26:12.59 spid51 SQL Server Assertion: File: <"logmgr.cpp">, line=5512 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning
the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
2014-11-17 00:26:12.61 spid51 Error: 3624, Severity: 20, State: 1.
2014-11-17 00:26:12.61 spid51 A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running
DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
2014-11-17 00:27:34.81 Server Using 'dbghelp.dll' version '4.0.5'
2014-11-17 00:27:34.81 Server ***Unable to get thread context - no pss
2014-11-17 00:27:34.81 Server * *******************************************************************************
2014-11-17 00:27:34.81 Server *
2014-11-17 00:27:34.81 Server * BEGIN STACK DUMP:
2014-11-17 00:27:34.81 Server * 11/17/14 00:27:34 spid 0
2014-11-17 00:27:34.81 Server *
2014-11-17 00:27:34.81 Server * Non-yielding Scheduler
2014-11-17 00:27:34.81 Server *
2014-11-17 00:27:34.81 Server * *******************************************************************************
2014-11-17 00:27:34.81 Server Stack Signature for the dump is 0x000003E6
2014-11-17 00:27:35.75 Server External dump process return code 0x20000001.
External dump process returned no errors.
2014-11-17 00:27:35.75 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
99%. Interval: 75000 ms.
2014-11-17 00:28:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 135953 ms.
2014-11-17 00:29:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 195953 ms.
2014-11-17 00:30:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 255953 ms.
2014-11-17 00:31:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 315953 ms.
2014-11-17 00:32:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 375953 ms.
2014-11-17 00:33:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 435953 ms.
2014-11-17 00:34:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 495953 ms.
2014-11-17 00:35:05.77 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2014-11-17 00:35:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 555953 ms.
2014-11-17 00:36:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
97%. Interval: 615953 ms.
2014-11-17 00:37:35.77 Server Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
98%. Interval: 675953 ms.

Assertion error are usually some corruption in SQL Server database. And non yielding scheduler seems like bug what is output of
select @@Version
Did you tried running dbcc checkdb on SQL Server 2005 database
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Stack dump: SQL Server keeps crushing

My SQL Server keeps crushing with a stack dump error saying:
(in the management studio error log):
spid197 External dump process return code 0x20000001. External Dump process returned no errors.
spid197 Stack signature for dump is 0x000000014A5D4200
How can I investigate this further and what do these errors mean... also what does this return code mean and what does this signature dump code mean and where can I read more about them?
Thanks in advance,
Dror

Support article on this and related errors:
FIX: SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a "Non-yielding Scheduler" error is logged
http://support.microsoft.com/kb/2699013
Another support article:
FIX: SQL Server 2005 or SQL Server 2008 may stop responding when you are performing a backup
http://support.microsoft.com/kb/960543
Also run DBCC CHECKDB to check for database corruption:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea0099e9-3ad2-4713-8e4e-ca429041bf2d/sql-server-2008-r2-sp1-creates-dump-files-twice-a-minute-please-help?forum=sqldatabaseengine
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

No Context for module while using WinDbg

I would like to request some help with an issue reading a few SQL Server dumps. I'm currently analyzing a dump created by SQL Server 2012 Enterprise. The dump is due to a “Non-Yielding Scheduler” issue that has occurred at least 6 times with
in the last two weeks.
My issue is, I am unable to load the following symbol modules, while using WinDbg.
************* Symbol Loading Error Summary **************
Module name            Error
sqlevn70               No data is available : srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
SQLNCLIR11             No data is available : srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
msfte                  The system cannot find the file specified : srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
XPStar                 No data is available : srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
xplog70                No data is available : srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
Is this a known issue, has anyone seen this issue, and if so is there a workaround to the issue?
Thanks you for your help in advance.
Curtis

Hello,
Please read the following article to analyze further.
http://mssqlwiki.com/2012/08/17/how-to-analyze-non-yielding-scheduler-dumps/
The following fixed have been released about this too:
http://support.microsoft.com/kb/2699013
http://support.microsoft.com/kb/2672531
http://support.microsoft.com/kb/2846378
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to schedule BW archive job?

Hi all,
I will use Archive Development Kit to archive BW data. But I will not do it mannually by using SARA. Anybody knows how to schedule from non SAP scheduler.
BambooShampoo.

Hi,
You need to define jobs both in BW (Job1) and the third party system (Job2).
Trigger Job1 which will trigger BW job (Job2). You need to set the dependencies on Third Party tool for the third party jobs. No need to define any dependencies for the BW jobs. Individual BOX needs to be identified on third party tool.
Thx,
Soumya

Mythtv, auto shutdown no longer working, scheduler.cpp ?

Following a recent update the automatic shutdown of my backend is no longer working (well, at least not reliably).
I have 3 scripts set up in the relevant sections of the mythtv-setup to check if myth is ok to shut down, set the new wakeup time and perform the actual shutdown. These scripts still work alright, but the backend is not initiating the shutdown any more in some cases.
Lots of trial and error makes me think that this is somehow related to scheduler.cpp, but I am not sure if this is the case or how to fix it.
I think I have established a pattern:
Scenario 1:
- Boot backend
- do nothing else (e.g. start remote frontend or mythfrontend on the backend)
- automatic shutdown does not work
Scenario 2:
- Boot backend
- start remote frontend
- shut down frontend
- automatic shutdown does not work
- restart backend service (without reboot)
- automatic shutdown works
I also notice that in scenario 2 (when automatic shutdown works) there are a whole heap of these kind of messages right until shutdown occurs:
2013-04-29 19:18:07.592125 N [660/738] Expire autoexpire.cpp:641 (SendDeleteMessages) - Expiring 156 MB for 1073 at 2013-04-13T11:50:20Z => Hulk
2013-04-29 19:18:07.632899 E [660/660] CoreContext mainserver.cpp:2610 (DoHandleDeleteRecording) - ERROR when trying to delete file: myth://192.168.1.103:65103:6543/1070_20120126203445.mpg. File doesn't exist. Database metadata will not be removed.
2013-04-29 19:18:07.889638 E [660/660] CoreContext mainserver.cpp:2610 (DoHandleDeleteRecording) - ERROR when trying to delete file: myth://192.168.1.103:65103:6543/1022_20120206192600.mpg. File doesn't exist. Database metadata will not be removed.
In scenario 2 (successful) I see the following in the log just before the above auto expire stuff:
Scheduler scheduler.cpp:2307 (HandleRunSchedulerStartup) - Scheduler: Seem to be woken up by USER
then a whole heap of auto expiry stuff and finally:
Scheduler scheduler.cpp:2862 (CheckShutdownServer) - CheckShutdownServer returned - OK to shutdown
2013-04-29 19:19:55.276775 N [660/735] Scheduler scheduler.cpp:2947 (ShutdownServer) - Running the command to set the next scheduled wakeup time :-
sudo /home/laffi/scripts/MythSetWakeup 1367229120
2013-04-29 19:19:55.372582 N [660/735] Scheduler scheduler.cpp:2974 (ShutdownServer) - Running the command to shutdown this computer :-
sudo /home/laffi/scripts/MythShutdown
In scenario 1 (unsuccessfull shutdown) I also get
Scheduler scheduler.cpp:2307 (HandleRunSchedulerStartup) - Scheduler: Seem to be woken up by USER
and then autoexpiry, but then, once a frontend connects:
ProcessRequest mainserver.cpp:1385 (HandleAnnounce) - adding: frontend as a client (events: 0)
I don't get autoexpiry of files and no shutdown, both of which I believe are initiated by scheduler.cpp
I also noticed the following in the logs when auto shutdown does not work:
2013-04-29 15:40:36.046359 I [648/848] ProcessRequest mainserver.cpp:1385 (HandleAnnounce) - adding: mythbackend as a client (events: 1)
which does not seem to appear in the logs when auto shutdown works.
Any ideas ? I have found very little (next to none) regarding scheduler.cpp when searching.

The other side of the VPN is a TMG server hosted at our main office. I can connect to it off site, and others were connected to it remotely as well, but for some reason users at that remote site can no longer connect to the VPN.
I talked to my ISP wondering if there was something that was blocked due to the change from dhcp to static IP addresses, but they don't see anything.

Scheduling Agreement: Planning in Frozen Period

Hi,
as you know you can set 2 fixed periods for scheduling agreements and configure SAP to create fixed or non fixed schedule lines inside the period.
Do you know if there is anyway to configure the system in order to prevent it to create new schedule lines inside this period?
I explain better: we define a contract with the vendor and enstablish that there is a frozen period of 90 days, meaning that from here to 90 days your delivery schedule can't change in any way. Therefore i set the first fixed period of SA to 90 days and tell the system to create fixed schedule lines in that time interval, so they won't be changed. But if a new requirement in the past or within the 90 days comes out and the MRP runs with automatic schedule lines creation enabled, then i get more fixed schedule lines in the past and contractual parameters are violated.
Any way to prevent this?
Thanks and best regards

Hi,
Thanks for all your replies, mentioned settings are already maintained and I did check all the queques for any error.
OLTP transfer setting is also maintained as immediate..so I don't need to transfer change pointers through report, as it should immediately be transferred to ECC.
My question is: We have report - create release (transaction - /SAPAPO/PWBSCH1) to release scheduling agreement, so I believe for scheduling agreement we need to use above transaction.
It seems to work, as I can see IDOC but its in failed status.
I have following question:
- Does scheduling line release work in a different way than purchase req, in APO. I did test with purchase req and it was immediately transferred to ECC.
Has somebody worked for schedule agreement scenario in APO?
Any insights would be appreciated.
Thanks
Sharad

How to initiate scheduling msg delivery

Hi:
          I want to invoke a MDB every day at 22:00. The best way is to use Schedule class to deliver a same JMS msg to the MDB on my schedule.
          Now the question is when and where to initiate the scheduling?
          Is the start class in weblogic server the best place?
          Thanks,
          Tony

Hi Tony,
          I assume a startup class, or, likely more conveniently, a load-on-start-servlet, could be the right place, as long as it can reliably detect if there's already a scheduled timer (to avoid duplicate timers firing). Or perhaps a non-persistent scheduled message would suffice for your purposes, in which case there'd be no timer in the system when it boots.
          Side notes: When I look at scheduling of this nature, I worry about timer management first. Do the timers need to be easily canceled, paused, or modified? Will the timer still fire even if the server is booted a bit late - say 22:30? Pre 9.0 versions of WL don't provide the APIs necessary for JMS Scheduled message cancellation, pausing, or modification. The best place to initiate scheduling may actually be a UNIX cron job or NT Scheduled Task. Alternatively, WebLogic 9.0 provides persistent EJB timers that may suffice. And 9.2 will supply a "clustered timer" service (slightly less capable, but with higher HA characteristics).
          OK, I do run on a bit sometimes. Hope this helps.
          Tom, BEA

Non Yielding scheduler

Similar Messages

Maybe you are looking for