04-16-2013 01:26 AM
Dear's,
I have 2 different EV sites and I have been going through IIS setting on EV server and found that in Default Web Site under Bindings I have the below also included
net.tcp
net.pipe
net.msmq
msmq.formatname
Whereas on the other EV sites in IIS setting on EV server have none of the above in bindings for Default Web Site.
Since both the EV sites are working fine without any issue I would like to know what is the use of having net.tcp, net.pipe,net.msmq and msmq.formatname
under bindings, can this be removed to make the IIS settings similar on both the sites.
Solved! Go to Solution.
04-17-2013 08:41 AM
You will get these bindings if when you install .NET 3.5.1 Feature you elect to include 'Non-HTTP Activation' under the WCF Activation option. EV environments have no requirement for this particular sub-option as long as the 'HTTP Activation' is enabled. The 'HTTP Activation' option is necessary as part of the Windows Process Activation Service and Net.Tcp Port Sharing Service.
If you are using CA/DA in your environment then you may have installed this as well. Either way .Net 3.5 SP1 is required for EV9 regardless.
You should be able to remove the installed option and/or the additional bindings without any repurcussion from an EV perspective.
04-16-2013 01:58 AM
I have these bindings in place in my lab server, they are required for WCF service.
04-16-2013 02:02 AM
I believe you have IIS 7.0 or higher and EV 10, where EV Indexing service is implemented as a windows service build on WCF (Windows Communications Foundation Services)
04-16-2013 02:24 AM
I have IIS 7.0 and EV 9.0.3
but my confusion is that on other site we don't have any such settings in IIS but still no issue faced on any site.
Can you please explain me in details about the use of those bindings .
Do we need to keep the those bindings as best practice for EV ?
04-16-2013 04:48 AM
04-17-2013 07:13 AM
Hi,
But I am still on EV 9 .
04-17-2013 07:23 AM
04-17-2013 08:41 AM
You will get these bindings if when you install .NET 3.5.1 Feature you elect to include 'Non-HTTP Activation' under the WCF Activation option. EV environments have no requirement for this particular sub-option as long as the 'HTTP Activation' is enabled. The 'HTTP Activation' option is necessary as part of the Windows Process Activation Service and Net.Tcp Port Sharing Service.
If you are using CA/DA in your environment then you may have installed this as well. Either way .Net 3.5 SP1 is required for EV9 regardless.
You should be able to remove the installed option and/or the additional bindings without any repurcussion from an EV perspective.
04-17-2013 10:41 AM
Hi,
Thanks for this explanation, it's all clear for me .