Common WCF Errors and Solutions - 4

Problem :
Unable to load DLL 'mqrt.dll'
Solution :
If you decide to use msmq binding with WCF. But you are in trouble with the problem written above. The problem is that you forgot to install msmq which is an optional component.

The only thing you should do is to install Message Queuing components.

Common WCF Errors and Solutions - 3

Problem:
Cannot load the X.509 certificate identity specified in the configuration
Solution :
I assume that you have either Windows 7 or Windows Server 2008 operation system with IIS 7+ in order to host WCF services, suddenly you encounter the problem. Luckily, i have a solution for you.

To resolve this problem you should add dns element into web.config file which is placed in your service folder. Please check this sample settings excerpted from a web.config.

<endpoint address="ws" binding="wsHttpBinding" contract="EvalServiceLibrary.IEvalService"
listenUriMode="Explicit">
<identity>
<dns value="localhost" />
<certificateReference storeName="My" storeLocation="LocalMachine"
x509FindType="FindBySubjectDistinguishedName" />
</identity>
</endpoint>

Common WCF Errors and Solutions - 2

Problem:
Could Not Load Type ‘System.ServiceModel.Activation.HttpModule’
Solution :
I assume that you have either Windows 7 or Windows Server 2008 operation system with IIS 7+ in order to host WCF services, suddenly you encounter the problem. Luckily, i have a solution for you.

In order to resolve this problem you should use aspnet_regiis.exe called ASP.NET IIS Registration Tool which is placed in C:\Windows\Microsoft.NET\Framework\v4.0.30319. This path can be diverse due to your .NET Framework or operating system installation.

• Open Command Prompt
• Find C:\Windows\Microsoft.NET\Framework\v4.0.30319 path
• Run aspnet_regiis.exe -iru 

It's accomplished. Now, it's the time to see the result.

Common WCF Errors and Solutions - 1

Problem :
The protocol 'net.tcp' is not supported.
Solution :
If you try to expose your service from IIS 5/6, i have to say it's not possible. There is nothing to do to overcome with IIS 5/6. You have to use IIS 7+.
Although you see the error in WCF service run by IIS 7+, you have to install these following components :

• Windows Process Activation Service
• Process Model
• .NET Environment
• Configuration APIs

• .NET Framework 3.0 Features
• .NET Framework 3.0
• WCF Activation

After installing these components written above, the next step is to make net.tcp enabled. The Default Web Site on your IIS must be bound to a net.tcp port. In this step, you have to modify applicationHost.config file  which is in C:\Windows\System32\inetsrv\config\ by using appcmd.exe in C:\Windows\System32\inetsrv\ 

I highly recommend to backup your applicationHost.config file. Before pass to the next step.

Open the command prompt and go to C:\Windows\System32\inetsrv\config\ path and run the following 4 commands : 

appcmd.exe set site "Default Web Site" -+bindings.[protocol='net.tcp', bindingInformation='808:*']

appcmd.exe set site "Default Web Site" -+bindings.[protocol='net.pipe', bindingInformation='*']

appcmd.exe set site "Default Web Site" -+bindings.[protocol='net.msmq', bindingInformation='localhost']

appcmd.exe set app "Default Web Site/< your wcf application >" /enabledProtocols:http,net.pipe,net.tcp,net.msmq

Finally, the problem has been solved.

JSON Validator

Certainly, internet has lots of source for people who is involved in software development. I came across nice tool to validate JSON. I'm surprised how i couldn't see it. Here is the link i mentioned.

http://www.jsonlint.com/