You have the Windows Communication Foundation (WCF) service installed on a server that is running Microsoft BizTalk Server 2009.
You create a BizTalk Server project in Visual Studio.
You use the BizTalk WCF Service Consuming Wizard to add WCF send adapters to the BizTalk Server project.
You choose a metadata file as the metadata source. Additionally, the name of the WCF Service contains a hyphen (-). For example, you choose a Web Services Description Language (WSDL) file as the metadata source, and the WCF Service name is "Example-Testservice".
When you successfully complete the wizard, you build the BizTalk Server project.
In this scenario, the BizTalk Server project does not build successfully. Additionally, when you check the generated schemas and orchestrations, you notice the following problems:
The hyphen (-) in the WCF service name is converted to an underscore (_) character in the "Type Name" field of the generated schemas. For example, the generated schema is prefixed with "Example_Testservice".
The Multi-Part Message in the generated orchestration references the type by using type names that are prefixed with "Example-Testservice".
"Security" and "session" messages are generated unexpectedly in the orchestration. Additionally, part names in the orchestration are named "Security" and "Session," respectively.
The problem occurs because the BizTalk WCF Service Consuming Wizard incorrectly converts the hyphen when it is used as part of a WCF Service name.
To resolve this problem, apply this hotfix.
More information about this hotfix
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:
2429050 Cumulative update package 1 for BizTalk Server 2009
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 the problem that is 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 to 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:
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.
You must have Microsoft BizTalk Server 2009 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and the 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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base: