Broken OWA, ECP etc after Remote Desktop Services removal :(

HI 


Check your bindings in  Default Web Site configuration
Remove the extra bindings if you see anything
Check if OWA is bound to the correct ports 

August 5th, 2015 4:27am

Thanks Sathish.

Done this already :(

Wondering if some could just post default settings.

Free Windows Admin Tool Kit Click here and download it now
August 5th, 2015 4:30am

Here you go 

Authentication depends upon your config (ssl offload, basic , NTLM etc...)

If its not working recreate the VD and see the results.

August 5th, 2015 6:20am

Hi All,

Just wondering if someone can help with owa, ecp binging and authorization details. My server was working perfectly and i installed remote desktop services on the same server and had to remove the role.

Once i did that OWA and ECP would not longer function, had a lot of searching however no real solution for the problem. Event logs are simililar for every service and here is one of them, had also removed and recreated the virtual directories, nothing worked, however outlook is working fine.

WebHost failed to process a request.
 Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/56356607
 Exception: System.ServiceModel.ServiceActivationException: The service '/EWS/exchange.asmx' cannot be activated due to an exception during compilation.  The exception message is: This collection already contains an address with scheme https.  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 https.  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)
   at System.ServiceModel.UriSchemeKeyedCollection..ctor(Uri[] addresses)
   at System.ServiceModel.ServiceHost..ctor(Type serviceType, Uri[] baseAddresses)
   at Microsoft.Exchange.Services.Wcf.EWSServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
 Process Name: w3wp
 Process ID: 27868

Free Windows Admin Tool Kit Click here and download it now
August 5th, 2015 7:27am

Nop This didn't help either, wondering what the problem is.
August 6th, 2015 11:45pm

This has now been resolved. I thought i would write for anyone that might face the same issue.

In my case the exchange backend  had a 443 binding, that was causing the issue. Removed that and  restarted iis, fixed straight away.

Raza

  • Marked as answer by Razakhan 1 hour 46 minutes ago
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2015 1:40am

This has now been resolved. I thought i would write for anyone that might face the same issue.

In my case the exchange backend  had a 443 binding, that was causing the issue. Removed that and  restarted iis, fixed straight away.

Raza

  • Marked as answer by Razakhan Friday, August 07, 2015 5:43 AM
August 7th, 2015 5:38am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics