You encounter failures when you run the Test-EcpConnectivity cmdlet to test Exchange Control Panel connectivity in an Exchange Server 2010 environment

Applies to: Microsoft Exchange Server 2010 Service Pack 2Exchange Server 2010 EnterpriseExchange Server 2010 Standard

Symptoms


In a Microsoft Exchange Server 2010 environment, you encounter failures when you run the Test-EcpConnectivity cmdlet to test Exchange Control Panel connectivity to a server that is running Exchange Server 2010 and has the Client Access server role installed. Also, if the Exchange Server 2010 environment is monitored by Microsoft System Center Operations Manager (SCOM) 2007 R2, the administrator receives the following alerts every five minutes because this cmdlet is executed:
Source: MSExchange Monitoring ECPConnectivity External
Id: 1001
Type: Error
Message: One or more of the ECP connectivity tests failed.
Detailed information:
Target: Client Access Server|Site

Error: The server didn't return a user context cookie.

Cause


This issue occurs because the Test-EcpConnectivity cmdlet uses an invalid user-agent string in HTTP requests when it tries to connect to the Exchange Server 2010 Client Access server.

Resolution


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

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-EcpConnectivity cmdlet, visit the following Microsoft website:
For more information about user-agent strings, visit the following Microsoft website:
For more information about Exchange Control Panel connectivity transaction failures, visit the following Microsoft website: