Article ID: 2740200 - View products that this article applies to.
Consider the following scenario. You have a Windows Communication Foundation (WCF) service using Microsoft .NET Framework 4.0, hosted in a Microsoft Internet Information Services (IIS) web server. Under the SSL settings for the web application, you have enabled "Require SSL" as well as requiring client certificates. You then apply one of or more of the following hotfixes for WCF on .NET Framework 4:
A hotfix rollup package is available for WCF in the .NET Framework 3.0 SP2, in the .NET Framework 3.5 SP1 and in the .NET Framework 4
Multiple issues that are fixed in .NET Framework 4.0-based WCF services
FIX: .NET Framework 4-based WCF service may crash when many client web applications access the service if the TCP protocol is used
FIX: Assembly binding redirection does not work for a WCF behavior extension in a .NET Framework 3.5-based or .NET Framework 4-based WCF service
Update 4.0.3 for Microsoft .NET Framework 4 – Runtime Update
SecurityNegotiationException exception when a .NET Framework 4-based WCF client connects to a WCF service through a proxy server
FIX: Slow performance when many large requests are received by a .NET Framework 4-based WCF service
Hotfix rollup package 2532942 is available for Windows Communication Foundation for the .NET Framework 4
In this configuration, when you try to browse to or make a method call to the WCF service that is using client certificate authentication, you may receive an error message and stack trace similar to the one below. You may receive this error even if you have not changed any other setting in the WCF configuration or IIS SSL configuration:
This issue occurs due to a mismatch in the versions of System.ServiceModel.Activation.dll and System.ServiceModel.dll.
To resolve this problem, install the Microsoft hotfix 2537715
(http://support.microsoft.com/kb/2537715)after installing any of the hotfixes mentioned in the above list.
If you already have the Microsoft hotfix 2537715
(http://support.microsoft.com/kb/2537715)installed, and then you install one of the hotfixes mentioned above in the Symptoms section, then the Activation Exception issue described in this article does not occur.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.