Article ID: 319177 - View products that this article applies to.
This article was previously published under Q319177
This article has been archived. It is offered "as is" and will no longer be updated.
If you set CallContext objects before you create an instance of a serviced component in a client application, you may lose the CallContext objects after you create the object instance.
This problem occurs if the objects that you place in the CallContext derive from the ILogicalThreadAffinative interface. If you place these objects in the CallContext (by using the CallContext.SetData method) and then create an instance of a ServicedComponent object, the CallContext.GetData method for those objects returns null.
To resolve this problem, obtain the latest service pack for Microsoft .NET Framework. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/318836/EN-US/ )INFO: How to Obtain the Latest .NET Framework Service Pack
WORKAROUNDTo work around this problem, use one of the following methods:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft .NET Framework Service Pack 2 (SP2).
With the CallContext object, you can send information along the channel from client to server or vice versa. CallContext provides a set of properties that are carried along with the execution code path (call chain).
This problem also occurs with all headers in the CallContext object.
Steps to Reproduce the Problem
Article ID: 319177 - Last Review: January 17, 2015 - Revision: 3.3