Fatal Execuation Error - any workarounds available? or help debugg

[Guest]

We have a .NET application using Windows Forms. This application terminates
unexpectedly once or twice a day for our customers. The following entry is
listed in the event log:

..NET Runtime version 2.0.50727.832 - Fatal Execution Engine Error (7A0592A2)
(80131506)

This problem appears to have started recently in the past 1 or 2 months. Is
this a known issue, and if so, are there any workarounds?

I am really at a loss as to how to deal with this problem.
How do you suggest I go about debugging or troubleshooting this issue?

 

[Laura T.]

maybe this can help:
http://groups.google.it/group/micro...=it&lnk=st&q=7A0592A2&rnum=3#37c4ab2757ca6a1f

 

[Alvin Bruney [MVP]]

You should post this in the CLR newsgroup. Execution engine errors refer to
the CLR where the CLR team actively monitors this newsgroup.

 

[Guest]

Thanks for your past posts Laura and Alvin -

Laura's suggestion of removing .NET 2.0 security update (KB928365) didn't
help. But it was worth a try.

We solved the problem by adding a timer that garbage collects every second.
This allowed us to reproduce the problem on a somewhat consistent basis.
Then we narrowed down in the code where approximately this problem was
occurring. It was during cleanup of a particular COM object/interface.
Luckily it turned out that we weren't even using the capabilities of this COM
object and didn't have to create the object nor release it. We removed this
from our code and things have been working real well.

--
John Voelk
http://www.datstat.com
Professional online survey/data analysis software products and services

 

[Alvin Bruney [MVP]]

Thanks for the follow up.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless Author Plug
OWC Black Book 2nd Edition
Exclusively on www.lulu.com/owc
$24.99