0
Answered

Hosting on Cassini does not start with multiple endpoints

Matthew Clark 7 years ago • updated by anonymous 4 years ago 2

The Identity Broker service does not currently start due to the following error:

Service cannot be started. Unify.Framework.UnifyServiceStartException: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. If your service is being hosted in IIS you can fix the problem by setting 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' to true or specifying 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'.
Parameter name: item ---> System.ArgumentException: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. If your service is being hosted in IIS you can fix the problem by setting 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' to true or specifying 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'.
Parameter name: item
at System.ServiceModel.UriSchemeKeyedCollection.InsertItem(Int32 index, Uri item)
at System.Collections.Generic.SynchronizedCollection`1.Add(T item)...

Currently investigating possible solutions. Attempts to modify the web.config file as described in http://stackoverflow.com/questions/561823/wcf-error-this-collection-already-contains-an-address-with-scheme-http (and many other related sources) have not been successful, namely, adding

<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />

to the system.serviceModel element, and adding a baseAddressPrefix, also result in the above error.

Affected Versions:
Fixed by Version:

Adam noted that the app.config file was not consistent for the InterLINQ interface. Copying the updated app.config file from the service resolved this issue, although it is not directly clear why this error message was thrown. Issue resolved.