Exchange 2013 - Duplicate Binding for EWS

Question

Hi there,
on our Exchange 2013 server we find that Outlook and OWA are both working fine. Mac users can't connect. This seems to be related to the following error [sorry for the Dutch language]:
Basically it complains that an endpoint is already bound to the URI.
WebHost failed to process a request.
 Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/34026242
 Exception: System.ServiceModel.ServiceActivationException: De service /EWS/exchange.asmx kan niet worden geactiveerd als gevolg van een uitzondering tijdens de compilatie. Het uitzonderingsbericht is: Er is reeds een bindingsexemplaar gekoppeld aan luister-URI
https://bilbo.ourdomain.loc:444/EWS/Exchange.asmx/http. Als twee eindpunten dezelfde LuisterURI willen delen, moeten ze ook hetzelfde bindingsobjectexemplaar delen. De twee conflicterende eindpunten zijn opgegeven in AddServiceEndpoint()-aanroepen, in een
configuratiebestand, of in een combinatie van AddServiceEndpoint() en configuratiebestand. . ---> System.InvalidOperationException: Er is reeds een bindingsexemplaar gekoppeld aan luister-URI https://bilbo.ourdomain.loc:444/EWS/Exchange.asmx/http. Als twee
eindpunten dezelfde LuisterURI willen delen, moeten ze ook hetzelfde bindingsobjectexemplaar delen. De twee conflicterende eindpunten zijn opgegeven in AddServiceEndpoint()-aanroepen, in een configuratiebestand, of in een combinatie van AddServiceEndpoint()
en configuratiebestand. 
   bij System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   bij System.ServiceModel.ServiceHostBase.InitializeRuntime()
   bij System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   bij System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   bij System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
   bij System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   --- Einde van intern uitzonderingsstackpad ---
   bij System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   bij System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
 Process Name: w3wp
 Process ID: 8320
The IIS Manager has two sites ('Default Web Site', 'Exchange Back End').
For the Default Site only the bindings *:80, *:443, 127.0.0.1:80, 127.0.0.1:443 are enabled.
For the Exchange Back End only the bindings *:81, *:444 are enabled
There are no other sites. 
I have tried searching the config files by doing:
PS C:\inetpub> Get-ChildItem . -include *.config -rec | select-string -pattern "444"
This does give files under C:\inetpub\history and C:\inetpub\temp but I don't know [given the history/temp] names if I should look further here.
I have also looked at
PS C:\windows\system32\inetsrv> Get-ChildItem . -include *.config -rec | select-string -pattern "444"
This returns only a single line in config\applicationHost.config which matches what I see in the IIS Manager GUI.
Where else can I search to find the duplicate binding?
Eljakim

Answer 1

Okay, after a couple of nights of trouble shooting I found the solution.
In the web.config file under Exchange\ClientAccess\exchweb\ews somehow the following information had appeared:
<services>
<service name="Microsoft.Exchange.Services.Wcf.EWSService" behaviorConfiguration="EWSServiceBehavior">
<!-- For streamed transfer mode, we need a different endpoint address with /s/. -->
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpsBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpsBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" />
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="http" />
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="http" />
</service>
<service name="Microsoft.Exchange.UM.ClientAccess.UMWebService" behaviorConfiguration="UMServiceBehavior">
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract" />
<endpoint address="http" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract" />
</service>
</services>
The endpoint addresses are wrong in this file. I compared the endpoints to a config on another server and fixed the issue by changing the services to:
<services>
<service name="Microsoft.Exchange.Services.Wcf.EWSService" behaviorConfiguration="EWSServiceBehavior">
<!-- For streamed transfer mode, we need a different endpoint address with /s/. -->
<endpoint address="s" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpsBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract"/>
<endpoint address="s" behaviorConfiguration="MultiReceive" binding="webHttpBinding" bindingConfiguration="EWSStreamingNegotiateHttpBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSStreamingContract"/>
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpsBinding" name="Https" contract="Microsoft.Exchange.Services.Wcf.IEWSContract"/>
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="EWSAnonymousHttpBinding" name="Http" contract="Microsoft.Exchange.Services.Wcf.IEWSContract"/>
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="wssecurity"/>
<endpoint binding="customBinding" bindingConfiguration="EWSWSSecurityHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IEWSContract" address="wssecurity"/>
</service>
<service name="Microsoft.Exchange.UM.ClientAccess.UMWebService" behaviorConfiguration="UMServiceBehavior">
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpsBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract"/>
<endpoint address="" behaviorConfiguration="MultiReceive" binding="customBinding" bindingConfiguration="UMLegacyHttpBinding" contract="Microsoft.Exchange.Services.Wcf.IUM12LegacyContract"/>
</service>
</services>