SYMPTOMS
When you use Microsoft .NET Framework remoting in Microsoft Visual Studio .NET, you may receive an "Unhandled Execution" error message. The error message text indicates that the handle is not valid.
The following is an example of a fusion log that may appear when this error occurs:
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.GetCurrentSidString()
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.SetupWebRequest(IMessage msg, ITransportHeaders headers)
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream)
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
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 Willis.Business.Placement.PlacingFileApplicationManager.W_NET_PlacingFile_AS.PlacingFileApplicationManager.SavePlacingFile(PlacingFile pPlacingFile, Boolean pKeepLock)
at PlacingFileComplete.PF_Create.PlacingFileCreate()
at PlacingFileComplete.PF_Create.btnCreateUpdate_Click(Object sender, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain()
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 1.0 Service Pack 3 that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
------------------------------------------------------------------------
10-Sep-2003 23:53 1.0.3705.457 200,704 Aspnet_isapi.dll
11-Sep-2003 20:00 1.0.3705.457 1,953,792 Mscorlib.dll
10-Sep-2003 23:06 1.0.3705.457 2,273,280 Mscorsvr.dll
10-Sep-2003 23:07 1.0.3705.457 2,269,184 Mscorwks.dll
10-Sep-2003 23:50 1.0.3705.457 20,480 Perfcounter.dll
11-Sep-2003 19:59 1.0.3705.457 1,175,552 System.dll
11-Sep-2003 19:58 1.0.3705.457 311,296 System.runtime.remoting.dll
11-Sep-2003 20:00 1.0.3705.457 1,196,032 System.web.dll
11-Sep-2003 19:58 1.0.3705.457 507,904 System.web.services.dll
11-Sep-2003 20:00 1.0.3705.457 1,302,528 System.xml.dll