I have a problem with Exchange 2013 and the OWAProxyMonitor. Maybe someone can help me or tell me what I should do to get this fixed. I just opened a MS case ([REG:113061110504400]) about the problem with the OWYProxyMonitor Health Check being unhealthy.
The problem is, when I set the authentication of the OWAVirtualDirectory to Basic and Windows authentication, the OWAProxyMonitor HealthCheck becomes unhealthy and I get the following error message in the “Monitoring” eventlog:
-------------------------------------------------
The OWA.Proxy health set has detected a problem on EXSERVER beginning at 6/11/2013 1:21:26 PM (UTC). The health manager is reporting that recycling the MSExchangeOWAAppPool app pool has failed to restore health and it has requested the protocol be marked offline. Attempts to auto-recover from this condition have failed and requires Administrator attention. Details below:
<b>MachineName:</b>EXSERVER
<b>ServiceName:</b> OWA.Proxy
<b>ResultName:</b> OWAProxyTestProbe/MSExchangeOWAAppPool
<b>Error:</b> CafeLocalProbe MSExchangeOWAAppPool FAILED: FailedResponse
<b>Exception:</b> System.ApplicationException: CafeLocalProbe MSExchangeOWAAppPool FAILED: FailedResponse
at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeLocalProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Exchange.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Exchange.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()
<b>ExecutionContext:</b> probe defined timeout=60000ms, actual timeout=60000ms, http request timeout=59000ms
OWA FailedResponse after 0 milliseconds.The remote server returned an error: (400) Bad Request.+[000.000] selected OWA from OWAProxyTestProbe
[000.000] calculated wait time 59000 ms
[000.000] starting HTTP request task
[000.000] waiting 59000 ms
[000.000] issuing POST againsthttps://localhost/OWA/auth.owa
[000.000] awaiting POST response
<b>FailureContext:</b> MSExchangeOWAAppPool
<b>ResultType:</b> Failed
<b>IsNotified:</b> False
<b>DeploymentId:</b> 0
<b>RetryCount:</b> 0
<b>ExtensionXml:</b>
<b>Version:</b>
<b>StateAttribute1:</b> MSExchangeOWAAppPool
<b>StateAttribute2:</b> Credentials:HealthMailbox5ed0fe35f5fe479b9866b42587558e25@domain.it CIRIJUaH%(.oTY@*jharD+s&hqvr>FjxDoVfE82miqB)%;O%d{K2_!je%:Di5ZPiaKcaTaVY-s{;ag9zP>M7Spq0O#T1&k^astf:w3eru4ZQphe3[LLLN_522JJ_!!@J
<b>StateAttribute3:</b> FailurePoint=BackEnd, HttpStatusCode=400, Error=BadRequest, Details=System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass20.<OnResponseReady>b__1e()
<b>StateAttribute4:</b>
<b>StateAttribute5:</b>
<b>StateAttribute6:</b> 0
<b>StateAttribute7:</b> 0
<b>StateAttribute8:</b> 0
<b>StateAttribute9:</b> 0
<b>StateAttribute10:</b> 0
<b>StateAttribute11:</b>
<b>StateAttribute12:</b>
<b>StateAttribute13:</b>
<b>StateAttribute14:</b>
<b>StateAttribute14:</b>
<b>StateAttribute16:</b> 0
<b>StateAttribute17:</b> 0
<b>StateAttribute18:</b> 0
<b>StateAttribute19:</b> 0
<b>StateAttribute20:</b> 0
<b>StateAttribute21:</b>
<b>StateAttribute22:</b>
<b>StateAttribute23:</b>
<b>StateAttribute24:</b>
<b>StateAttribute25:</b>
<b>PoisonedCount:</b> 0
<b>ExecutionId:</b> 15879172
<b>ExecutionStartTime:</b> 6/11/2013 2:21:32 PM
<b>ExecutionEndTime:</b> 6/11/2013 2:21:32 PM
<b>ResultId:</b> 819607
<b>SampleValue:</b> 31
-------------------------------------------------------------------------------
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -IdentityEXSERVER -HealthSet 'OWA.Proxy'
State Name TargetResource HealthSet AlertValue ServerComponent
----- ---- -------------- --------- ---------- ---------------
Offline OWAProxyTestMonitor MSExchangeOWAAppPool OWA.Proxy Degraded OwaProxy
Offline OWAProxyTestMonitor MSExchangeOWACalendarAppPool OWA.Proxy Healthy OwaProxy
States of all health sets:
Note: Data may be stale. To get current data, run: Get-HealthReport -IdentityEXSERVER
State HealthSet AlertValue LastTransitionTime MonitorCount
----- --------- ---------- ------------------ ------------
NotApplicable ActiveSync Healthy 5/24/2013 11:58:13 AM 3
NotApplicable AD Healthy 5/24/2013 10:52:32 AM 10
NotApplicable ECP Healthy 5/27/2013 3:31:50 PM 1
NotApplicable EDS Healthy 5/24/2013 10:53:14 AM 9
Online FrontendTransport Healthy 5/24/2013 3:18:11 PM 11
Online HubTransport Healthy 6/10/2013 7:55:47 PM 27
NotApplicable DataProtection Healthy 5/24/2013 10:48:52 AM 1
NotApplicable Monitoring Unhealthy 6/10/2013 8:02:48 PM 9
NotApplicable Network Healthy 6/10/2013 5:50:34 PM 1
NotApplicable FIPS Healthy 5/24/2013 10:49:57 AM 3
Online Transport Healthy 6/10/2013 7:57:33 PM 9
NotApplicable RPS Healthy 5/24/2013 10:44:16 AM 1
Online UM.CallRouter Healthy 6/10/2013 7:48:01 PM 7
NotApplicable UserThrottling Healthy 6/10/2013 8:15:28 PM 7
NotApplicable Search Healthy 5/24/2013 10:51:22 AM 9
NotApplicable AntiSpam Healthy 5/24/2013 10:49:09 AM 3
NotApplicable Security Healthy 5/24/2013 10:50:51 AM 3
NotApplicable IMAP.Protocol Healthy 5/24/2013 10:51:23 AM 3
NotApplicable Datamining Healthy 5/24/2013 10:50:03 AM 3
NotApplicable Provisioning Healthy 5/24/2013 10:45:29 AM 3
NotApplicable POP.Protocol Healthy 5/24/2013 10:44:47 AM 3
NotApplicable Outlook Healthy 5/27/2013 2:57:55 PM 5
NotApplicable ProcessIsolation Healthy 5/24/2013 10:51:13 AM 12
NotApplicable Store Healthy 5/24/2013 10:49:33 AM 6
NotApplicable TransportSync Healthy 5/24/2013 10:52:27 AM 3
NotApplicable EventAssistants Healthy 5/24/2013 10:52:03 AM 2
NotApplicable MRS Healthy 5/24/2013 10:51:23 AM 3
NotApplicable MailboxTransport Healthy 5/24/2013 10:48:43 AM 2
NotApplicable MessageTracing Healthy 5/24/2013 10:52:33 AM 3
NotApplicable CentralAdmin Healthy 5/24/2013 10:52:38 AM 3
NotApplicable UM.Protocol Healthy 5/24/2013 10:48:27 AM 3
NotApplicable Autodiscover.Protocol Healthy 5/24/2013 10:50:08 AM 3
Online ECP.Proxy Healthy 5/24/2013 11:57:31 AM 4
NotApplicable OAB Healthy 5/24/2013 10:52:40 AM 3
NotApplicable OWA.Protocol Healthy 5/24/2013 10:52:24 AM 3
NotApplicable Calendaring Healthy 5/24/2013 10:50:26 AM 3
Online RPS.Proxy Healthy 5/24/2013 11:57:31 AM 13
Online RWS.Proxy Healthy 5/24/2013 11:57:31 AM 10
NotApplicable PushNotifications.Protocol Healthy 5/24/2013 10:50:25 AM 3
NotApplicable EWS.Protocol Healthy 5/24/2013 10:45:06 AM 3
NotApplicable ActiveSync.Protocol Healthy 5/24/2013 10:45:33 AM 3
Online Autodiscover.Proxy Healthy 5/24/2013 11:57:31 AM 1
Online ActiveSync.Proxy Healthy 5/24/2013 11:57:32 AM 1
Online EWS.Proxy Healthy 5/24/2013 11:57:31 AM 1
Online OAB.Proxy Healthy 5/24/2013 11:57:31 AM 1
Offline OWA.Proxy Degraded 6/11/2013 3:36:27 PM 2
Online Outlook.Proxy Healthy 5/24/2013 11:57:31 AM 1
NotApplicable OWA Healthy 5/24/2013 11:58:04 AM 1
NotApplicable RemoteMonitoring Healthy 6/9/2013 4:59:58 PM 3
NotApplicable Autodiscover Healthy 6/9/2013 8:50:27 PM 1
NotApplicable EWS Healthy 6/9/2013 8:50:27 PM 1
Note: Subsequent detected alerts are suppressed until the health set is healthy again.
-------------------------------------------------
When I change the authentication from Basic and Windows authentication to FBA, Health Monitoring reports a healthy state of the OWAProxyMonitor.
Actually I’m publishing Exchange with UAG 2010 SP3 and I have to set the OWA authentication from FBA to Basic for don’t getting the double authentication problem. If I set authentication to FBA, I have to authenticate me at the UAG logon screen and then at the OWA logon (Exchange).
OWA and OWA Proxy to 2010 works internally and externally fine . The Microsoft technician told me that the health monitoring is only a visual failure and everything is OK.
Is there a solution to get this fixed?