Outlook Anywhere stopped working after I finished my Exchange 2010 migration. All of my IIS permissions are correct, Outlook Web Access works fine and my SAN unified communcation certificate is up to date, but Outlook Anywhere just hangs and won't connect. Help!
The Outlook Anywhere feature can be a tricky customer. I see you've already checked a number of areas -- that's good. If Outlook Anywhere isn't working after your Exchange 2010 migration, I suggest setting up a good old-fashioned RPC/HTTP connection.
If Outlook Anywhere continues to hang as outlined above, you know you have an issue with RPC/HTTP and it needs to be resolved.
To start, open the Exchange Remote Connectivity Analyzer (ExRCA). Choose the Outlook Anywhere (RPC over HTTP) option and fill in the required details.
If you have a healthy connection, you'll see a screen with a number of green checkmarks. If the test encounters an issue, you'll get the dreaded red X.
If you have a corrupted RPC over HTTP module, more than likely you've received a note about error HTTP 500.
This issue causes the RPC/HTTP connection to freeze when it attempts to resolve the names within the connection settings. It will eventually time out, or you'll end up force-quitting the task in Outlook because it not responding.
To fix this issue, follow these steps:
- Go to the Exchange Management Console (EMC) and disable Outlook Anywhere.
- Open PowerShell and run the servermanagercmd -r rpc-over-http-proxy command.
- Reboot the server.
- Reinstall the RPC proxy component, then open PowerShell and run the servermanagercmd -i rpc-over-http-proxy command.
- Enable Outlook Anywhere in the EMC.
- Go to the service.msc console and restart the Microsoft Active Directory Topology Service.
Now, run the ExRCA utility again and you should receive a page with all green check marks; Outlook Anywhere connectivity has been restored.
About the author
This was first published in February 2013