FIX: The client's credentials are not used when an orchestration calls a second WCF service, and event ID 5754 is logged in BizTalk Server 2006 R2

Consider the following scenario. A client calls a Windows Communication Foundation (WCF) service. The WCF service is an orchestration that is published as a WCF service that uses a Request-Response receive port. This orchestration calls a second WCF service. When the second WCF service is called, the client�s credentials are not used. When this problem occurs, an event error that resembles the following is logged in the Application event log:

Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5754
Description:
A message sent to adapter "Adapter_Name" on send port "Send_Port_Name" with URI "URI" is suspended.
Error details:
System.ApplicationException: The context property http://schemas.microsoft.com/BizTalk/2003/system-properties#WindowsUser is not contained in the message context

Note This problem may also occur if you use Windows message security with a WCF receive location.

This problem occurs because the WCF adapter does not correctly promote the OriginatorSID context property. Therefore, the second WCF service call uses the orchestration host instance account instead of the original client credentials.

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.

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

After the hotfix is installed, the WCF adapter correctly promotes the OriginatorSID context property of the original callers.

Note In an expression shape, you can obtain the client credentials by using the Microsoft.BizTalk.XLANGs.BTXEngine.OriginatorSID context property of the received message.

For more information about WCF adapters, visit the following Microsoft Web site: For more information about BizTalk Server message context properties, visit the following Microsoft Web site: For more information about the SystemMessageContext.WindowsUser property, visit the following Microsoft Web site: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: