QMSED.EXE和clr.dll的问题 [英] Problems with QMSED.EXE and clr.dll

问题描述

我使用.bat文件和程序qmsedx.exe，以便用户每次需要时都可以重新处理某些应用程序.它一直没有问题，但是我注意到，这在Windows 10上不起作用，每次用户尝试重新处理该应用时，它都会向他们显示 qmsed.exe已停止工作.

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. 

我有Windows Server 2008 R2标准Service Pack 1，并使用QlikView Server Edition 11.20.12451.0 SR7 64位

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?

预先感谢！

-----

这是补充我的问题的两个XML文件:

Here are the two XML files for complementing my problem:

<?xml version ="1.0" encoding ="utf-8" standalone =是"?>
<事件><事件xmlns ='http://schemas.microsoft.com/win/2004/08/events/event'><系统><提供者名称='.NET Runtime'/>< ; EventID Qualifiers ='0'> 1023</EventID>< Level> 2</Level>< Task> 0</Task><关键字> 0x80000000000000</Keywords>< TimeCreated SystemTime ='2017-01-25T16:15:15.297734100Z'/>< EventRecordID> 46103</EventRecordID>< Channel>应用程序</Channel><计算机> F3ZZT32.imsalum.com</Computer>安全/</System>< EventData><数据>应用程序: QMSEDX.exe
框架版本:v4.0.30319
说明:由于.NET运行时中的内部错误(IP 736CFDF9(73550000)，退出代码为80131506.)，该进程已终止.
</Data></EventData>< RenderingInfo Culture ='en-US'><消息>应用程序:QMSEDX.exe
框架版本:v4.0.30319
说明:由于.NET运行时中的内部错误(IP 736CFDF9(73550000)，退出代码为80131506.)，该进程已终止.
</消息><错误</Level><任务></任务< Opcode> Info</Opcode>< Channel></Channel>< Provider></Provider> <关键字><关键字>经典</关键字></关键字</RenderingInfo></事件></事件>

<?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>

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

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

推荐答案

您好，qlikit，

Hi qlikit,

感谢您在MSDN论坛中发帖.

Thank you for posting in MSDN forum.

我注意到该异常发生在Framework版本:v4.0.30319

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

首先，请安装此修补程序: http://support.microsoft.com/kb/2640103

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

然后还请参见以下错误消息:

Then also see the error message as below:

>>说明:由于.NET Runtime中的内部错误(IP 736CFDF9)，该进程已终止(73550000) ，退出代码为80131506 .

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

从.NET 4.0开始的ExecutionEngineException，此异常立即终止程序.普遍原因是垃圾收集堆的状态损坏.反过来，这又总是由非托管代码引起的. 在代码中引发此异常的确切位置无济于事，损坏通常在检测到损坏之前就已经发生了.

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.

要找到确切原因，将非常困难.查看您的服务可能正在使用的任何非托管代码.如果没有明显的候选者，则怀疑环境问题，恶意软件扫描仪的行为是臭名昭著的.如果重复 然后非常难以怀疑的是诸如软RAM错误之类的硬件问题.

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.

此外，并发实施垃圾回收的错误 x64 .Net 4 可能会导致此问题，如以下Microsoft KB条目所述:

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

ExecutionEngineException occurs during Garbage Collection

您首先应该进行深入的小型转储研究，以确保问题在垃圾回收期间发生.

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

通常，可以在崩溃条目后面的事件日志的Windows错误报告条目中找到minidump位置.

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

最好的问候

这篇关于QMSED.EXE和clr.dll的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！