IBM.Data.DB2.iSeries的iSeries的.NET/C#DB2'FatalExecutionEngineError' [英] .NET/C# DB2 for iSeries 'FatalExecutionEngineError' from IBM.Data.DB2.iSeries
问题描述
从C#/.NET程序连接到开发(非实时)iSeries时遇到麻烦
Having trouble connecting from a C#/.NET program to a Development (non-live) iSeries
尝试打开新连接时遇到以下故障:-
Getting the following failure when trying to open a new connection:-
引发了'System.ExecutionEngineException'类型的异常."
"Exception of type 'System.ExecutionEngineException' was thrown."
HResult -2146233082
HResult -2146233082
托管调试助手'FatalExecutionEngineError'在'C:\ Users \ sclose \ Documents \ Visual Studio 2015 \ Projects \ iSeries1 \ iSeries1 \ bin \ Debug \ iSeries1.vshost.exe'中检测到问题.
Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\Users\sclose\Documents\Visual Studio 2015\Projects\iSeries1\iSeries1\bin\Debug\iSeries1.vshost.exe'.
其他信息:运行时遇到致命错误.错误的地址位于线程0x28bc上的0x71ccec3c.错误代码为0xc0000005.此错误可能是CLR或用户代码中不安全或不可验证的部分中的错误.该错误的常见来源包括COM-interop或PInvoke的用户封送处理错误，这些错误可能会破坏堆栈.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0x71ccec3c, on thread 0x28bc. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.
一个非常简单的noddy程序，它设置一个连接字符串并打开一个新连接:-
Just a very simple noddy program which sets a connection string and opens a new connection:-
string ConnectionString = "DataSource=MACH03Y;UserID=sysmon;Password=xxxxxxxxx;LibraryList=U1SCLOSE;Naming=System";
_connection = new iDB2Connection(ConnectionString);
已安装Windows的iAccess 7.1，并能够通过System i Navigator连接并登录到iSeries
Have iAccess for Windows 7.1 installed and am able to connect and sign on to the iSeries through System i Navigator
尝试:-
1)UserId和库列表的各种组合(有效和无效)
1) Various combinations of UserId's and Library lists (valid and invalid)
2)有效和无效的数据源值
2) Valid and Invalid DataSource values
3)不同的IBM.Data.DB2.iSeries.dll版本，包括最新版本
3) Different IBM.Data.DB2.iSeries.dll versions including the latest
总是一样的失败
我们知道相同的代码可以在实时环境中成功运行，但这可能是第一次在开发环境中进行尝试！
We know the same code works successfully in a live environment but this is maybe first time it's been tried in a dev environment!
通常在开发人员中，它使用模拟服务，并且与真正的iSeries无关.
Normally in dev it uses a mock service and goes nowhere near a real iSeries
与.NET相比，我在iSeries方面有更多的经验
I have more experience on the iSeries side than the .NET side
是否认为这可能是网络/防火墙问题?
Thinking it's maybe a Network/Firewall issue?
非常感谢收到任何帮助
推荐答案
每当我看到此错误时，都表明Visual Studio调试器存在问题.我认为这不是您的代码或IBM.Data.DB2.iSeries.dll的问题.
Whenever I have seen this error, it has been a problem with the Visual Studio Debugger. I do not think it is a problem with your code or the IBM.Data.DB2.iSeries.dll.
错误代码5是Windows中的访问冲突.这些调试器崩溃通常是通过升级Visual Studio或应用最新的Service Pack修复的.VS2015在很多方面都是很棘手的，因为它是完全重写的，几年前我遇到了这些错误，直到他们修复了它们.首先尝试服务包.如果那没有帮助，请尝试使用2012版或2017版.也可以想象是Windows更新导致了此问题.它曾经发生过.
Error code 5 is an access violation in Windows. These debugger crashes are usually fixed by upgrading Visual Studio or applying the latest service pack. VS2015 is screwy in lots of ways, since it was a ground up rewrite, and I had these errors a few years ago until they fixed them. Try a service pack first. If that doesn't help, try either version 2012 or 2017. There also conceivably could be a Windows update that broke this. It has happened before.
另请参阅:"vshost32.exe已停止工作"；或致命执行引擎错误"；在Visual Studio中
这篇关于IBM.Data.DB2.iSeries的iSeries的.NET/C#DB2'FatalExecutionEngineError'的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
