I am getting an error on CAS servers after upgrade form exchnage 2010 sp1 to Exchange 2010 SP2 rollup 3,this error is reported through SCOM 2007 R2, i run the commnad manully test-ecpconnectivity no error in the result [Alert] : Exchange Control Panel connectivity (Internal) transaction failures. [Source] : ECP - XCHG-CAS3 (Client Access) - Default-First-Site-Name [Path] : XCHG-CAS3.msg.dubai.gov.ae;XCHG-CAS3 (Client Access) - Default-First-Site-Name [Last modified by] : System [Last modified time] : 7/20/2012 11:15:51 AM [Alert Description] : One or more of the ECP connectivity tests failed. Detailed information: ------------------------------------- Target: XCHG-CAS3.msg.dubai.gov.ae|Default-First-Site-Name Error: An exception was thrown by the Web service: The remote server returned an error: (500) Internal Server Error. Details: ------------------------------------- Diagnostic command: "Test-EcpConnectivity -TestType:Internal -MonitoringContext:$true -TrustAnySSLCertificate:$true -LightMode:$true" EventSourceName: MSExchange Monitoring ECPConnectivity Internal Knowledge: http://go.microsoft.com/fwlink/?LinkID=67336&id=F0A79980-0D69-4A9B-8B14-3D07A5F0827F Computer: XCHG-CAS3.msg.dubai.gov.ae Impacted Entities (0): [Alert Severity] : 2 [Alert Priority] : 2 [Alert Name] : Exchange Control Panel connectivity (Internal) transaction failures. [Alert Category] : Alert [Alert State] : New [Alert Closed By] : [Alert Raised Time] : 7/20/2012 11:15:51 AM [Alert Closed Time] :

What is impact do you see at this point of time ? Thanks, Ashwini KumarKnow more about Messaging :-)

i am clueless , even i didnt find any impect , but SCOM gives me an error ,h'

Is there any related error in your client server's event log? What is the result of this command "Test-EcpConnectivity"? Test-EcpConnectivity http://technet.microsoft.com/en-us/library/dd351282(v=exchg.150).aspx Thanks, EvanEvan Liu TechNet Community Support

Test-EcpConnectivity is fine when i run manually , ui am getting same erro in event viewer

Dear All , WE had open a case with microsft ,they had conformed me it is a bug in Exchnage 2010 R2 rollupdate 3 , it will fix in rollupdate 6

Did you get any feedback from Microsoft on this? We just upgraded to RU # 4 and we only started to get these alerts in our environment now.