As we all know that IIS 6 supports HTTP protocol only.
Windows Process Activation Service (WAS) supports non-http protocols in IIS. So, WAS helps WCF service to host with HTTP and NO-HTTP protocols such as net.tcp.
Windows Process Activation Service (WAS) supports non-http protocols in IIS. So, WAS helps WCF service to host with HTTP and NO-HTTP protocols such as net.tcp.
Once you changed binding in the config file to netTcpBinding
Your service will throw this error.
Don’t worry there is an easy solution for that.
Go to IIS (run->inetmgr) and right click on a website in IIS. Manage Website->Advance Settings. You may notice available protocols. IIS by default supports HTTP protocol only.
To activate Non-HTTP go to control panel then click on Turn Windows features on or off.
And then you may add other protocols as well in IIS.
Once you made all these changes your service should run with netTcpBinding.
Related blogs to WCF Service-
- Introduction to WCF
- ABC of WCF
- Basics of WCF Architecture
- WCF vs Web Service
- What is XML serialization?
- WCF Binding
- Create first WCF application
- Fault Contract in
- WCF Data Contract vs Message Contract
- Message Contract
- Data Contract Serialization and De-Serialization
- Data Contract in WCF
- Operation Contract in WCF
- Service Contract in WCF
- How to host a WCF service in IIS?
- WAS Hosting in WCF
- Self Hosting in WCF
- How to create WCF RESTful Service.
