Select the product you need help with

WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1 or in .NET Framework 4

Article ID: 982867 - View products that this article applies to.

SYMPTOMS

Consider the following scenario:

You use Network Load Balancer (NLB) to route messages for a set of computers that host Windows Communication Foundation (WCF) services. These services use secure sessions by setting the authenticationMode attribute to "SecureConversation."
You try to add Webheaders to messages in the application layer. After you do this, the NLB can use the Webheaders to route messages.

In this scenario, you cannot add WebHeaders to messages that are used to negotiate the session. Therefore, the two types of messages are routed to different host computers. In this situation, any cached session data in the host computer is unavailable and the WCF services fail.

Back to the top | Give Feedback

RESOLUTION

.NET Framework 4

To resolve this problem in the .NET Framework 4, install the hotfix that is described in the following Microsoft Knowledge Base (KB) article.

2532942

(http://support.microsoft.com/kb/2532942)

Hotfix rollup package 2532942 is available for Windows Communication Foundation for the .NET Framework 4

.NET Framework 3.5 Service Pack 1 (SP1)

To resolve this problem in the .NET Framework 3.5 SP1, install the hotfix that is described in this article.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. 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.

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB982867

(http://code.msdn.microsoft.com/KB982867)

Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.

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 Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The hotfix does not resolve the problem when you use secure conversation cookie mode.

Prerequisites

You must have the .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply the hotfix if the affected files are not being used.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The 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.