Google Mail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Runtime version 2.0.50727.1433 - Fatal Execution Engine "
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
ashu2409 via DotNetMonster.com  
View profile   Translate to Translated (View Original)
 More options 6 Oct, 08:42
Newsgroups: microsoft.public.dotnet.framework.clr
From: "ashu2409 via DotNetMonster.com" <u54936@uwe>
Date: Tue, 06 Oct 2009 07:42:03 GMT
Local: Tues 6 Oct 2009 08:42
Subject: Runtime version 2.0.50727.1433 - Fatal Execution Engine "
hi,

i have a window service in C# ,which is supposed to run 24x7,when i run it,
it runs fine for some time (may be some time 15 hours or 1 day), but after
that it hanged out. it does'nt do anything. it does not show any exception,
but i found this in event log,

1. .NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error
(79FFEE24) (80131506)
2.Windows cannot query for the list of Group Policy objects. A message that
describes the reason for this was previously logged by the policy engine.

i dont know whether these two exception related to each other or not.

i am using multithreading for xml crawling in this service.
this service is in .net framework 3.5 but error is showing framework 2.0
i have checked with debugger in vs2008 but did not find anything.
is this something related to memory management or deadlock,

Please suggest any solution for this.

--
Message posted via DotNetMonster.com
http://www.dotnetmonster.com/Uwe/Forums.aspx/dotnet-clr/200910/1


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Rich Lander [MSFT]  
View profile   Translate to Translated (View Original)
 More options 7 Oct, 14:05
Newsgroups: microsoft.public.dotnet.framework.clr
From: "Rich Lander [MSFT]" <r...@lander.ca>
Date: Wed, 7 Oct 2009 06:05:23 -0700 (PDT)
Local: Wed 7 Oct 2009 14:05
Subject: Re: Runtime version 2.0.50727.1433 - Fatal Execution Engine "
Could you run your service with windbg attached? You would also need
to get the symbols for .NET too, which should happen automatically (I
believe) if you hook up the symbol server correctly. When your app
crashes, you should get a stack trace, which would be useful in
diagnosing the problem. At present, there isn't really enough
information to know what yo do.

thanks -- rich


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google