Solved

Exchange Server Autodiscover problem

Posted on 2013-01-17
3
915 Views
Last Modified: 2013-02-07
Hi folks, the autodiscover service on our exchange server 2010 on SBS2011 has not been working since exchange crashed during a migration from sbs2003 because of a fast finger adsiedit I did on the source server to uninstall exchange after the migration. Microsoft had to come in and help reinstall exchange. But since then autodiscover never worked right and remote users have their outlook anywhere settings reset to blank at times or today autodiscover.domain instead of remote.domain. We reset it back to remote.domain on their systems and they connect fine again.
But today exchange went down and i noticed the information store service was stopped. I started it and exchange is working again for the users.
In event viewer we were getting a few of the following error but today it is every 30 seconds
Event ID 3
WebHost failed to process a request.
 Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/32001227
 Exception: System.ServiceModel.ServiceActivationException: The service '/Autodiscover/autodiscover.xml' cannot be activated due to an exception during compilation.  The exception message is: Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service.. ---> System.NotSupportedException: Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service.
   at System.ServiceModel.Channels.HttpChannelListener.ApplyHostedContext(VirtualPathExtension virtualPathExtension, Boolean isMetadataListener)
   at System.ServiceModel.Channels.HttpsChannelListener.ApplyHostedContext(VirtualPathExtension virtualPathExtension, Boolean isMetadataListener)
   at System.ServiceModel.Channels.HttpsTransportBindingElement.BuildChannelListener[TChannel](BindingContext context)
   at System.ServiceModel.Channels.BindingContext.BuildInnerChannelListener[TChannel]()
   at System.ServiceModel.Channels.BindingElement.BuildChannelListener[TChannel](BindingContext context)
   at Microsoft.Exchange.Autodiscover.WCF.LegacyMessageEncoderBindingElement.BuildChannelListener[TChannel](BindingContext context)
   at System.ServiceModel.Channels.BindingContext.BuildInnerChannelListener[TChannel]()
   at System.ServiceModel.Channels.Binding.BuildChannelListener[TChannel](Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, BindingParameterCollection parameters)
   at System.ServiceModel.Description.DispatcherBuilder.MaybeCreateListener(Boolean actuallyCreate, Type[] supportedChannels, Binding binding, BindingParameterCollection parameters, Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, ServiceThrottle throttle, IChannelListener& result, Boolean supportContextSession)
   at System.ServiceModel.Description.DispatcherBuilder.BuildChannelListener(StuffPerListenUriInfo stuff, ServiceHostBase serviceHost, Uri listenUri, ListenUriMode listenUriMode, Boolean supportContextSession, IChannelListener& result)
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
 Process Name: w3wp
 Process ID: 11212

We were working on repairing autodiscover last night -- I dont know exactly what the engineer did to repair it through the exchange powershell console. But that broke all the remote users on Outlook anywhere and the engineer somehow reversed what he did and they are back.
We enabled Windows authentication in the RPC virtual directory in IIS because we noticed it was disabled last night also. Cant see this causing a problem. Any suggestions on what I should do next? I think there might be a problem with autodiscover.xml but it tests successfully in Exchangetestconnectivity.com except that RPC failed a test which I am looking into. Thank you.
0
Comment
Question by:electricdad
  • 2
3 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38788844
First - check that you don't have the Windows Management Framework 3.0 installed.
http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx

Do you have Exchange 2010 SP2 installed? If not, install it.
If you do, then use the tool in the management console to reset the virtual directories.

For Outlook Anywhere you may have to reinstall it. Disable the RPC Proxy and virtual directories removed (in that order) and run IISRESET to get the change written to the IIS metabase. Check for the event log entry to confirm it has been disabled. Then reinstall the RPC Proxy and enable Outlook Anywhere again.

Simon.
0
 

Accepted Solution

by:
electricdad earned 0 total points
ID: 38846708
Well, it was an issue with the Autodiscover virtual directory which showed Windows Authentication as disabled. It should be enabled. If you try to enable it there, it will return to disable after an IISreset. You have to use the exhcange powershell command--
Set-AutodiscoverVirtualDirectory -Identity 'autodiscover (default Web Site)' -WindowsAuthentication $true
This worked and windows authentication is working and autodiscover works. All set. Thanks for the reply.
0
 

Author Closing Comment

by:electricdad
ID: 38863265
It worked using the powershell command
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Junk folder 23 109
Exchange 2013 -Load Balancing 5 34
Import Cert issue 15 41
Daily Outlook Calendar Meeting Reminder 5 29
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now