Fatal Execution Engine Error

Ever since the Beta II CTP, we have been getting intermitent "Fatal Execution Engine Error"s when an IIS hosted service receives its first request. This seems most common after we modify the service's code and dont issue an iisreset before running the client.

The error is occuring on all of our development machines (XP IIS 5.1) and our development servers (Server 2k3 IIS6).

Has anyone else run into these issues?

If we revert to the February CTP bits, the errors go away. We are currently running the July CTP bits and receiving the following 3 errors within the eventlog:

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Date: 7/21/2006
Time: 8:43:47 AM
User: N/A
Computer: EWELLNITZ-WXP
Description:
.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 7/21/2006
Time: 8:43:47 AM
User: N/A
Computer: EWELLNITZ-WXP
Description:
Faulting application aspnet_wp.exe, version 2.0.50727.42, stamp 4333aece, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? 0, fault address 0x0000c539.

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1000
Date: 7/21/2006
Time: 8:43:57 AM
User: N/A
Computer: EWELLNITZ-WXP
Description:
aspnet_wp.exe (PID: 3380) stopped unexpectedly.

This is the error we receive from the proxy:

Protocol Exception:

The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 872 bytes of the response were: '<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml" >
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1><span style="font-family:Verdana;color: #ff3300">Server Application Unavailable
</span></h1>


<span style="font-family:Verdana;">
The web application you are attempting to access on this web server is currently unavailable.&nbsp; Please hit the "Refresh" button in your web browser to retry your request.
</span>



<b>Administrator Note:
</b> An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.


</body>
</html>
'.

Stack trace:

at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at SolArc.RightAngle.Common.Security.ISecurityService.GetDirectoryItems()
at SolArc.RightAngle.Common.Security.SecurityServiceProxy.GetDirectoryItems() in D:\Projects\RightAngle.NET\SolArc.RightAngle\Common\Security\SecurityServiceProxy.cs:line 355

[5713 byte] By [EricWellnitz] at [2008-1-8]
# 1

you can use this article to debug the process

Troubleshooting ASP.NET using WinDbg and the SOS extension
http://support.microsoft.com/kb/892277/en-us
http://support.microsoft.com/kb/321564

if possible,please create memory dump before crash(before you update your code) and crash dump,if you send the dump files to us,we can analyze,why this app is crashing.

or

if you have repro,please send it to me,i will try to repro here

-Thank you

Madhu

MadhuPonduru-MSFT at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 2

Eric,

I noticed this problem after switching from Beta 2 to RC1. In my case the problem was caused by attempting to throw a FaultException with a fault detail that violated serialization rules and caused an exception to be thrown from serialization.

For example, the following data contract does not allow nulls for the "Message" property:

[DataContract]

public class CustomFaultDetail

{

private string message;

public CustomFaultDetail(string message)

{

this.message = message;

}

[DataMember(IsRequired = true, EmitDefaultValue = false)]

public string Message

{

get { return message; }

set { message = value; }

}

}

If I execute the following code from an operation I can reproduce this problem:

CustomFaultDetail detail = new CustomFaultDetail(null); // sets Message = null

throw new FaultException<CustomFaultDetail>(detail);

I resolved this issue by setting making the properties/elements of my fault details not required (IsRequired=false/minOccurs=0).

HTH.

Cheers,
~Mork

DanMork at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 3
Did this ever get figured out? I have the same problem and the one suggestion to solve it does not apply to my situation.
turczytj at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 4

We are still getting the error on Windows XP and Server 2003 machines, but it does not occur on Vista machines.

I think it may be related to one of the following:

  • We are inheriting all service contracts from a base service contract called IService
  • A few of our service contracts are derived from generic service contracts (i.e. IEntityService<TEntity, TId> : IService). The generic is closed on the service contract that the service implements (i.e. IContactService).
  • The service contracts are defined in a common assembly that is shared by both the client and the server.

Anyone else doing something similar and seeing errors?

EricWellnitz at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 5
I am not inheriting any of my service contracts, so it must be something else.
turczytj at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 6
Anyone know if IIS Debug Diagnostic will help find the cause of Fatal Execution Engine Errors?
EricWellnitz at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 7
I saw somewhere else that the problem may have to do with the client being configured for SOAP 1.1 and the service configured for SOAP 1.2. Does anybody know how to configure the client and services to use one version or the other?
turczytj at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 8
Did everybody give up on this?
turczytj at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 9

I extracted the crash dump as Madhu suggested above. From looking at the call stack it appears it has something to do with unloading the dlls from memory to replace them with the re-compiled ones.

I sent a memory dump to Madhu. I am hoping he will have time to look into it.

EricWellnitz at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 10

I get exactly the same error using Windows Xp with WCF. What happens is that the web app gets unloaded for any reason, ie recompile, change of config etc - and then after the app is loaded again, ASP.NET crashes trying to execute the call to WCF. What's interesting is that although it is always a WCF call where the app blows up, it's not always the first call and it seems a bit random.

I ran the debugger as you suggested but it doesn't really tell me much.

This costs me a lot of dev time and frustration since I do about 30 recompiles a day while I'm developing. Because I was running with a non-interactive user, I thought the problem might be related to the following hotfix: http://support.microsoft.com/Default.aspx?kbid=913384 but I applied it, and changed my app to an interactive user account, but I still have the problem. So I assume that this is more likely a WCF problem.

Thanks, Rob

rob_kent at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 11
Did Madhu ever get back in touch with you?
turczytj at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 12
No, he hasn't yet.
EricWellnitz at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 13

I am doing something similar and i have the same error.

I sent the memory dump too, and i am waiting.

EricB.Delahaye at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...
# 14
if you ever get a reply, please post the results in this thread. Thanks.
turczytj at 2007-10-2 > top of Msdn Tech,Visual Studio Orcas,Windows Communication Foundation (Indigo)...

Visual Studio Orcas

Site Classified