Article ID: 959136 - View products that this article applies to.
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
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 informationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesYou must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix 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.
Collapse this tableExpand this table
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:
http://msdn.microsoft.com/en-us/library/bb259952.aspxFor more information about BizTalk Server message context properties, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/aa577668.aspxFor more information about the SystemMessageContext.WindowsUser property, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/microsoft.biztalk.message.interop.systemmessagecontext.windowsuser.aspxFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 959136 - Last Review: March 24, 2009 - Revision: 1.1
Contact us for more help
Connect with Answer Desk for expert help.