Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

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

View products that this article applies to.

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.


↑ Back to the top

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.

↑ Back to the top

Resolution

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

↑ Back to the top

Status

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

↑ Back to the top

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

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2572958
Revision : 2
Created on : 9/26/2018
Published on : 9/26/2018
Exists online : False
Views : 425