Select the product you need help with
FIX: A .NET Framework 3.0-based WCF service may crash with a System.ServiceModel.CommunicationException exception if the service uses the netTcpBinding bindingArticle ID: 2600907 - View products that this article applies to. On This PageSYMPTOMSYou run a Microsoft .NET Framework 3.0-based Windows Communication Foundation (WCF) service that uses the netTcpBinding binding. When a transient network error occurs, the service crashes because of a System.ServiceModel.CommunicationException exception. The exception may occur because of time-out or because of an underlying network resource issue. The stack trace may resemble the following example: … at System.ServiceModel.Channels.SecurityChannelListener`1.DuplexSessionReceiveMessageAndVerifySecurityAsyncResult.BeginTryReceiveItem(TimeSpan timeout, AsyncCallback callback, Object state) at System.ServiceModel.Channels.SecurityChannelListener`1.ReceiveItemAndVerifySecurityAsyncResult`2.StartInnerReceive() at System.ServiceModel.Channels.SecurityChannelListener`1.ReceiveItemAndVerifySecurityAsyncResult`2.Start() at System.ServiceModel.Channels.SecurityChannelListener`1.DuplexSessionReceiveMessageAndVerifySecurityAsyncResult.ReceiveMessage(Object state) at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.WorkItem.Invoke2() at System.Security.SecurityContext.Run(SecurityContext securityContext, ContextCallback callback, Object state) at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.WorkItem.Invoke() at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.ProcessCallbacks() at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.CompletionCallback(Object state) CAUSEThis issue occurs because the ReceiveMessage method in the DuplexSessionReceiveMessageAndVerifySecurityAsyncResult object does not catch exceptions that are caused by the error, and they are transferred to the user thread. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must have the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed on one of the following Windows operating systems to apply this hotfix:
935791
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935791/
)
How to obtain the latest Windows Vista service pack968849
For more information about how to obtain Service Pack 1 for Windows 7 or for Windows Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/968849/
)
How to obtain the latest service pack for Windows Server 2008976932
(http://support.microsoft.com/kb/976932/
)
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2Restart informationYou may have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you exit all .NET Framework applications before you apply this hotfix to avoid having to restart the computer.Replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.For all supported x86-based versions of Windows Vista SP2 and of Windows Server 2008 SP2Collapse this table
For all supported x64-based versions of Windows Vista SP2 and of Windows Server 2008 SP2Collapse this table
For all supported IA-64-based versions of Windows Server 2008 SP2Collapse this table
For all supported x86-based versions of Windows 7 SP1Collapse this table
For all supported x64-based versions of Windows 7 SP1 and Windows Server 2008 R2 SP1Collapse this table
For all supported IA-64-based versions of Windows Server 2008 R2 SP1Collapse this table
MORE INFORMATIONFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 2600907 - Last Review: September 7, 2011 - Revision: 1.0
| Article Translations
|



Back to the top








