none
Problems with QMSED.EXE and clr.dll RRS feed

  • Question

  • I use .bat files and the program qmsedx.exe so that users can reprocess some applications every time they need it. It has been working without problems but I noticed that this doesn't work with Windows 10, every time users try to reprocess the app it show them that qmsed.exe has stopped working. 

    I have Windows Server 2008 R2 Standard Service Pack 1 and using a QlikView Server Edition 11.20.12451.0 SR7 64-bit

    Does anybody knows about this problem?

    Thanks in advance!

    -----

    Here are the two XML files for complementing my problem:

    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <Events><Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='.NET Runtime'/><EventID Qualifiers='0'>1023</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2017-01-25T16:15:15.297734100Z'/><EventRecordID>46103</EventRecordID><Channel>Application</Channel><Computer>F3ZZT32.imsalum.com</Computer><Security/></System><EventData><Data>Application: QMSEDX.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 736CFDF9 (73550000) with exit code 80131506.
    </Data></EventData><RenderingInfo Culture='en-US'><Message>Application: QMSEDX.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 736CFDF9 (73550000) with exit code 80131506.
    </Message><Level>Error</Level><Task></Task><Opcode>Info</Opcode><Channel></Channel><Provider></Provider><Keywords><Keyword>Classic</Keyword></Keywords></RenderingInfo></Event></Events>

    ------------------

    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <Events><Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Application Error'/><EventID Qualifiers='0'>1000</EventID><Level>2</Level><Task>100</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2017-01-25T16:15:15.470694700Z'/><EventRecordID>46104</EventRecordID><Channel>Application</Channel><Computer>F3ZZT32.imsalum.com</Computer><Security/></System><EventData><Data>QMSEDX.exe</Data><Data>0.0.0.0</Data><Data>545ba880</Data><Data>clr.dll</Data><Data>4.6.1586.0</Data><Data>575a139f</Data><Data>c0000005</Data><Data>0017fdf9</Data><Data>2a50</Data><Data>01d277263654a048</Data><Data>\\VSN2K838\reload\QMSEDX.exe</Data><Data>C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll</Data><Data>bc648f49-9f67-4f62-898b-fad5dceed915</Data><Data></Data><Data></Data></EventData><RenderingInfo Culture='en-US'><Message>Faulting application name: QMSEDX.exe, version: 0.0.0.0, time stamp: 0x545ba880
    Faulting module name: clr.dll, version: 4.6.1586.0, time stamp: 0x575a139f
    Exception code: 0xc0000005
    Fault offset: 0x0017fdf9
    Faulting process id: 0x2a50
    Faulting application start time: 0x01d277263654a048
    Faulting application path: \\VSN2K838\reload\QMSEDX.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    Report Id: bc648f49-9f67-4f62-898b-fad5dceed915
    Faulting package full name: 
    Faulting package-relative application ID: </Message><Level>Error</Level><Task>Application Crashing Events</Task><Opcode>Info</Opcode><Channel></Channel><Provider></Provider><Keywords><Keyword>Classic</Keyword></Keywords></RenderingInfo></Event></Events>
    Thursday, January 26, 2017 7:05 PM

All replies

  • Hi qlikit,

    Thank you for posting in MSDN forum.

    I have noticed that the exception occurs at Framework Version: v4.0.30319

    Firstly, please install this hotfix: http://support.microsoft.com/kb/2640103

    Then also see the error message as below:

    >>Description: The process was terminated due to an internal error in the .NET Runtime at IP 736CFDF9 (73550000) with exit code 80131506.

    The ExecutionEngineException starting with .NET 4.0, this exception immediately terminates the program.  The generic cause is corruption of the state of the garbage collected heap.  Which in turn is invariably caused by unmanaged code.  The exact location in code at which this exception is raised isn't helpful, the corruption usually occurred well before the damage is detected.

    Finding the exact cause for this is going to be difficult.  Review any unmanaged code your service might be using.  Suspect environmental problems if there is no obvious candidate, misbehaving malware scanners are notorious.  If it repeats very poorly then suspect hardware problems like soft RAM errors.

    Besides, a bug in the concurrent implementation of the Garbage Collection on x64 .Net 4 can cause this as stated in the following microsoft KB entry:

    ExecutionEngineException occurs during Garbage Collection

    You should first make a deep minidump exploration to be sure that the problem occurred during a Garbage collection.

    The minidump location can usually be found in a Windows Error Reporting entry in the event log following the crash entry.

    Best Regards,


    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, January 27, 2017 2:55 AM
    Moderator
  • Hi qlikit,

    Is there any update about this issue? Have you solved it successfully?

    Would you mind sharing your result or solution here?

    If you think my reply is helpful, please mark my reply as answer, it will be easier for other members who meet similar problem.

    If the error persists, please let me know, I will help you for more troubleshooting,

    Best Regards,


    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.

    Tuesday, February 7, 2017 5:16 AM
    Moderator