Hello
I have developed a windows service. A few days ago we noticed it just
stops functioning.
I installed the .net 3.5 SP1 which should include all the patches up
to now.
There was no change. Once in a while, without any apparant reason or
pattern, the application just stops working.
The eventlog shows:
Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Date: 09/09/2008
Time: 12:19:51
User: N/A
Computer: ROTEMS-LAP-HZ
Description:
..NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error
(7A097706) (80131506)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

We are going live in a few days, and up until 2 days ago everything
worked fine.
Rotem

hmm, that's a nasty error. Cut the code down to just bare bones and load it
into a separate windows service running on the same box and see if produces
the same error. If it does, that's a microsoft issue to fix. You can also
run it under the debugger and set the debugger to break on a first chance
exception. That may locate the line of code that may be responsible for the
error. However, since nothing changed on the box, it may be SP1 related.

Sorry I have same problem . Have You resoltion for this ?

Alvin Bruney [ASP.NET MVP] wrote:
[..]

I am not sure if this helps but I had a similar experience today. I was
working in Visual Studio 2008 SP1 with a solution. I also had another
instance of VS2008 SP1 open with a larger solution. I closed the first Visual
Studio instance and then closed the second one. When I open VS again and then
tried to load first solution, VS starts to do it then *POOF* VS completely
disappears. I found an entry in the Event Log ".NET Runtime version
2.0.50727.3053 - Fatal Execution Engine Error (6A445E00) (80131506)" which
let me to find this series of posts abandoned. I ended up deleteing all the
files (or at least the ones that were not locked) in the following folders.

C:\Users\<YourUserName>\AppData\Local\Temp\
C:\Windows\Temp\
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temp orary ASP.NET Files\

The problem appears to have gone away and I can now load my solution again.
Pretty wacky stuff.


"Marek" wrote:
[..]

I encountered this problem couple of days ago and I did a system restore to
resolve the issue :)..i know that is the right way of fixing the issue, but i
could not find any other way to sort out the issue.

You can read more about the solution i adopted over her
http://www.techdreams.org/microsoft/...t/370-20080926

Hope this helps you.

"Rotem" wrote:
[..]