I have several services that need to be run on the same website. Two services have a net.tcp endpoint. Addresses are formatted as follows:
net.tcp: //backend.ourcompany.com: 9080 / Product1 / 2010/09 / Service1 / Service1.svc
net.tcp: //backend.ourcompany.com: 9081 / Product1 / 2010/09 / Service2 / Service2.svc
net.tcp: //backend.ourcompany.com: 9090 / Product2 / 2010/09 / Service2 / Service2.svc
All services have their own Web.config. Currently, all services have a different base address in their Web.config and relative endpoint address. Everything worked fine, only with the installation of the fist, after installing the second I continue to get this error: "This collection already contains the address with the net.tcp scheme. This collection can have no more than one address according to the scheme. If your service is hosted in IIS, you can fix this problem by setting "system.serviceModel / serviceHostingEnvironment / multipleSiteBindingsEnabled" to true or by specifying "system.serviceModel / serviceHostingEnvironment / baseAddressPrefixFilters".
Since multipleSiteBindingsEnabled is for http only (why?), I tried to get it to work with baseAddressPrefixFilters, but I really don't understand how this will help me in my case. Is it possible that I'm trying to do here? Otherwise, it will be a big failure of IIS, in a self-service environment I have been doing the same for many years. Now I want to migrate my existing services to IIS due to AppFabric monitoring features.
source
share