ECP.Proxy Offline The remote server returned an error: (401) Unauthorized

Hi Forum,

Is there a way to properly troubleshoot this ECP.Proxy issue? As you can see there are more unhealthy components however this one is causing an issue with our Kemp loadbalancer and flagging the server as down.

[PS] C:\test>Get-HealthReport mailserver | ? {$_.AlertValue -eq 'Unhealthy'} | ft -AutoSize

Server   State         HealthSet        AlertValue LastTransitionTime MonitorCount
------   -----         ---------        ---------- ------------------ ------------
mailserver NotApplicable AMScanTimeout    Unhealthy  13-3-2015 11:11:07 6
mailserver Online        HubTransport     Unhealthy  13-3-2015 11:01:04 97
mailserver NotApplicable MailboxTransport Unhealthy  11-3-2015 22:16:25 26
mailserver NotApplicable DataProtection   Unhealthy  13-3-2015 10:18:13 48
mailserver NotApplicable OWA              Unhealthy  13-3-2015 06:49:23 19
mailserver Offline       ECP.Proxy        Unhealthy  7-3-2015 13:59:10  1

On the other MBX/CAS dual-role member:

[PS] C:\temp>Get-HealthReport mailserver11 | where {$_.AlertValue -eq 'unhealthy'} | ft -AutoSize

Server   State         HealthSet AlertValue LastTransitionTime MonitorCount
------   -----         --------- ---------- ------------------ ------------
mailserver11 NotApplicable EDS       Unhealthy  12-3-2015 17:02:22 44
mailserver11 NotApplicable OWA       Unhealthy  13-3-2015 10:52:17 19

In the event log I see:

and at the bottom

I have been able to find a solution but it's looking like an authorization problem but where and how can I fix this?

Tnx,

Tim

March 13th, 2015 7:57am

Hi Timmy,

Please make sure you have run as Administrator, and check the MSExchangeServiceHost service is running well.

 

Thanks

Free Windows Admin Tool Kit Click here and download it now
March 16th, 2015 3:03am

Hi Mavis.

Run what as administrator and how do I verify the ExchangeServcieHost if there aren't any logs reflecting issues with this service?

Tnx

Tim

March 16th, 2015 1:15pm

Hi Forum,

I have found the solution. Apparently since we are NOT using forms based authentication Managed Availability will always fail with a 401 error. This (I guess) is the normal behavior.

Thanks to http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx I have successfully disabled the ECP.Proxy probe and the Kemp is a happy camper. It still does not explain why mailserver11 doesn't show this error. But i's satisfied.

Tim

Free Windows Admin Tool Kit Click here and download it now
March 17th, 2015 4:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics