Here is some notes from a recent issue error that I encountered this week with an Exchange 2010 server configured for Outlook Anywhere. For some reason Outlook Anywhere stopped working and the Outlook Anywhere (RPC over HTTP) clients were no longer able to connect.
After checking all the basics in Exchange, like:
- Confirming the OA settings
- Certificates (not expired and common name)
- Firewall rules
- Autodiscover etc.
- I ran the tests from www.TestExchangeConnectivity.com and it showed an error response, expanding the log it this in the end:
Testing Http Authentication Methods for URL https://mail.MyDomain.com/rpc/rpcproxy.dll
The HTTP authentication test failed.
An HTTP 500 response was returned from Unknown
For Outlook Anywhere confirm the following:
- That your domain “mail.mydomain.com” is the common name in the certificate and that the output is correct in the EXPR provider
- That redirection is not configured on the IIS virtual directory
- Check the SSL settings of /RPC virtual directory, it should be: Require SSL (Checked), Require 128-bit SSL (Unchecked), Client certificates: Ignore
- If the above does not help, you may have to reinstall the RPC Proxy component, I found that reinstalling the RPC Proxy component solved my problem and according to several searches on
The process of reinstalling RPC Proxy is:
- Disable Outlook Anywhere using EMC or EMS
- Remove RPC proxy component using the command: servermanagercmd -r rpc-over-http-proxy
- Reboot the server
- Install RPC proxy component using the command: servermanagercmd -i rpc-over-http-proxy
- Enable Outlook Anywhere
- Restart Microsoft Active Directory Topology service
- Check if the issue still exists
- The reinstall of the RPC Proxy component solved the problem for me.