I am facing issue in Exchange 2013 CU2, I got this alert from SCOM 2012 atleast 5-6 times a day, OWA health set is unhealthy, I have done all the steps mentioned in this web link. Authentication type for OWA Virtual directory is integrated windows and Basic. I have 2 CAS servers, and this alert generated from both of them.
http://technet.microsoft.com/en-us/library/ms.exch.scom.OWA(EXCHG.150).aspx?v=15.0.712.24
Alert: Health Set unhealthy
Source: EX-CAS - OWA
Path: EX-CAS;EX-CAS
Last modified by: System
Last modified time: 1/5/2014 8:15:08 PM
Alert description: Outlook Web Access logon is failing on ClientAccess server EX-CAS.
Availability has dropped to 0%. You can find protocol level traces for the failures on C:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\OWA\ClientAccessProbe.
Incident start time: 1/6/2014 4:05:08 AM
Last failed result:
Failing Component - Owa
Failure Reason - CafeFailure
Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException: Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Failure source: Owa
Failure reason: CafeFailure
Failing component:Owa
Exception hint: CafeErrorPage: CafeFailure Unauthorized Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
---> Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
--- End of inner exception stack trace ---
at Microsoft.Exchange.Net.MonitoringWebClient.BaseExceptionAnalyzer.Analyze(TestId currentTestStep, HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, Action`1 trackingDelegate)
at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.AnalyzeResponse[T](HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndSend[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse, Boolean fireResponseReceivedEvent)
at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndGet[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
at Microsoft.Exchange.Net.MonitoringWebClient.Authenticate.AuthenticationResponseReceived(IAsyncResult result)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
at Microsoft.Exchange.Net.MonitoringWebClient.Owa.OwaLogin.AuthenticationCompleted(IAsyncResult result)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Bool
-------------------------------------------------------------------------------
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'EX-CAS' -HealthSet 'OWA'
State Name TargetResource HealthSet AlertValue ServerComponent
----- ---- -------------- --------- ---------- ---------------
NotApplicable OwaCtpMonitor OWA Unhealthy None
States of all health sets:
Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX-CAS'
State HealthSet AlertValue LastTransitionTime MonitorCount
----- --------- ---------- ------------------ ------------
NotApplicable ActiveSync Healthy 1/3/2014 5:21:13 AM 2
NotApplicable AD Healthy 11/24/2013 6:54:18 AM 10
NotApplicable ECP Healthy 1/5/2014 3:03:05 AM 1
Online Autodiscover.Proxy Healthy 11/20/2013 10:06:37 AM 1
NotApplicable Autodiscover Healthy 1/3/2014 10:18:17 PM 2
Online ActiveSync.Proxy Healthy 11/20/2013 10:06:37 AM 1
Online ECP.Proxy Healthy 11/21/2013 6:16:08 PM 4
Online EWS.Proxy Healthy 11/20/2013 10:06:37 AM 1
Online OutlookMapi.Proxy Healthy 11/24/2013 6:54:28 AM 4
Online OAB.Proxy Healthy 11/19/2013 7:14:34 PM 1
Online OWA.Proxy Healthy 11/20/2013 10:06:37 AM 2
NotApplicable EDS Healthy 1/3/2014 5:19:56 AM 10
Online RPS.Proxy Healthy 1/3/2014 5:21:27 AM 13
Online RWS.Proxy Healthy 1/3/2014 5:20:09 AM 10
Online Outlook.Proxy Healthy 1/3/2014 5:21:12 AM 4
NotApplicable EWS Healthy 1/3/2014 10:18:17 PM 2
Online FrontendTransport Healthy 1/5/2014 3:47:09 AM 11
Online HubTransport Healthy 1/5/2014 3:47:09 AM 29
NotApplicable Monitoring Unhealthy 1/5/2014 4:05:57 AM 9
NotApplicable DataProtection Healthy 1/3/2014 5:25:42 AM 1
NotApplicable Network Healthy 1/4/2014 1:51:16 PM 1
NotApplicable OWA Unhealthy 1/5/2014 8:05:08 PM 1
NotApplicable FIPS Healthy 1/3/2014 5:21:12 AM 3
Online Transport Healthy 1/5/2014 4:11:00 AM 9
NotApplicable RPS Healthy 11/20/2013 10:07:12 AM 2
NotApplicable Compliance Healthy 11/20/2013 10:08:10 AM 2
NotApplicable Outlook Healthy 11/21/2013 6:12:54 PM 2
Online UM.CallRouter Healthy 1/5/2014 3:47:10 AM 7
NotApplicable UserThrottling Healthy 1/5/2014 4:16:42 AM 7
NotApplicable Search Healthy 11/24/2013 6:55:06 AM 9
NotApplicable AntiSpam Healthy 1/3/2014 5:16:43 AM 3
NotApplicable Security Healthy 1/3/2014 5:19:28 AM 3
NotApplicable IMAP.Protocol Healthy 1/3/2014 5:21:14 AM 3
NotApplicable Datamining Healthy 1/3/2014 5:18:34 AM 3
NotApplicable Provisioning Healthy 1/3/2014 5:19:56 AM 3
NotApplicable POP.Protocol Healthy 1/3/2014 5:20:44 AM 3
NotApplicable Outlook.Protocol Healthy 1/3/2014 5:19:46 AM 3
NotApplicable ProcessIsolation Healthy 1/3/2014 5:19:26 AM 9
NotApplicable Store Healthy 1/3/2014 5:20:38 AM 6
NotApplicable TransportSync Healthy 11/24/2013 6:53:09 AM 3
NotApplicable MailboxTransport Healthy 1/3/2014 5:21:11 AM 6
NotApplicable EventAssistants Healthy 11/21/2013 6:22:01 PM 2
NotApplicable MRS Healthy 1/3/2014 5:20:29 AM 3
NotApplicable MessageTracing Healthy 1/3/2014 5:18:15 AM 3
NotApplicable CentralAdmin Healthy 1/3/2014 5:17:25 AM 3
NotApplicable UM.Protocol Healthy 1/3/2014 5:17:08 AM 3
NotApplicable Autodiscover.Protocol Healthy 1/3/2014 5:17:13 AM 3
NotApplicable OAB Healthy 1/3/2014 5:20:51 AM 3
NotApplicable OWA.Protocol Healthy 1/3/2014 5:20:52 AM 3
NotApplicable Calendaring Healthy 11/24/2013 6:56:59 AM 3
NotApplicable PushNotifications.Protocol Healthy 11/21/2013 6:16:05 PM 3
NotApplicable EWS.Protocol Healthy 1/3/2014 5:19:07 AM 3
NotApplicable ActiveSync.Protocol Healthy 1/3/2014 5:20:16 AM 3
NotApplicable RemoteMonitoring Healthy 1/5/2014 3:47:09 AM 3
Any solution for this alert, how to rectify it, but OWA is running perfect for all users.