none
SQL 2005 x64 exception RRS feed

  • Question

  • 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

     
    Friday, April 25, 2014 1:19 PM

All replies

  • Hello,

    You are already patched to SP4 so its would be unfair to say you are not running supported version.IMO you should raise a case with MS guys and allow them to analyze dumps.It can be bug in system or can be some rouge query running on your system BTW what were you doing when you got this message.Did SQL server restarted ?


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers


    Friday, April 25, 2014 1:25 PM
    Moderator
  • I see "sqlshield" in your stack dump.  I would suggest contacting them and seeing if there is a patch or some other known issue.

    The exception C0000264 is "Resource Not Owned".  This sounds like a permissions issue to something, but I could be wrong.

    Friday, April 25, 2014 1:42 PM
    Moderator
  • SQL server was not actually restarted. SQL process was in some unresponsive state. But all applications stopped working. So we've end the SQL process and restart the SQL service again. What do you think can i catch some rouge query with profiler in that situation with exception?

    Regards,

    Matjaž

    Friday, April 25, 2014 2:05 PM
  • SQL server was not actually restarted. SQL process was in some unresponsive state. But all applications stopped working. So we've end the SQL process and restart the SQL service again. What do you think can i catch some rouge query with profiler in that situation with exception?

    Regards,

    Matjaž

    Profiler wont help as since you restarted SQL server you probably cannot capture it. I doubt there would be any thing in cache for DMV to get information from.I suggest you to get SQL dump ,which got generated , analyzed by Microsoft expert. 

    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Friday, April 25, 2014 2:58 PM
    Moderator
  • I agree with what Tom has said, in addition:

    SQL Shield uses something called "detouring" here is a KB article explaining about it and thatIT IS NOT SUPPORTED for SQL Server.

    http://support.microsoft.com/kb/920925/en-us


    Sean Gallardy | Blog | Twitter

    Friday, April 25, 2014 3:46 PM
    Answerer
  • Hi,

    We've checked about sqlshield from the vendor of one application which also use SQL, and the version is the latest.

    Here is another stack from the today's exception. Any idea, what to check?

    Regards,

    Matjaž

    0:000> .ecxr
    rax=0000000077207080 rbx=0000000000000000 rcx=000000001a677ed0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000440
    rip=00000000772070bd rsp=000000001a6783c0 rbp=000000000000003f
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000287 r12=00000000032fdab0 r13=0000000000000000
    r14=00000000000017a4 r15=00000000d0ff7bd4
    iopl=0         nv up ei pl nz na pe nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
    kernel32!RaiseException+0x39:
    00000000`772070bd 4881c4c8000000  add     rsp,0C8h
    0:000> kc 1000
    Call Site
    kernel32!RaiseException
    sqlservr!CDmpDump::Dump
    sqlservr!CImageHelper::DoMiniDump
    sqlservr!stackTrace
    sqlservr!stackTraceCallBack
    sqlservr!ex_handle_except
    kernel32!UnhandledExceptionFilter
    ntdll!RtlpNotOwnerCriticalSection
    ntdll!_C_specific_handler
    ntdll!RtlpExecuteHandlerForException
    ntdll!RtlDispatchException
    ntdll!RtlRaiseStatus
    ntdll!RtlpNotOwnerCriticalSection
    ntdll! ?? ::FNODOBFM::`string'
    sqlshield
    0x0

    Monday, April 28, 2014 12:13 PM
  • Here is another stack from the today's exception. Any idea, what to check?

    Can you disable/uninstall sqlshield to see if the problem goes away?


    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

    Monday, April 28, 2014 12:23 PM
    Moderator
  • Very difficult. There are running financial applications which are related to this database and sqlshield.

    But i'm not sure that this is the main problem. Do you maybe know for some additional patches after SP4 and CU3 for SQL 2005 x64?.

    Regards,

    Matjaž 

    Monday, April 28, 2014 12:54 PM
  • Hello,

    Since sqlshield was part of the execption stack, that means it was inside sqlshield's code. Also, since dtouring isn't supported and you're having issues on a version of sql server that is out of mainstream support the only option I see is to disable sql shield. If this is not possible you aren't going to receive any help from MS in fixing this and you're only solution would be to let thing keep crashing.

    Choice1: Let things keep crashing.
    Choice2: Disable SQL Shield and see if it goes away. If it does you have your root cause.

    To reiterate: You're using multiple items either not supported or out of bug/patch support. There is nothing more we can really help you with.


    Sean Gallardy | Blog | Twitter

    Monday, April 28, 2014 1:29 PM
    Answerer
  • I still reiterate my part,if you feel uneasy with disabling Sqlshield please log a case with MS they would analyse your scenario and would tell you better way to disable it with minimum possible or not change.If you are ok with yourself you can go ahead.Opening a case would also let MS analyze your dumps and can point any other facts necessary.

    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Monday, April 28, 2014 2:27 PM
    Moderator
  • As soon as I read your stack dump, that is exactly what I saw too. sqlshield is almost certainly the problem. If your dumps are not from a sensitive instance containing sensitive information Id be happy to analyze them for you. Alternatively you could crack open the debugger yourself and have a go...

    Id uninstall sqlshield immediately and then see how stable your instance is post doing so.


    Regards,
    Mark Broadbent
    Contact me through twitter | blog | sqlcloud


    Please click "Propose as answer" if a post solves your problem
    or/and vote the post up if it's been helpful.

    Want professional SQL Server High Availability Training? Click here

    Monday, April 28, 2014 5:40 PM
  • Looks like sqlshield again. The FNODOBFM call is a little misleading and most probably can be ignored. This is almost certainly the degugger just getting its knickers in a twist for some of its public symbols.

    Regards,
    Mark Broadbent
    Contact me through twitter | blog | sqlcloud


    Please click "Propose as answer" if a post solves your problem
    or/and vote the post up if it's been helpful.

    Want professional SQL Server High Availability Training? Click here

    Monday, April 28, 2014 5:48 PM
  • 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          

    Sunday, May 4, 2014 8:10 PM