1. Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/39571e42-aca7-469d-8c68-aa59c2da4fcc/
This error can occur when IIS is installed after installing .NET Framework 4, or if the 3.0 version of the WCF Http Activation module is installed after installing IIS and .NET Framework 4.
To resolve this problem, you must use the ASP.NET IIS Registration Tool (Aspnet_regiis.exe,) to register the correct version of ASP.NET. This can be accomplished by using the –iru parameters when running aspnet_regiis.exe as follows:
aspnet_regiis.exe -iru
2.Could not find a base address that matches scheme net.tcp for the endpoint with binding MetadataExchangeTcpBinding. Registered base address schemes are [http].
http://talentedmonkeys.wordpress.com/2010/06/21/wcf-in-iis-gotcha-enable-the-right-protocols/- In IIS, right-click your application.
- Select “Manage Application | Advanced Settings…”
- Add “,net.tcp” (leaving off the quotes) to the end of the text in the “Enabled Protocols”
3. "The provided URI scheme 'http' is invalid; expected 'https"
You have <security mode="Transport"> on the binding. This means it uses https. Change the <endpoint address=...> to agree, or change to a non-transport-security http binding.
4.Keyset does not exist WCF +SSL + Username & Password authentication
This happens because the user used to run the application pool needs permission to access certificates. Return in mmc and give to that user needed permission