none
Stack Dump on SQL server 2014 for solarwind application RRS feed

  • Question

  • Hi All,

    I am facing  one problem in Microsoft SQL server 2014 solar wind application is running on it.  after some period  stack dump generated on this SQL server , I tried to analyze this Dump on windbg  and found below output  which  I am not able to understand. can someone help me in this.

    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 2

    DUMP_QUALIFIER: 400

    CONTEXT:  (.ecxr)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na pe nc
    cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000
    00000000`00000000 ??              ???
    Resetting default scope

    FAULTING_IP:
    sqllang+f1ee01
    00007ffc`abfcee01 488b042530000000 mov     rax,qword ptr [30h]

    EXCEPTION_RECORD:  (.exr -1)
    ExceptionAddress: 00007ffcabfcee01 (sqllang+0x0000000000f1ee01)
       ExceptionCode: 00000000
      ExceptionFlags: 00000000
    NumberParameters: 0

    WRONG_SYMBOLS_TIMESTAMP: 5c7f684f

    WRONG_SYMBOLS_SIZE: 1ad000

    FAULTING_MODULE: 00007ffcb9b90000 ntdll

    DEBUG_FLR_IMAGE_TIMESTAMP:  5c7f684f

    ADDITIONAL_DEBUG_TEXT: 
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

    ANALYSIS_SESSION_HOST:  TTRAFLON2K867

    ANALYSIS_SESSION_TIME:  09-12-2019 10:32:14.0367

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    MANAGED_CODE: 1

    MANAGED_ENGINE_MODULE:  clr

    STACK_TEXT: 
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


    SYMBOL_STACK_INDEX:  0

    FOLLOWUP_NAME:  MachineOwner

    STACK_COMMAND:  .ecxr ; kb ; ~0s; .ecxr ; kb

    BUGCHECK_STR:  5C7F684F

    EXCEPTION_CODE: (NTSTATUS) 0x5c7f684f - <Unable to get error code text>

    EXCEPTION_CODE_STR:  5C7F684F

    EXCEPTION_STR:  PRIVATE_SYMBOLS

    PROCESS_NAME:  ntdll.wrong.symbols.dll

    IMAGE_NAME:  ntdll.wrong.symbols.dll

    MODULE_NAME: ntdll_wrong_symbols

    SYMBOL_NAME:  ntdll_wrong_symbols!5C7F684F1AD000

    BUCKET_ID:  PRIVATE_SYMBOLS_X64_6.3.9600.19358_(winblue_ltsb_escrow.190505-1600)_TIMESTAMP_190306-062727

    DEFAULT_BUCKET_ID:  PRIVATE_SYMBOLS_X64_6.3.9600.19358_(winblue_ltsb_escrow.190505-1600)_TIMESTAMP_190306-062727

    PRIMARY_PROBLEM_CLASS:  PRIVATE_SYMBOLS

    FAILURE_BUCKET_ID:  PRIVATE_SYMBOLS_X64_6.3.9600.19358_(winblue_ltsb_escrow.190505-1600)_TIMESTAMP_190306-062727_5C7F684F_ntdll.wrong.symbols.dll!5C7F684F1AD000

    FAILURE_EXCEPTION_CODE:  5C7F684F

    FAILURE_IMAGE_NAME:  ntdll.wrong.symbols.dll

    BUCKET_ID_IMAGE_STR:  ntdll.wrong.symbols.dll

    FAILURE_MODULE_NAME:  ntdll_wrong_symbols

    BUCKET_ID_MODULE_STR:  ntdll_wrong_symbols

    FAILURE_FUNCTION_NAME:  5C7F684F1AD000

    BUCKET_ID_FUNCTION_STR:  5C7F684F1AD000

    BUCKET_ID_OFFSET:  0

    BUCKET_ID_MODTIMEDATESTAMP:  0

    BUCKET_ID_MODCHECKSUM:  0

    BUCKET_ID_MODVER_STR:  0.0.0.0

    BUCKET_ID_PREFIX_STR:  PRIVATE_SYMBOLS_X64_6.3.9600.19358_(winblue_ltsb_escrow.190505-1600)_TIMESTAMP_190306-062727

    FAILURE_PROBLEM_CLASS:  PRIVATE_SYMBOLS

    FAILURE_SYMBOL_NAME:  ntdll.wrong.symbols.dll!5C7F684F1AD000

    TARGET_TIME:  2019-09-12T01:10:06.000Z

    OSBUILD:  9200

    OSSERVICEPACK:  19358

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  3

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 8

    OSEDITION:  Windows 8 Server TerminalServer SingleUserTS

    OS_LOCALE: 

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2019-05-06 03:41:50

    BUILDDATESTAMP_STR:  190505-1600

    BUILDLAB_STR:  winblue_ltsb_escrow

    BUILDOSVER_STR:  6.3.9600.19358

    ANALYSIS_SESSION_ELAPSED_TIME:  140

    ANALYSIS_SOURCE:  UM

    FAILURE_ID_HASH_STRING:  um:private_symbols_x64_6.3.9600.19358_(winblue_ltsb_escrow.190505-1600)_timestamp_190306-062727_5c7f684f_ntdll.wrong.symbols.dll!5c7f684f1ad000

    FAILURE_ID_HASH:  {bda99ce3-caf6-0a37-2348-7ade1176bf01}

    Followup:     MachineOwner
    ---------

    Thursday, September 12, 2019 9:38 AM

Answers

  • Hi subhendu.tiwari, 

    As others mentioned, maybe you can ask professional engineer for help, and they will deal with your problem separately and confidentially. https://support.microsoft.com/en-us/assistedsupportproducts

    Best regards,
    Cathy 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, September 13, 2019 5:40 AM

All replies

  • Don't waste your time to analyse stack dumps of SQL Server; you won't find any useful. Only MS Software engineers have the right Tools & source code to Analyse it.

    Take care you are on latest patch level and if that issue still occurs, then raise a Support case at Microsoft.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Thursday, September 12, 2019 9:54 AM
    Moderator
  • If the stack dump keep generating then it raise a case with Microsoft & they can able to get you what exactly possible from the stack dump.

    It's difficult for others to understand about each class in it.

    First thing hope your SQL version is up to date interms of SP,if not please get it apply first.


    Regards, S_NO "_"

    Thursday, September 12, 2019 10:06 AM
  • What is output of select @@version

    Cheers,

    Shashank

    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

    MVP

    Thursday, September 12, 2019 11:46 AM
    Moderator
  • Do not waste your time trying to read the dump file. There is nothing useful to you in that file.

    Before pursing this any further, make sure you have the latest Service Pack and CU installed.  If that does not fix it, then contact MS Support.  MS is horrible about publicly documenting changes.  Even though you do not find anything in the release notes related to your issue, does NOT mean it is not fixed.

    https://support.microsoft.com/en-us/help/321185/how-to-determine-the-version-edition-and-update-level-of-sql-server-an

    Thursday, September 12, 2019 12:48 PM
    Moderator
  • Hi subhendu.tiwari, 

    As others mentioned, maybe you can ask professional engineer for help, and they will deal with your problem separately and confidentially. https://support.microsoft.com/en-us/assistedsupportproducts

    Best regards,
    Cathy 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, September 13, 2019 5:40 AM