OWA/ECP Monitoring 401 after CU2 (Network Steve Forum)

OWA/ECP Monitoring 401 after CU2

We are running mixed Exchange 2010 SP3 and Exchange 2013 CU2. Was previously on CU1. After installing CU2, the monitors for OWA and ECP failing with 401. Both are working fine for users, and monitoring was working fine on CU1. Looking at the log its just a 401 for every test on OWA and ECP. From the log:

2013-07-17T00:02:05.315Z,---------------------------------------------------------------------------------------------
2013-07-17T00:02:05.299Z,"Starting Owa probe with Target: https://localhost/owa/, Username: HealthMailboxc0fc5e348e004bd28a70ec1f8e5c1b30@asmr.com "
2013-07-17T00:02:05.299Z,Test step started: OwaLoginScenario
2013-07-17T00:02:05.299Z,Test step started: Authentication
2013-07-17T00:02:05.299Z,"Request being sent:
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
"
2013-07-17T00:02:05.299Z,"OWA logon scenario failed: 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: ba2812e2-659b-4b21-895e-ab49ffc6bcf9
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/8.0
WWW-Authenticate: Negotiate,NTLM,Basic realm=""localhost""
X-Powered-By: ASP.NET
X-FEServer: S1EX2013-01
Date: Wed, 17 Jul 2013 00:02:05 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:

   --- 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, Boolean requiresSynchronization)
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:

July 17th, 2013 4:29pm

Hi,

I am only aware of the the following known issue:

See the "Exchange Control Panel might not work when requests are proxied through Exchange 2013" section in the following article:

http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx

If it is not related to your problem, please refer to the IIS log and let me know the detailed error code, like 401.1, 401.2.

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Free Windows Admin Tool Kit Click here and download it now

July 18th, 2013 1:51pm

Looks like the OWA probe is getting 401.2 and the ECP probe is 401.0

#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken

2013-07-18 18:02:47 172.30.1.9 GET /ecp/ &cafeReqId=34c9629c-87f0-4baa-9bfd-e7b7c5e1aca2; 443 - 172.30.1.9 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 401 0 0 0

2013-07-18 18:04:32 ::1 GET /owa/ &cafeReqId=457a3b11-702e-4623-a9a7-9128e56b3aa5; 443 - ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWACTP) - 401 2 5 0

July 18th, 2013 2:19pm

Looking the IIS logs some more and comparing to before I installed CU2, it went and goes something like this:

CU1

-Access /owa/ anonymously and get the 401.2

-Access /owa/ using a monitoring account and get 200

-Do some other actions, presumably monitoring actions

-Logoff

-End

CU2

-Access /owa/ anonymously and get the 401.2

-End

I can't fathom why its no longer trying to logon with a monitoring account. OWA is setup to use WindowsAuth and Basic, same as with CU1.

Free Windows Admin Tool Kit Click here and download it now

July 18th, 2013 2:54pm

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