Application crashes with error code 0xe0434f4d on exit

A

ankan.banerjee

Hi all,

We have a .NET Server DLL which is hosted as a COM+ application. The
server is invoked by another .NET Client DLL which resides on the
local machine and is invoked by a MFC application. On exit of this MFC
app, we get a crash with the
error code 0xe0434f4d.

Surprisingly, this error only happens in the local system is
using .NET Framework 2.0. With the
..NET Framework 1.1, this error did not occur. Even worse, if the MFC
application is compiled in Debug mode, then the crash does not happen
in .NET Framework 2.0 also! So only our release build has this
problem.

Have any of you faced similar issues before? I could find a lot of
links with my search on the error code but none of them
seemed to be valid for our context, but the issue seems to be related
to .NET.

Any help/hints would be appreciated. Thanks in advance!

Ankan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Running C# (.NET Framework 2.0) Application from long path (>127)crashes! 1
.NET application deployment questions 0
Error "The type initializer for ... threw an exception" 2
Deploying application got error 3
System policy prevents loading manifests and installing .NET SDK 2.0 with Vista 1
Creating application pool for ASP.NET 1.1 in IIS7 running on x64 V 3
Will it run on .NET 1.1? 5
All .NET programs startup with an error 2

Top