The "Test-OutlookConnectivity -Protocol HTTP" cmdlet fails to test the Outlook Anywhere connectivity in an Exchange Server 2010 environment

Article translations Article translations
Article ID: 2572958 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You enable the Outlook Anywhere (known as RPC over HTTP) feature on a Microsoft Exchange Server 2010 Client Access server.
  • You configure only one external host name for Outlook Anywhere, Outlook Web App (OWA), Microsoft Exchange Web Service (EWS) and so on.
  • You run the Test-OutlookConnectivity -Protocol HTTP cmdlet in the Exchange Management Shell (EMS) to test the Outlook Anywhere connectivity.
In this scenario, the cmdlet fails. Additionally, you receive an error message that resembles the following in verbose logging:
VERBOSE: [<Time>] Test-OutlookConnectivity : Pinging RpcProxy at the following URL: 
http://<FQDN of the RPC proxy server>/rpc/RpcProxy.dll.
VERBOSE: [<Time>] Test-OutlookConnectivity : An unexpected exception occurred while pinging RpcProxy. The most common reason for this occurring is that the IIS DefaultAppPool isn't running. Exception: The remote server
returned an error: (401) Unauthorized.


CAUSE

This issue occurs because the Client Access server performs remote procedure call (RPC) proxy when only one external host name is used. However, RPC proxy does not support Kerberos authentication.

RESOLUTION

To resolve this issue, install the following update rollup:
2582113 Description of Update Rollup 5 for Exchange Server 2010 Service Pack 1

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about the Test-OutlookConnectivity cmdlet, visit the following Microsoft website:
General information about the Test-OutlookConnectivity cmdlet
For more information about 401.x-Unauthorized, visit the following Microsoft website:
General information about 401.x-Unauthorized
For more information about how to enable Outlook Anywhere, visit the following Microsoft website:
General information about how to enable Outlook Anywhere
For more information about how to configure an external host name for Outlook Anywhere, visit the following Microsoft website:
General information about how to configure an external host name for Outlook Anywhere
For more information about Client Access server proxy and redirection, visit the following Microsoft website:
General information about Client Access server proxy and redirection

Properties

Article ID: 2572958 - Last Review: August 24, 2011 - Revision: 1.0
APPLIES TO
  • Microsoft Exchange Server 2010 Service Pack 1, when used with:
    • Microsoft Exchange Server 2010 Standard
    • Microsoft Exchange Server 2010 Enterprise
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2572958

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com