FIX: Binding configurations for some binding types are not saved in the WCF-Custom adapter or in the WCF-CustomIsolated adapter in BizTalk Server Administration Console

Consider the following scenario in Microsoft BizTalk Server:

• You configure a receive location or a send port to use the "WCF-Custom" transport type or the "WCF-CustomIsolated" transport type in BizTalk Server Administration Console.
• In Binding configuration, you change one of the following binding types:
  • mexHttpBinding
  • mexHttpsBinding
  • mexNamedPipeBinding
  • mexTcpBinding
  • ws2007FederationHttpBinding
  • ws2007HttpBinding

In this scenario, the change that you made for the binding types are not saved in the Transport Properties window. Additionally, if you reopen the Transport Properties window, the binding configuration for the binding type that you tried to change is reset to the original value.

Note The WCF-CustomIsolated adapter is used for a receive location that is running in an isolated host. The WCF-Custom adapter is used for both receive locations and send ports to connect to Windows Communication Foundation (WCF) services. For more information about how to configure these adapters, see the More Information section.

Cumulative updated information

For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

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.

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, submit a request to 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 Web site: 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.

Prerequisites

You must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about Configuring the WCF-Custom adapter, visit the following Microsoft MSDN Web site:
http://msdn.microsoft.com/en-us/library/bb226520.aspx
For more information about Configuring the WCF-CustomIsolated adapter, visit the following Microsoft MSDN Web site:
http://msdn.microsoft.com/en-us/library/bb246042.aspx
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684� �Description of the standard terminology that is used to describe Microsoft software updates