 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / October 2007Fatal Execuation Error - any workarounds available? or help debugg
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? maybe this can help: http://groups.google.it/group/microsoft.public.windowsupdate/browse_thread/threa d/8e953b80e6dbd8b7/37c4ab2757ca6a1f?hl=it&lnk=st&q=7A0592A2&rnum=3#37c4ab2757ca6 a1f > We have a .NET application using Windows Forms. This application > terminates [quoted text clipped - 12 lines] > 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? You should post this in the CLR newsgroup. Execution engine errors refer to the CLR where the CLR team actively monitors this newsgroup.  SignatureRegards, Alvin Bruney ------------------------------------------------------ Shameless Author Plug OWC Black Book 2nd Edition Exclusively on www.lulu.com/owc $24.99 > maybe this can help: > http://groups.google.it/group/microsoft.public.windowsupdate/browse_thread/threa d/8e953b80e6dbd8b7/37c4ab2757ca6a1f?hl=it&lnk=st&q=7A0592A2&rnum=3#37c4ab2757ca6 a1f [quoted text clipped - 15 lines] >> 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? 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. SignatureJohn Voelk http://www.datstat.com Professional online survey/data analysis software products and services > You should post this in the CLR newsgroup. Execution engine errors refer to > the CLR where the CLR team actively monitors this newsgroup. [quoted text clipped - 18 lines] > >> 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? Thanks for the follow up. SignatureRegards, Alvin Bruney ------------------------------------------------------ Shameless Author Plug OWC Black Book 2nd Edition Exclusively on www.lulu.com/owc $24.99 > Thanks for your past posts Laura and Alvin - > [quoted text clipped - 37 lines] >> >> 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? Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.