Get-healthreport unhealthy

Hi all,
been installing Exchange 2013 ( cu1,cu2 and cu3) a couple of times and out of the Box it seems like some healthset are unhealthy or disabled.
Still everything seems to work (most important like ActiveSync,owa,oab and ecp) even those healthsets are unhealthy.
What is the main reason for this?
My lab environment is really simple,only firewall is my D-Link router,no co-existing (just Exchange 2013) With one site and one AD.
Thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi,
According to the screenshot, we can see that the Outlook.Proxy health set is unhealthy.
I recommend you refer to the following article to troubleshoot the issue:
Troubleshooting Outlook.Proxy Health Set
The Outlook.Proxy health set monitors the availability of the Outlook Anywhere proxy infrastructure on the Client Access server (CAS).
If you receive an alert that specifies that the Outlook.Proxy service is unhealthy, this indicates an issue that may prevent users from accessing their mail.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

Help with Autodiscover.Proxy Unhealthy state.

Hello, I am trying to diagnose unhealthy systems in Exchange 2013. Here is my command and output. Lets start with the first one, Autodiscover.Proxy.
[PS] C:\Windows\system32>Get-HealthReport -Server email| where {$_.alertvalue -ne "Healthy" }
Server State HealthSet AlertValue LastTransitionTime MonitorCount
email Offline Autodiscover.Proxy Unhealthy 11/19/2014 10:52... 1
email Online HubTransport Unhealthy 11/24/2014 6:38:... 96
email Online FrontendTransport Unhealthy 9/25/2014 9:28:3... 12
email NotApplicable MSExchangeCertif... Disabled 1/1/0001 12:00:0... 2
I go to follow this article here: http://technet.microsoft.com/en-us/library/ms.exch.scom.autodiscover.proxy%28v=exchg.150%29.aspx
But the issue is that Invoke-MonitoringProbe does not return anything of value to me. Can you help me analyze this output?
[PS] C:\Windows\system32>Invoke-MonitoringProbe Autodiscover.Proxy\AutoDiscoverProxyTestProbe -Server email | Format-Lis
t
RunspaceId : bfa8f7cf-cc0b-4395-b3c8-75ab16fc227c
Server : email
MonitorIdentity : Autodiscover.Proxy\AutoDiscoverProxyTestProbe
RequestId : d677ac2a-43fa-4147-b806-b2f433c5a6e3
ExecutionStartTime : 11/25/2014 3:23:33 PM
ExecutionEndTime : 11/25/2014 3:23:33 PM
Error : Unknown app pool name:
Exception : System.InvalidOperationException: Unknown app pool name:
at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeLocalProbe.DoWork(Cancellati
onToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken
joinedToken)
at
Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()
PoisonedCount : 0
ExecutionId : 60170839
SampleValue : 0
ExecutionContext : Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms
FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : d677ac2a43fa4147b806b2f433c5a6e3-AutoDiscoverProxyTestProbe
IsNotified : False
ResultId : 27004887
ServiceName : InvokeNow
StateAttribute1 :
StateAttribute2 :
StateAttribute3 :
StateAttribute4 :
StateAttribute5 :
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 :
StateAttribute12 :
StateAttribute13 :
StateAttribute14 :
StateAttribute15 :
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 :
StateAttribute22 :
StateAttribute23 :
StateAttribute24 :
StateAttribute25 :
Identity : 956989c13cc44e6faf102491a8d7a11b
IsValid : True
ObjectState : New
I'm not seeing any issue right now with Autodiscover but I don't want a larger issue to show up in the near future.

Ok, I guess we can do that. A new health set came up today Unhealthy. Its Compliance and in a NotApplicable state. I will try to determine the impact of this and start a different thread on that if I can't figure that one out.
Otherwise I don't see any problem with mail.
More info, not sure if I posted this, but if this helps, the Event Viewer states this:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring Source: Microsoft-Exchange-ManagedAvailability Date: 12/23/2014 7:03:08 AM Event ID: 4 Task Category: Monitoring Level: Error Keywords: User: SYSTEM Computer: email.domain.com Description: The Autodiscover.Proxy
health set has detected a problem on EMAIL beginning at 12/22/2014 3:01:12 PM (UTC). The health manager is reporting that recycling the MSExchangeAutodiscoverAppPool 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 administrator attention is required.
Details below: MachineName: EMAIL
ServiceName: Autodiscover.Proxy
ResultName: AutodiscoverProxyTestProbe/MSExchangeAutodiscoverAppPool
Error: The remote server returned an error: (500) Internal Server Error.
Exception: System.ApplicationException: The remote server returned an error: (500) Internal Server Error. at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeLocalProbe.DoWork(CancellationToken cancellationToken) at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken
joinedToken) at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<startexecuting>b__0() at System.Threading.Tasks.Task.Execute() </startexecuting>
<startexecuting>ExecutionContext: Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms FailedResponse after 0 milliseconds. The remote server returned an error: (500) Internal Server Error.
[000.000] Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms [000.000] Starting HTTP request task [000.000] Waiting 59000 ms [000.000] Issuing GET against https://autodiscover.domain.com/AutoDiscover/ [000.000] Awaiting
GET response [000.000] Performing SSL validation [000.000] Failed with exception: The remote server returned an error: (500) Internal Server Error. </startexecuting>
<startexecuting>FailureContext:</startexecuting>
<startexecuting></startexecuting>ResultType: Failed
IsNotified: False
DeploymentId: 0
RetryCount: 0
ExtensionXml:
StateAttribute1: No response headers available.
StateAttribute2: [email protected] cfj>M!T@O-;XNkj+=u8[SL#f8Oby*S:(&Bg@GTal_=R@3YXtGi=%Vj832L_AE|l>Jhy18K/an^cNHv7i*3-8d*9?#FQa8u!IUoAai-mr(&PG|ZALs2&?6hI2N]9NKK][
StateAttribute3:
StateAttribute4:
StateAttribute5:
StateAttribute6: 0
StateAttribute7: 0
StateAttribute8: 0
StateAttribute9: 0
StateAttribute10: 0
StateAttribute11:
StateAttribute12:
StateAttribute13:
StateAttribute14:
StateAttribute14:
StateAttribute16: 0
StateAttribute17: 0
StateAttribute18: 0
StateAttribute19: 0
StateAttribute20: 0
StateAttribute21:
StateAttribute22:
StateAttribute23:
StateAttribute24:
StateAttribute25:
PoisonedCount: 0
Client Access Array: Client Access Array name could not be retrieved.
ExecutionId: 30334093
ExecutionStartTime: 12/23/2014 12:03:08 PM
ExecutionEndTime: 12/23/2014 12:03:08 PM
ResultId: 32263287
SampleValue: 0 Event Xml:
<event style="font-size:0.75em;line-height:1.5;" xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><system><provider guid="{C424A887-A89F-455F-8319-960917152221}" name="Microsoft-Exchange-ManagedAvailability"><eventid>4</eventid>
<version>0</version> <level>2</level> <task>2</task> <opcode>0</opcode> <keywords>0x8000000000000000</keywords> <timecreated systemtime="2014-12-23T12:03:08.889029200Z"><eventrecordid>7753</eventrecordid>
<correlation activityid="{ED377619-21A3-44A7-9444-751CDE95B0A1}"><execution processid="4204" threadid="14216"><channel>Microsoft-Exchange-ManagedAvailability/Monitoring</channel> <computer>email.domain.com</computer>
<security userid="S-1-5-18"></security></execution></correlation></timecreated></provider></system> <userdata><eventxml xmlns="myNs" xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events"><healthset>Autodiscover.Proxy</healthset>
<subject>Exchange Server Alert: The Autodiscover.Proxy health set is unhealthy.</subject> <message>The Autodiscover.Proxy health set has detected a problem on EMAIL beginning at 12/22/2014 3:01:12 PM (UTC). The health manager is reporting
that recycling the MSExchangeAutodiscoverAppPool 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 administrator attention is required. Details below: MachineName:
EMAIL ServiceName: Autodiscover.Proxy ResultName: AutodiscoverProxyTestProbe/MSExchangeAutodiscoverAppPool Error: The remote server returned an error: (500) Internal Server Error. Exception:
System.ApplicationException: The remote server returned an error: (500) Internal Server Error. at Microsoft.Exchange.Monitoring.ActiveMonitoring.ClientAccess.CafeLocalProbe.DoWork(CancellationToken cancellationToken) at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken
joinedToken) at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0() at System.Threading.Tasks.Task.Execute() ExecutionContext: Probe Absolute Timeout=60000ms, Timeout Value=60000ms,
Calculated HttpRequest Timeout=59000ms FailedResponse after 0 milliseconds. The remote server returned an error: (500) Internal Server Error. [000.000] Probe Absolute Timeout=60000ms, Timeout Value=60000ms, Calculated HttpRequest Timeout=59000ms [000.000]
Starting HTTP request task [000.000] Waiting 59000 ms [000.000] Issuing GET against https://autodiscover.domain.com/AutoDiscover/ [000.000] Awaiting GET response [000.000] Performing SSL validation [000.000] Failed with exception: The remote server returned
an error: (500) Internal Server Error. FailureContext: ResultType: Failed IsNotified: False DeploymentId: 0 RetryCount: 0 ExtensionXml: StateAttribute1:
No response headers available. StateAttribute2: [email protected] cfj>M!T@O-;XNkj+=u8[SL#f8Oby*S:(&Bg@GTal_=R@3YXtGi=%Vj832L_AE|l>Jhy18K/an^cNHv7i*3-8d*9?#FQa8u!IUoAai-mr(&PG|ZALs2&?6hI2N]9NKK][
StateAttribute3: StateAttribute4: StateAttribute5: StateAttribute6: 0 StateAttribute7: 0 StateAttribute8: 0 StateAttribute9:
0 StateAttribute10: 0 StateAttribute11: StateAttribute12: StateAttribute13: StateAttribute14: StateAttribute14: StateAttribute16:
0 StateAttribute17: 0 StateAttribute18: 0 StateAttribute19: 0 StateAttribute20: 0 StateAttribute21: StateAttribute22: StateAttribute23:
StateAttribute24: StateAttribute25: PoisonedCount: 0 Client Access Array: Client Access Array name could not be retrieved. ExecutionId: 30334093 ExecutionStartTime:
12/23/2014 12:03:08 PM ExecutionEndTime: 12/23/2014 12:03:08 PM ResultId: 32263287 SampleValue: 0</message> <monitor>AutodiscoverProxyTestMonitor/MSExchangeAutodiscoverAppPool</monitor></eventxml></userdata></event>

Best Practice Analyzer Results: Health Report Error EDS AlertValue Unhealthy.

I ran the Microsoft Office 365 Best Practices Analyzer Beta 1.0 and I get the following error:
C:\windows\system32>Get-healthreport -rollupgroup
servername.. then I got lots of results.. I narrow it to the following!
PSComputerName          : kaneex13.kanecpas.local
RunspaceId              : 85204a86-04f3-4779-9cad-3092ebfe3435
PSShowComputerName      : False
Server                  : kaneex13.kanecpas.local
CurrentHealthSetState   : NotApplicable
Name                    : MaintenanceFailureMonitor.EDS
TargetResource          :
HealthSetName           : EDS
HealthGroupName         : ServiceComponents
AlertValue              : Unhealthy
FirstAlertObservedTime : 2/6/2015 9:12:57 AM
Description             :
IsHaImpacting           : False
RecurranceInterval      : 300
DefinitionCreatedTime   : 2/6/2015 8:58:03 AM
HealthSetDescription    :
ServerComponentName     : None
LastTransitionTime      : 2/6/2015 9:12:57 AM
LastExecutionTime       : 2/6/2015 12:38:00 PM
LastExecutionResult     : Succeeded
ResultId                : 57636932
WorkItemId              : 94
IsStale                 : False
Error                   :
Exception               :
IsNotified              : False
LastFailedProbeId       : -301690410
LastFailedProbeResultId : 351526122
ServicePriority         : 0
Identity                : EDS\MaintenanceFailureMonitor.EDS\
IsValid                 : True
ObjectState             : New
I try to fix it and this is my findings!!
https://technet.microsoft.com/en-us/library/ms.exch.scom.eds(v=exchg.150).aspx
I'm running Exchange 2013 on Server 2012

Hi,
Based on my research, it’s a known issue that there will be 1006 error in the application log after we install a new Exchange 2013 server:
http://social.technet.microsoft.com/Forums/en-US/5ab1a91a-ccd4-49fb-a451-159592fc85d4/msexchangediagnostics-error-1006-logical-to-physical-size-ratio-free-megabytes?forum=exchangesvradmin
And it can be resolved by setting the value of DriveSpaceTrigger to false:
http://windowsitpro.com/blog/case-erroneous-disk-space-checker
In your case, we can firstly try to restart the MS Exchange Diagnostics Service.
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

HubTransport and FrontendTransport marked as Unhealthy. How to diagnose and resolve?

I am trying to do an Exchange 2007 to 2013 migration. Before doing all the final repointing of DNS and proxying clients, I just want to make sure that the new Exchange 2013 is healthy. So I run a Get-HealthReport and it shows both the Online
states of HubTransport and FrontendTransport as Unhealthy.
In the event logs under Microsoft>Exchange>ManagedAvailability>Monitoring I see Error events for them about the client submission probe failed x times over 15 minutes. No connection because the target machine actively refused it 127.0.0.1:587.
There was also another one that said Unable to relay. For the Hub Transport it does not give as detailed information. It just says The HubAvailibilityProbe has failed 5 or more times in 15 minutes. Last failing server: ".
So it would sound like a connectivity problem, so with TELNET I tried to connect to port 25 and I get this:
telnet 127.0.0.1 25
421 4.3.2 Service not available
BUT if I put the hostname instead of 127.0.0.1, I get the 220 EMAIL.domain.com Microsoft ESMTP MAIL Service ready.
I tried temporarily disabling the windows firewall and its the same problem. I know SMTP is running because from another machine I can telnet to the mail server on port 25 and I get the SMTP banner.
So for me it seems like the Managed Availability is trying to use the IP address of 127.0.0.1 and that fails fundamentally for me when I try that in the command line, so no wonder why its marking the FrontendTransport as unhealthy. How can I resolve
this? I would think a resolution would be either somehow allow 127.0.0.1 access to relay which I DID put in my Frontend Transport receive connector, but it made no difference. Or the other option is somehow configure the probe to use the
hostname instead of 127.0.0.1.
As far as the HubTransport being unhealthy, I have a feeling its the same type of issue, but I am not seeing as detailed information in this path of the Event Viewer.

Bump....
No issues with mail flow but still getting this in the MOnitoring log from Managed Availability.
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: Microsoft-Exchange-ManagedAvailability
Date: 12/8/2014 11:11:29 AM
Event ID: 4
Task Category: Monitoring
Level: Error
Keywords:
User: SYSTEM
Computer: email.domain.com
Description:
The inbound proxy probe failed 3 times over 15 minutes.
Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Probe Exception: 'System.Exception: Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Failure Context: 'Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Execution Context: ''
Probe Result Name: 'OnPremisesInboundProxy'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '9/25/2014 1:27:15 PM'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-12-08T16:11:29.045528200Z" />
<EventRecordID>7358</EventRecordID>
<Correlation />
<Execution ProcessID="7604" ThreadID="1800" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>email.domain.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>FrontendTransport</HealthSet>
<Subject>The inbound proxy probe failed 3 times over 15 minutes.</Subject>
<Message>The inbound proxy probe failed 3 times over 15 minutes.
Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Probe Exception: 'System.Exception: Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Failure Context: 'Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
Execution Context: ''
Probe Result Name: 'OnPremisesInboundProxy'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '9/25/2014 1:27:15 PM'
</Message>
<Monitor>OnPremisesInboundProxyMonitor</Monitor>
</EventXML>
</UserData>
</Event>

Exchange 2013 CU2, Alert for OWA Health set unhealthy from SCOM 2012

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.

Hi,
Sorry for the late reply.
Do we have Exchange 2010 coexistence?
If it is the case, I know the following known issue:
Release Notes for Exchange 2013
http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx
Please note the "Exchange 2010 coexistence" session.
If it is not related to our problem, please check the IIS log.
If there is any detailed error code, like 401.1, 401.2, please let me know.
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

OnPremisesSmtpClientSubmissionMonitor unhealthy

Hi
I ran "get-healthreport" and got an unhealthy "Frontend Transport". I found out the problem is the monitor "OnPremisesSmtpClientSubmissionMonitor". I found this event:
The client submission probe failed 3 times over 15 minutes.
Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
Probe Exception: 'System.Exception: Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Failure Context: 'Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
Execution Context: ''
Probe Result Name: 'OnPremisesSmtpClientSubmission'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '3/13/2015 11:56:16 AM'
But I can telnet the port 487 on 127.0.0.1 and the last run seems to be fine. I have restarted the Frontend transport service with no luck. The state is still "Unhealthy".
RunspaceId : b49aab67-784f-464f-9c60-4b07fcde8f6e
Server : srvexchange01
CurrentHealthSetState : Online
Name : OnPremisesSmtpClientSubmissionMonitor
TargetResource :
HealthSetName : FrontendTransport
HealthGroupName : ServiceComponents
AlertValue : Unhealthy
FirstAlertObservedTime : 13.03.2015 12:56:16
Description :
IsHaImpacting : False
RecurranceInterval : 450
DefinitionCreatedTime : 17.03.2015 14:47:56
HealthSetDescription :
ServerComponentName : FrontendTransport
LastTransitionTime : 13.03.2015 12:56:16
LastExecutionTime : 17.03.2015 15:49:53
LastExecutionResult : Succeeded
ResultId : 1671349
WorkItemId : 70
IsStale : False
Error :
Exception :
IsNotified : False
LastFailedProbeId : 37
LastFailedProbeResultId : 835260
ServicePriority : 2
Identity : FrontendTransport\OnPremisesSmtpClientSubmissionMonitor\
IsValid : True
ObjectState : New

Hello,
Please try:
Add-GlobalMonitoringOverride -Identity "FrontendTransport\OnPremisesInboundProxy" -PropertyName Enabled -PropertyValue 0 -ApplyVersion "15.0.xxx.xx" -ItemType
Monitor
The
ApplyVersion here is your current Exchange version.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013 Managed Availability: ProcessIsolation HealthSet unhealthy.

In env with 2 CAS and 3 MB Servers, all 2013 CU3, the ProcessIsolation healthset is market as Unhealthy. Here is the result from the monitor:
< Message > Maintenance workitem "Process.Isolation.Maintenance.Workitem" (ID: 64) has failed. Health Manager has detected it is either set to run once and failed, or has been failing consistently. Maintenance workitem failure could cause
monitoring gap and should be investigated. The error message from the last result is: workitem completed with result: TimedOut ------------------------------------------------------------------------------- States of all monitors within the health set: Note:
Data may be stale....<Result from Get-HealthReport here>.........
Note: Subsequent detected alerts are suppressed until the health set is healthy again. </ Message >
Using get-serverhealth I can see that "ProcessIsolation\MaintenanceFailureMonitor.ProcessIsolation\" is Unhealthy.
I cannot find any documentation regarding this Healthset. How should I investigate this?

Hi,
Is there any related error message in the Application log?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

ServerHealth on CasServer Healthset RPS.ProxyResource MSExchangePowerShellFrontEndAppPool Status Unhealthy

Hi,
our cas-Server reports an Unhealthy Healthset:
get-healthreport -server casserver| where {$_.alertvalue -ne "healthy"} | ft -auto
Server State HealthSet AlertValue LastTransitionTime MonitorCount
casserver Online RPS.Proxy Unhealthy 28.10.2014 10:42:57 1
and
$issues = Get-HealthReport -server casserver | where {$_.alertvalue -ne "healthy"}
foreach ($line in $issues) {$line.entries | where {$_.alertvalue -ne "healthy"} | ft -auto}
Server State Name TargetResource HealthSetName AlertValue ServerComponent
casserver Online RPSProxyTestMonitor MSExchangePowerShellFrontEndAppPool RPS.Proxy Unhealthy RpsProxy
i can connect to OWA and ECP under https://localhost/owa and "https://casserver.domain.int/owa"
but i cant connect to https://localhost/powerShell/ and https://casserver.domain.int/powerShell
The Exchange Default Website and BackEnd have an SAN Cert with alle names in the cert:
CN = autodiscover.domain.int
DNS Name=autodiscover.domain.int
DNS Name=autodiscover
DNS Name=mail.domain.int
DNS Name=mail DNS Name=casserver.domain.int
DNS Name=casserver
DNS Name=mgmtcasserver.domain.int
DNS Name=cmgmtasserver
DNS Name=localhost
DNS Name=10.20.40.54
DNS Name=10.50.60.72
The PowerShell Directory Points to "D:\Exchange2013\ClientAccess\PowerShell"
Can anyone help?

Hi Joerg,
According to your description, I cannot understand what your problem is.
Could you please explain it in more detail?
Best regards,
Niko Cheng
TechNet Community Support

ActiveSyncCTPMonitor probe unhealthy, along with a few others

Exchange 2013 is up and running (still in test mode) and I can process mail with POP, IMAP, Outlook Anywhere, and activesync (with my cellphone and tablet). Event logs are pretty normal except for the ProbeResult log. I see errors in there for ActiveSync,
IMAP and POP and some others. I ran the get-serverhealth cmdlet and then followed the instructions in the knowledgebase articles to reset stuff in IIS. I am at a loss what else to do. Everything seems
to be working fine but I see those errors. (Maybe I shouldn't have looked in that log :)
Any suggestions? Thanks,
Lou

First one is typical activesync error posted frequently. Second one happens every so often, unhandled exception in the get-healthreport cmdlet:
Log Name: Microsoft-Exchange-ActiveMonitoring/ProbeResult
Source: Microsoft-Exchange-ActiveMonitoring
Date: 1/22/2015 10:44:42 PM
Event ID: 2
Task Category: Probe result
Level: Error
Keywords:
User: SYSTEM
Computer: <removed name>
Description:
Probe result (Name=ActiveSyncCTPProbe/MSExchangeSyncAppPool)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Exchange-ActiveMonitoring" Guid="{ECD64F52-A3BC-47B8-B681-A11B7A1C8770}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x800000000000000</Keywords>
<TimeCreated SystemTime="2015-01-23T03:44:42.151623700Z" />
<EventRecordID>246015</EventRecordID>
<Correlation />
<Execution ProcessID="2984" ThreadID="3064" />
<Channel>Microsoft-Exchange-ActiveMonitoring/ProbeResult</Channel>
<Computer><removed></Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<ResultId>262998</ResultId>
<ServiceName>ActiveSync</ServiceName>
<IsNotified>0</IsNotified>
<ResultName>ActiveSyncCTPProbe/MSExchangeSyncAppPool</ResultName>
<WorkItemId>117</WorkItemId>
<DeploymentId>0</DeploymentId>
<MachineName>EXCHANGE</MachineName>
<Error>Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index</Error>
<Exception>System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.Generic.List`1.get_Item(Int32 index)
at System.Linq.Enumerable.ElementAt[TSource](IEnumerable`1 source, Int32 index)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.ActiveSync.Probes.ActiveSyncCustomerTouchPointProbe.GetMonitoringAccount()
at Microsoft.Exchange.Monitoring.ActiveMonitoring.ActiveSync.Probes.ActiveSyncCustomerTouchPointProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()</Exception>
<RetryCount>0</RetryCount>
<StateAttribute1>[null]</StateAttribute1>
<StateAttribute2>[null]</StateAttribute2>
<StateAttribute3>[null]</StateAttribute3>
<StateAttribute4>[null]</StateAttribute4>
<StateAttribute5>[null]</StateAttribute5>
<StateAttribute6>0</StateAttribute6>
<StateAttribute7>0</StateAttribute7>
<StateAttribute8>0</StateAttribute8>
<StateAttribute9>0</StateAttribute9>
<StateAttribute10>0</StateAttribute10>
<StateAttribute11>[null]</StateAttribute11>
<StateAttribute12>[null]</StateAttribute12>
<StateAttribute13>[null]</StateAttribute13>
<StateAttribute14>[null]</StateAttribute14>
<StateAttribute15>[null]</StateAttribute15>
<StateAttribute16>0</StateAttribute16>
<StateAttribute17>0</StateAttribute17>
<StateAttribute18>0</StateAttribute18>
<StateAttribute19>0</StateAttribute19>
<StateAttribute20>0</StateAttribute20>
<StateAttribute21>PDWS;</StateAttribute21>
<StateAttribute22>[null]</StateAttribute22>
<StateAttribute23>[null]</StateAttribute23>
<StateAttribute24>[null]</StateAttribute24>
<StateAttribute25>[null]</StateAttribute25>
<ResultType>4</ResultType>
<ExecutionId>54042604</ExecutionId>
<ExecutionStartTime>2015-01-23T03:44:42.1516237Z</ExecutionStartTime>
<ExecutionEndTime>2015-01-23T03:44:42.1516237Z</ExecutionEndTime>
<PoisonedCount>0</PoisonedCount>
<ExtensionXml>[null]</ExtensionXml>
<SampleValue>0</SampleValue>
<ExecutionContext>[null]</ExecutionContext>
<FailureContext>[null]</FailureContext>
<FailureCategory>-1</FailureCategory>
<ScopeName>[null]</ScopeName>
<ScopeType>[null]</ScopeType>
<HealthSetName>[null]</HealthSetName>
<Data>[null]</Data>
<Version>65536</Version>
</EventXML>
</UserData>
</Event>
Log Name: MSExchange Management
Source: MSExchange CmdletLogs
Date: 1/23/2015 5:15:55 AM
Event ID: 8
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: <removed>
Description:
(PID 2984, Thread 189) Task Get-HealthReport throwing unhandled exception: System.ArgumentException: sessionState
at Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer.GetProvisioningBroker(ISessionState sessionState)
at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlersImpl(Task task)
at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task)
at Microsoft.Exchange.Configuration.Tasks.Task.<BeginProcessing>b__4()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeNonRetryableFunc(Action func, Boolean terminatePipelineIfFailed).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange CmdletLogs" />
<EventID Qualifiers="49152">8</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-01-23T10:15:55.000000000Z" />
<EventRecordID>217</EventRecordID>
<Channel>MSExchange Management</Channel>
<Computer><removed></Computer>
<Security />
</System>
<EventData>
<Data>2984</Data>
<Data>189</Data>
<Data>Get-HealthReport</Data>
<Data>Get-HealthReport</Data>
<Data>System.ArgumentException: sessionState
at Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer.GetProvisioningBroker(ISessionState sessionState)
at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlersImpl(Task task)
at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task)
at Microsoft.Exchange.Configuration.Tasks.Task.<BeginProcessing>b__4()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeNonRetryableFunc(Action func, Boolean terminatePipelineIfFailed)</Data>
</EventData>
</Event>
Lou

DAG Sporadic Entire Server DB Fail Over

Hi,
I have been having this issues for a while now, I have two physical exchange servers in a DAG, both on Exchange 2013 CU1. Randomly, every few days and various times, Server1 will fail all of it's databases over to Server2. I'll redistribute them, and again,
say Server2 will fail all databases to Server1. In short, both servers at times have failed their databases over.
I started with this: http://technet.microsoft.com/en-us/library/dd351258(v=exchg.150).aspx which led me to setup monitoring of the Microsoft-Exchange-ManagedAvailability logs. I can tell you that replication tests work fine, and the health of all the
databases are fine.
My monitoring turned up the following errors, in this example "EX0001" was the server that failed all of it's databases over to "EX0002". It seems pretty clear to me, that Exchange Managed Availability, is finding an issue with
EWS, attempting to restart the MSExchangeServicesApp pool and cannot due to "Throttling" so ti fails the DB's over, that's my best guess...the problem is I dont know how to fix this...I've run through troubleshooting EWS Healthset, nothing
really turns up... http://technet.microsoft.com/en-us/library/ms.exch.scom.ews.protocol(v=exchg.150).aspx
EX0001
1011
Microsoft-Exchange-ManagedAvailability
Recovery
Microsoft-Exchange-ManagedAvailability/RecoveryActionLogs
5/22/2014 7:06:43 AM
Warning (Info)
1520183
NT AUTHORITY\SYSTEM
RecycleApplicationPool-MSExchangeServicesAppPool-EWSSelfTestRestart: Throttling rejected the operation
EX0001
4
Microsoft-Exchange-ManagedAvailability
Monitoring
Microsoft-Exchange-ManagedAvailability/Monitoring
5/22/2014 7:17:27 AM
Error (Info)
8287
NT AUTHORITY\SYSTEM
The EWS.Protocol health set has detected a problem on EX0001 beginning at 5/22/2014 10:55:12 AM (UTC). The health manager is reporting that recycling the MSExchangeServicesAppPool
app pool has failed to restore health and it has tried to fail over active copies of local databases to a healthy server. Attempts to auto-recover from this condition have failed and requires Administrator attention. Details below: MachineName:
EX0001 ServiceName: EWS.Protocol ResultName: EWSSelfTestProbe/MSExchangeServicesAppPool Error: System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) Exception: System.Exception: System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.ThrowError(Object key, Object exceptiondata, String logDetails) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.RunEWSGenericProbe(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() ExecutionContext: EWSGenericProbeError:Exception=System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon
FailureContext: ResultType: Failed IsNotified: False DeploymentId: 0 RetryCount: 0 ExtensionXml: Version: StateAttribute1:
EWS StateAttribute2: Unknown StateAttribute3: StateAttribute4: StateAttribute5: StateAttribute6: 0 StateAttribute7: 0 StateAttribute8:
0 StateAttribute9: 0 StateAttribute10: 0 StateAttribute11: StateAttribute12: StateAttribute13: StateAttribute14: StateAttribute14:
StateAttribute16: 0 StateAttribute17: 0 StateAttribute18: 0 StateAttribute19: 0 StateAttribute20: 120011 StateAttribute21: [000.000] EWSCommon
start: 5/22/2014 11:13:13 AM [000.000] Configuring EWScommon [000.000] Probe time limit: 120000ms, HTTP timeout: 59500ms, RetryCount: 1 [000.047] using authN: CAFE
[email protected] xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt
[000.047] using HTTP request timeout: 59500 ms [000.047] action iteration 0 [000.047] starting (total time left 119954 ms) [059.568] action threw Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The operation has timed out [064.584]
action iteration 1 [064.584] starting (total time left 55416 ms) [120.011] action wait timed out [120.011] action threw System.TimeoutException: iteration 1; 55.427003 seconds elapsed StateAttribute22: StateAttribute23:
StateAttribute24: StateAttribute25: PoisonedCount: 0 ExecutionId: 32395373 ExecutionStartTime: 5/22/2014 11:13:13 AM ExecutionEndTime: 5/22/2014
11:15:13 AM ResultId: 253233015 SampleValue: 0 ------------------------------------------------------------------------------- States of all monitors within the health set: Note: Data may be stale. To get current data,
run: Get-ServerHealth -Identity 'EX0001' -HealthSet 'EWS.Protocol' State Name TargetResource HealthSet AlertValue ServerComponent ----- ---- -------------- --------- ---------- --------------- NotApplicable EWSSelfTestMonitor MSExchangeServicesAppPool EWS.Protocol
Unhealthy None NotApplicable EWSDeepTestMonitor DG01DB15 EWS.Protocol Unhealthy None NotApplicable PrivateWorkingSetWarningThresholdExc... msexchangeservicesapppool EWS.Protocol Healthy None NotApplicable ProcessProcessorTimeErrorThresholdEx... msexchangeservicesapppool
EWS.Protocol Healthy None NotApplicable ExchangeCrashEventErrorThresholdExce... msexchangeservicesapppool EWS.Protocol Healthy None States of all health sets: Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX0001' State HealthSet
AlertValue LastTransitionTime MonitorCount ----- --------- ---------- ------------------ ------------ NotApplicable Autodiscover.Protocol Healthy 3/8/2014 12:46:17 AM 4 NotApplicable ActiveSync.Protocol Healthy 3/8/2014 1:15:35 AM 7 NotApplicable ActiveSync
Healthy 3/8/2014 2:08:15 AM 3 NotApplicable EDS Healthy 5/22/2014 5:19:41 AM 13 NotApplicable ECP Healthy 3/8/2014 1:15:27 AM 3 NotApplicable EventAssistants Healthy 5/22/2014 5:48:56 AM 28 NotApplicable EWS.Protocol Unhealthy 5/22/2014 7:07:12 AM 5 NotApplicable
FIPS Healthy 5/21/2014 10:24:01 PM 18 NotApplicable AD Healthy 2/23/2014 10:42:29 PM 10 NotApplicable OWA.Protocol.Dep Healthy 5/22/2014 5:19:40 AM 1 NotApplicable Monitoring Unhealthy 5/22/2014 5:35:31 AM 9 Online HubTransport Unhealthy 5/22/2014 5:19:43
AM 138 NotApplicable DataProtection Healthy 5/22/2014 7:08:02 AM 201 NotApplicable AntiSpam Healthy 5/22/2014 5:19:40 AM 4 NotApplicable Network Healthy 5/21/2014 10:36:54 PM 1 NotApplicable OWA.Protocol Healthy 3/8/2014 1:15:34 AM 5 NotApplicable MailboxMigration
Healthy 3/8/2014 12:46:18 AM 4 NotApplicable MRS Healthy 3/8/2014 12:44:35 AM 9 NotApplicable MailboxTransport Healthy 5/22/2014 5:19:41 AM 57 NotApplicable PublicFolders Healthy 5/21/2014 10:44:15 PM 4 NotApplicable RPS Healthy 2/23/2014 11:38:33 PM 1 NotApplicable
Outlook.Protocol Healthy 4/22/2014 11:04:18 AM 3 NotApplicable UserThrottling Healthy 5/22/2014 5:51:13 AM 7 NotApplicable SiteMailbox Healthy 3/8/2014 2:10:53 AM 3 NotApplicable UM.Protocol Healthy 5/22/2014 5:19:41 AM 17 NotApplicable Store Healthy 5/22/2014
5:19:43 AM 225 NotApplicable MSExchangeCertificateDeplo... Disabled 1/1/0001 12:00:00 AM 2 NotApplicable DAL Healthy 8/2/2013 12:59:03 AM 16 NotApplicable Search Healthy 5/22/2014 5:37:18 AM 269 Online EWS.Proxy Healthy 5/5/2014 1:34:08 AM 1 Online RPS.Proxy
Healthy 5/5/2014 1:34:38 AM 13 Online OAB.Proxy Healthy 5/5/2014 1:34:37 AM 1 Online ECP.Proxy Healthy 5/5/2014 1:34:17 AM 4 Online OWA.Proxy Healthy 5/5/2014 1:34:25 AM 2 Online Outlook.Proxy Healthy 5/5/2014 1:34:08 AM 1 Online Autodiscover.Proxy Healthy
5/5/2014 1:34:08 AM 1 Online ActiveSync.Proxy Healthy 5/5/2014 1:34:35 AM 1 Online RWS.Proxy Healthy 5/5/2014 1:34:18 AM 10 NotApplicable Autodiscover Healthy 5/21/2014 10:24:01 PM 2 Online FrontendTransport Healthy 5/15/2014 12:49:31 AM 11 NotApplicable EWS
Unhealthy 5/22/2014 7:06:01 AM 2 NotApplicable OWA Healthy 2/23/2014 11:37:56 PM 1 NotApplicable Outlook Healthy 3/8/2014 12:45:14 AM 5 Online UM.CallRouter Healthy 5/22/2014 5:19:41 AM 7 NotApplicable RemoteMonitoring Healthy 8/2/2013 12:58:03 AM 1 NotApplicable
POP.Protocol Healthy 5/20/2014 9:22:12 AM 5 NotApplicable IMAP.Protocol Healthy 5/20/2014 9:22:21 AM 5 Online POP.Proxy Healthy 3/7/2014 1:31:10 PM 1 Online IMAP.Proxy Healthy 3/7/2014 1:31:10 PM 1 NotApplicable IMAP Healthy 5/20/2014 9:23:32 AM 2 NotApplicable
POP Healthy 5/20/2014 9:17:18 AM 2 NotApplicable Antimalware Healthy 5/15/2014 8:33:13 AM 8 NotApplicable FfoQuarantine Healthy 8/2/2013 12:58:20 AM 1 Online Transport Healthy 5/22/2014 5:38:00 AM 9 NotApplicable Security Healthy 3/8/2014 12:46:09 AM 3 NotApplicable
Datamining Healthy 3/8/2014 12:45:44 AM 3 NotApplicable Provisioning Healthy 3/8/2014 12:45:40 AM 3 NotApplicable ProcessIsolation Healthy 3/8/2014 12:47:05 AM 12 NotApplicable TransportSync Healthy 3/8/2014 12:45:37 AM 3 NotApplicable MessageTracing Healthy
3/8/2014 12:44:56 AM 3 NotApplicable CentralAdmin Healthy 3/8/2014 12:45:12 AM 3 NotApplicable OAB Healthy 8/2/2013 1:02:27 AM 3 NotApplicable Calendaring Healthy 8/2/2013 1:02:07 AM 3 NotApplicable PushNotifications.Protocol Healthy 2/23/2014 10:46:17 PM
3 NotApplicable Ediscovery.Protocol Healthy 5/21/2014 10:38:16 PM 1 NotApplicable HDPhoto Healthy 5/6/2014 9:36:25 AM 1 NotApplicable Clustering Healthy 3/8/2014 12:45:34 AM 4 NotApplicable DiskController Healthy 4/22/2014 2:51:30 AM 1 NotApplicable MailboxSpace
Healthy 5/22/2014 6:16:51 AM 96 NotApplicable FreeBusy Healthy 5/22/2014 5:32:54 AM 1 Note: Subsequent detected alerts are suppressed until the health set is healthy again.

Hi,
Based on the error message, throttling rejected the operation. I recommend you use the Get-ThrottlingPolicy | fl cmdlet to view EWS settings in throttling policy.
You can modify the default throttling policy and set the basic settings for EWS. Then restart the Microsoft Exchange Throttling service and recycle the MSExchangeServicesAppPool to check the result.
For more information about the EWS throttling, you can refer to the following articles.
EWS throttling in Exchange
http://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
EWS Best Practices: Understand Throttling Policies
http://blogs.msdn.com/b/mstehle/archive/2010/11/09/ews-best-practices-understand-throttling-policies.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Tuning Exchange 2013 HealthSet Monitors (example: MailboxTransport - Mapi.Submit.Monitor)

Hello everyone,
I was hoping some of you could help me out a bit with the new monitors in Exchange 2013.
Especially after updating to CU6 we are getting a lot of warnings from SCOM with different HealthSets that show as unhealthy. These are usually “OK” again when we log on to the server and run Get-ServerHealth or Get-HealthReport. The most common healthset is
Compliance, but also get warnings from MailboxTransport and ActiveSync.
If we do manage to log on before the healthset returns to healthy again, like in the example below, we can drill down a bit. We are however very unsure about what to do with this information. Perhaps we should change the threshold, but how do we find out exactly
what this monitor is reporting on? We know it has something to do with Mapi Submit, and that the threshold is 8, but not much more than that?
Get-ServerHealth SERVER | where {($_.healthsetname -eq "mailboxtransport") -and ($_.alertvalue -eq "unhealthy")} | ft name,alertvalue -auto
Name AlertValue
Mapi.Submit.Monitor Unhealthy
(Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/MonitorDefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like "Mapi.Submit.Monitor"}
auto-ns2 : http://schemas.microsoft.com/win/2004/08/events
xmlns : myNs
Id : 266
AssemblyPath : D:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Office.Datacenter.ActiveMonitoringLocal.dll
TypeName : Microsoft.Office.Datacenter.ActiveMonitoring.OverallXFailuresMonitor
Name : Mapi.Submit.Monitor
WorkItemVersion : [null]
ServiceName : MailboxTransport
DeploymentId : 0
ExecutionLocation : [null]
CreatedTime : 2014-11-20T08:51:03.5576888Z
Enabled : 1
TargetPartition : [null]
TargetGroup : [null]
TargetResource : MailboxTransport
TargetExtension : [null]
TargetVersion : [null]
RecurrenceIntervalSeconds : 0
TimeoutSeconds : 30
StartTime : 2014-11-20T08:51:03.5576888Z
UpdateTime : 2014-11-20T08:42:58.9416436Z
MaxRetryAttempts : 0
ExtensionAttributes : [null]
SampleMask : Mapi.Submit.Probe
MonitoringIntervalSeconds : 3600
MinimumErrorCount : 0
MonitoringThreshold : 8
SecondaryMonitoringThreshold : 0
MonitoringSamplesThreshold : 100
ServicePriority : 2
ServiceSeverity : 0
IsHaImpacting : 0
CreatedById : 57
InsufficientSamplesIntervalSeconds : 28800
StateAttribute1Mask : [null]
FailureCategoryMask : 0
ComponentName : ServiceComponents/MailboxTransport/High
StateTransitionsXml : <StateTransitions>
<Transition ToState="Unrecoverable" TimeoutInSeconds="0" />
</StateTransitions>
AllowCorrelationToMonitor : 0
ScenarioDescription : [null]
SourceScope : [null]
TargetScopes : [null]
HaScope : Server
Version : 65536
We have an Exchange 2007 server coexisting in the environment, but it is not in use and will be decommissioned.
ServerRole Edition AdminDisplayVersion
Mailbox, ClientAccess, HubTransport Standard Version 8.3 (Build 83.6)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)

Thanks Belinda.
We had a look in the log you mentioned, and found some events that appear to be related.
Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed.
This could indicate that the mailbox submissions are taking too long or not progressing at all.
SequenceNumber: 635515592255510017
Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635515592255510017. First Run? = False. Previous mail submission to store
was successful. Results - # of previous results: 0. Could Not Find stages that ran. Previous SendMail failure - Mail submitted to Store during the previous run never reached SendAsCheck.
This may indicate a latency from Store to Submission Service. Investigating. Found lower SA latency. Indicates an issue in Submission service.
Investigate. In SendMail - NotificationID=00000044-0000-0000-0000-0000659c9601 Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail
failure.
CheckPreviousRunMail exception details:
Current SendMail exception details:
MailWasSentInLastRun (0(no)/1(yes)): 1
CheckMailSuccess(0(no)/1(yes)): 0
SendMailSuccess(0(no)/1(yes)/2(no-noMDBs)/3(no-noActiveMDBs)/4(no-ignorableException)): 1
PreviousMailLatencies: <[email protected]>,,2014-11-20T08:37:58.817Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.811|SA=0.343|MTSSDMO=0.426|MTSSDPL=0.002|MTSSDSS=0.008|MTSSDS=0.031|MTSS=0.466;;<[email protected]>,,2014-11-20T08:32:58.772Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.702|SA=0.203|MTSSDMO=0.451|MTSSDPL=0.003|MTSSDSS=0.007|MTSSDS=0.047|MTSS=0.500;;<[email protected]>,,2014-11-20T08:27:58.664Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=1.170|SA=0.530|MTSSDMO=0.548|MTSSDPL=0.002|MTSSDSS=0.035|MTSSDS=0.078|MTSS=0.647;;
GetPreviousMailLatencyFailures:
(The following are applicable if the mail was actually sent)
MailSentAt: 20.11.2014 08:42:58
TimeInSendingToStore: 62,3989
Sent Mail Result Details:
(InternetMessageId:<[email protected]>;
ItemEntryId:0 0 0 0 2E 57 BD C1 1C 4B 5C 47 9E 54 6E B8 B2 C5 75 38 7 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 0 0 1 B 0 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 18 1A CD F1 0 0 )
Properties of Sending mail
(Subject:00000044-0000-0000-0000-0000659c9601-MapiSubmitLAMProbe;
Sender:[email protected];
MbxGuid:340b204b-c716-4dfe-bbe1-cf09b5c73934;
MdbGuid:2a6b9801-1647-4378-bc11-6ff342d22fcf;
Recipient:[email protected];
Body and MessageClass:MessageClass:IPM.Note.MapiSubmitLAMProbe;MessageBody:This is a Probe Mapi message that's Submitted from Store to Mailbox transport Submission service to Hub transport service;
DoNotDeliver, DropMessageInHub and DeleteAfterSent:DoNotDeliver:True;DropMessageInHub:True;DeleteAfterSubmit:True;)
Probe Exception: 'System.ApplicationException: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.PerformProbeFinalAction(Boolean potentialForAlertBasedOnPreviousRun, Boolean potentialForAlertBasedOnCurrentRun, Exception previousRunVerificationException,
Exception currentRunException, DateTime timeMessageSentToStore)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWorkInternal(CancellationToken cancellationToken)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Probe Result Name: 'Mapi.Submit.Probe'
Probe Result Type: 'Failed'
Monitor Total Value: '0'
Monitor Total Sample Count: '12'
Monitor Total Failed Count: '12'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '16.11.2014 21:40:10'

Mailbox Transport health state unhelathy

Hi team,
I check my Exchange 2013 Mailbox server, abd the result, Mailbox Transport health set become unhealthy
and after i check into mailbox transport detail, there is some error. here the details
[PS] C:\Windows\system32>get-healthreport -server BCEJKT-MBX2-SVR | where {$_.alertvalue -ne "healthy"} | ft -auto
Server State HealthSet AlertValue LastTransitionTime MonitorCount
NotApplicable FIPS Unhealthy 8/6/2014 3:41:14 AM 22
NotApplicable Monitoring Unhealthy 8/6/2014 3:56:32 AM 9
NotApplicable MailboxTransport Unhealthy 8/6/2014 4:11:41 AM 56
NotApplicable MSExchangeCertificateDeployment Disabled 1/1/0001 7:00:00 AM 2
Server State Name TargetResource HealthSetName AlertValue ServerComp
onent
NotApplicable Mapi.Submit.Monitor MailboxTransport MailboxTransport Unhealthy None
NotApplicable MailboxDeliveryAvail MailboxTransport Unhealthy None
abilityMonitor
NotApplicable TransportDeliveryFai MailboxTransport Disabled None
luresDeliveryStoreDr
iver560Monitor
what error means?
and, why the state "NotApplicable" ?
Is there any services trouble (disturbed)?
Please give me details :)
Thanks
Regards

Hi,
There is no official document explaining the state "NotApplicable". Search all related articles about HealthSet, the state is always NotApplicable.
From the output of running Get-HealthReport cmdlet, FIPS, Monitoring and MailboxTransport health set are unhealthy. Please use the Test-ServiceHealth cmdlet to check result.
Besides, please check the application log and system log for events related to this feature.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Health probe - not running and trying to see why?

Hi,
Im trying to fix our exchange server 2013 (patched upto and including CU8)
when I run the following command
get-healthreport -server servername | where {$_.alertvalue -ne “healthy”} | ft -auto
Server State
HealthSet
AlertValue LastTransitionTime MonitorCount
xx NotApplicable
Compliance Unhealthy 23/04/2015 14:01:26 29
xx NotApplicable
MailboxTransport Unhealthy 23/04/2015 13:21:35 25
xx NotApplicable
Outlook
Unhealthy 23/04/2015 13:57:21 3
when i run the next command to get a list of the monitors that are unhealthy
$test = get-healthreport -server servername | where {$_.alertvalue -ne “healthy”}
foreach ($line in $test) {$line.entries | where {$_.alertvalue -ne “healthy”} | ft -auto}
it shows me that the following monitor is unhealthy in the outlook healthset
Server State Name TargetResource HealthSetName AlertValue ServerComponent
xx NotApplicable OutlookRpcCtpMonitor Outlook Unhealthy None
From this I found that the probe is OutlookRpcCtpMonitor, so I then tried to invoke the probe
invoke-monitoringprobe -identity Outlook\OutlookRpcCtpProbe -server xx
that returns the following error..
WARNING: Failed to find the probe result for invoke now request id 2610659f96e64e62b4c71d1f61f65d5e and probe
workdefinition id 198.
I have restarted the server, recycled the MSExchangeSyncAppPool. Not sure what else to try so that can fix the unhealthy set within exchange.
Kind regards
Simon

Hi,
According to your post, I understand that OutlookRpcCtpMonitor is unhealthy and run “Invoke-MonitoringProbe” failed.
If I misunderstand your concern, please do not hesitate to let me know.
Please try to run Microsoft Connectivity Analyzer to test Outlook connectivity:
https://testconnectivity.microsoft.com/
Also, try to run Test-OutlookConnectivity with OutlookRpcCTPProbe to test a logon from Client Access server for the mailbox.
For your reference:
https://technet.microsoft.com/en-us/library/dd638082(v=exchg.150).aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Exchange 2013 CU3 monitoring

Hello,
I'm getting several times per day the following alert in the Event Viewer of both my Mailbox Role servers which then raise an alert in SCOM 2012:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: ManagedAvailability
Event ID: 4
Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate.
I'm not able to find information about what is being monitored and how to get rid of this events.
Any help appreciated.
Thank you in advance.
Raffaele Zamuner

Hi Amit,
here's the output from the EMS and the Event Viewer:
[PS] C:\Windows\system32>Get-ServerHealth [ServerName] | ?{$_.alertvalue -ne "Healthy" -and $_.alertvalue -ne "Disabled"}
Server State Name TargetResource
HealthSetName AlertValue ServerComp
onent
[ServerName] NotApplicable ScanTimeMeanMonitor FIPS
Unhealthy None
[ServerName] NotApplicable MaintenanceFailur... DAL
Unknown None
[ServerName] NotApplicable DatabaseLogicalPh... FINIT MailboxSpace Repairing None
[ServerName] NotApplicable DatabaseLogicalPh... MailboxSpace
Unhealthy None
[ServerName] Online Total.Shadow.Queu...
HubTransport Unhealthy HubTran...
[ServerName] NotApplicable MailboxDeliveryAv... MailboxTrans... Unhealthy
None
[ServerName] NotApplicable DatabaseLogicalPh... DB1 MailboxSpace Repairing None
[ServerName] NotApplicable DatabaseLogicalPh... MCS1 MailboxSpace Repairing None
[PS] C:\Windows\system32>get-serverhealth -Server [ServerName] -HealthSet AMScanTimeou
[PS] C:\Windows\system32>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-06-03T07:23:16.626852900Z" />
<EventRecordID>1753</EventRecordID>
<Correlation />
<Execution ProcessID="1860" ThreadID="21496" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>[ServerName].finit.local</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>FIPS</HealthSet>
<Subject>FIPS health set unhealthy (ScanTimeMeanMonitor) - High Mean Scan Time</Subject>
<Message>Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate. ------------------------------------------------------------------------------- States of all monitors within the health set: Note: Data may be stale.
To get current data, run: Get-ServerHealth -Identity '[ServerName]' -HealthSet 'FIPS' State Name TargetResource HealthSet AlertValue ServerComponent ----- ---- -------------- --------- ---------- --------------- NotApplicable ScanProcessesRunningMonitor FIPS
Healthy None NotApplicable ScanProcessBelowMinimumMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutUrgentMonitor FIPS Healthy None NotApplicable ScanRequestQueueTimeoutUrgentMonitor FIPS
Healthy None NotApplicable RecoveryQueueTimeoutUrgentMonitor FIPS Healthy None NotApplicable ScanTimeMeanMonitor FIPS Healthy None NotApplicable ScanRequestErrorRatioMonitor FIPS Healthy None NotApplicable ScanRequestErrorsMonitor FIPS Healthy None NotApplicable
TextExtractionErrorsMonitor FIPS Healthy None NotApplicable ObsoleteEngineInUseEventMonitor FIPS FIPS Healthy None NotApplicable MaintenanceFailureMonitor.FIPS FIPS Healthy None NotApplicable EngineNotEnabledForUpdatesEventMonitor FIPS FIPS Healthy None NotApplicable
EUSTerminationEventMonitor FIPS FIPS Healthy None NotApplicable EUSUnableToStartEventMonitor FIPS FIPS Healthy None NotApplicable ADFilteringSettingsWatcherStartFaile... FIPS FIPS Healthy None NotApplicable ScanningProcessRepeatedlyCrashingMon... FIPS FIPS
Healthy None NotApplicable FilteringManagementServiceDownMonitor FIPS Healthy None NotApplicable PrivateWorkingSetWarning.fms fms FIPS Healthy None NotApplicable PrivateWorkingSetError.fms fms FIPS Healthy None NotApplicable ProcessProcessorTimeWarning.fms
fms FIPS Healthy None NotApplicable ProcessProcessorTimeError.fms fms FIPS Healthy None NotApplicable ExchangeCrashEventError.fms fms FIPS Healthy None NotApplicable LongRunningWatsonWarning.fms fms FIPS Healthy None NotApplicable LongRunningWerMgrWarning.fms
fms FIPS Healthy None NotApplicable MicrosoftFailedUpdatesMonitor FIPS Healthy None NotApplicable MicrosoftEngineErrorsMonitor FIPS Healthy None NotApplicable MSClassificationEngineErrorsMonitor FIPS Healthy None States of all health sets: Note: Data may be
stale. To get current data, run: Get-HealthReport -Identity '[ServerName]' State HealthSet AlertValue LastTransitionTime MonitorCount ----- --------- ---------- ------------------ ------------ NotApplicable ActiveSync.Protocol Healthy 03/06/2014 05.04.35 9
NotApplicable Autodiscover.Protocol Healthy 03/06/2014 01.18.16 9 NotApplicable ActiveSync Healthy 03/06/2014 08.24.19 1 NotApplicable Antimalware Unhealthy 03/06/2014 09.18.14 11 NotApplicable ECP Healthy 03/06/2014 08.40.07 5 NotApplicable Ediscovery.Protocol
Healthy 03/06/2014 08.55.21 1 NotApplicable AD Healthy 03/06/2014 07.46.15 19 NotApplicable EDS Healthy 03/06/2014 08.52.30 90 NotApplicable EventAssistants Healthy 03/06/2014 09.21.03 15 NotApplicable EWS.Protocol Healthy 03/06/2014 09.15.04 11 NotApplicable
FEP Healthy 02/06/2014 09.04.40 2 NotApplicable FIPS Healthy 03/06/2014 09.15.34 28 NotApplicable Monitoring Healthy 03/06/2014 07.53.12 17 NotApplicable MailboxMigration Healthy 02/06/2014 14.03.19 3 Online UM.CallRouter Healthy 03/06/2014 04.44.11 8 NotApplicable
UM.Protocol Healthy 03/06/2014 05.05.45 22 NotApplicable OAB Healthy 03/06/2014 09.22.26 8 Online HubTransport Unhealthy 03/06/2014 09.22.35 133 NotApplicable EAS Healthy 02/05/2014 10.33.27 1 NotApplicable Autodiscover Healthy 03/06/2014 05.56.59 1 NotApplicable
DataProtection Healthy 03/06/2014 09.18.11 66 NotApplicable FreeBusy Healthy 02/05/2014 10.30.56 1 NotApplicable Clustering Healthy 03/06/2014 08.21.27 5 NotApplicable BitlockerDeployment Healthy 02/06/2014 22.00.36 1 NotApplicable ClientAccess.Proxy Healthy
02/06/2014 14.20.31 1 NotApplicable Compliance Healthy 02/05/2014 10.29.01 1 NotApplicable EWS Healthy 01/06/2014 12.57.38 1 NotApplicable FfoRws Healthy 01/06/2014 09.15.31 1 NotApplicable Places Healthy 03/06/2014 01.16.29 1 Online Transport Healthy 03/06/2014
08.23.33 10 NotApplicable RemoteMonitoring Healthy 02/06/2014 15.11.34 4 NotApplicable Search Healthy 03/06/2014 07.04.56 140 NotApplicable Inference Healthy 01/06/2014 23.57.09 1 NotApplicable OWA Healthy 03/06/2014 09.16.39 2 NotApplicable MailboxSpace Repairing
03/06/2014 09.22.02 17 NotApplicable MRS Healthy 03/06/2014 09.20.58 19 NotApplicable MessageTracing Healthy 03/06/2014 07.03.30 8 NotApplicable Network Healthy 03/06/2014 09.09.30 2 NotApplicable Calendaring Healthy 03/06/2014 09.19.16 8 NotApplicable PeopleConnect
Healthy 02/06/2014 14.10.08 1 NotApplicable IMAP Healthy 03/06/2014 08.10.29 1 NotApplicable POP Healthy 03/06/2014 05.54.04 1 NotApplicable ProcessIsolation Healthy 03/06/2014 07.39.59 22 NotApplicable Provisioning Healthy 03/06/2014 08.35.16 8 NotApplicable
Psws Healthy 03/06/2014 08.51.44 15 NotApplicable PublicFolders Healthy 03/06/2014 09.21.54 5 NotApplicable Outlook Healthy 03/06/2014 05.56.00 1 NotApplicable RPS Healthy 03/06/2014 08.22.48 1 NotApplicable RWS Healthy 03/06/2014 08.11.44 2 NotApplicable
Security Healthy 03/06/2014 08.11.33 8 NotApplicable SiteMailbox Healthy 03/06/2014 09.07.10 4 NotApplicable Store Healthy 03/06/2014 09.19.09 110 NotApplicable TransportSync Healthy 03/06/2014 08.11.56 8 NotApplicable UserThrottling Healthy 03/06/2014 09.21.49
8 NotApplicable FfoWebService Healthy 03/06/2014 07.07.43 1 NotApplicable DAL Healthy 03/06/2014 08.08.02 12 NotApplicable FfoWebstore Healthy 03/06/2014 07.07.33 1 NotApplicable AntiSpam Healthy 03/06/2014 06.02.52 8 NotApplicable OWA.Protocol.Dep Healthy
30/05/2014 17.45.35 1 NotApplicable MigrationMonitor Healthy 03/06/2014 08.33.07 3 NotApplicable MailboxTransport Unhealthy 03/06/2014 09.05.01 63 NotApplicable MSExchangeCertificateDeplo... Disabled 01/01/0001 01.00.00 2 NotApplicable OWA.Protocol Healthy
03/06/2014 07.33.09 9 NotApplicable Outlook.Protocol Healthy 02/06/2014 18.07.34 11 NotApplicable RPS.Protocol Healthy 02/05/2014 10.33.10 2 NotApplicable IMAP.Protocol Healthy 03/06/2014 07.31.55 7 NotApplicable Datamining Healthy 03/06/2014 05.06.42 7 NotApplicable
POP.Protocol Healthy 01/06/2014 19.02.12 7 Online FrontendTransport Healthy 02/06/2014 09.06.30 7 NotApplicable CentralAdmin Healthy 03/06/2014 07.37.18 7 Online ECP.Proxy Healthy 03/06/2014 06.30.43 7 Online RPS.Proxy Healthy 03/06/2014 09.22.16 28 NotApplicable
PushNotifications.Protocol Healthy 03/06/2014 08.34.46 7 Online RWS.Proxy Healthy 02/06/2014 22.55.09 7 Online Outlook.Proxy Healthy 03/06/2014 07.51.37 7 Online OutlookMapi.Proxy Healthy 03/06/2014 08.09.14 7 Note: Subsequent detected alerts are suppressed
until the health set is healthy again.</Message>
<Monitor>ScanTimeMeanMonitor</Monitor>
</EventXML>
</UserData>
</Event>
Raffaele Zamuner

Exchange 2013 and SCOM False Events

We are having many problems with the health monitoring of exchange in our SCOM 2012 environment. We have 9 exchange servers, with 3 DAGS across the 9 servers. WE are constantly getting health events in SCOM, even for monitors i've explicitly disabled. For
example, the FIPS monitor. Following this guide (http://blogs.technet.com/b/exchange/archive/2013/08/13/customizing-managed-availability.aspx) i disabled the FIPS probes/monitors all together across our entire Exchange environment, and yet in SCOM, all 9 servers
show this monitor as being unhealthy. Is my understanding on this functionality incorrect, or is it just not functioning properly?
Similarly, even when an Exchange monitor is completely healthy, it shows as unhealthy in SCOM. Right now, HubTransport shows as unhealthy in SCOM For all our Exchange servers, but when i run this command everything shows as healthy, across all servers.
Get-ServerHealth <server name> | ?{$_.HealthSetName -eq "HubTransport"}
I understand that these monitors can be unhealthy for a while and correct themselves, but shouldn't that correct them in SCOM as well? And for disabled monitors, like FIPS, they should never be unhealthy at all. So why are they showing as unhealthy in SCOM?
Am i expected to reset health in SCOM every time an unhealthy flag is thrown in Exchange?
From what i've seen there is a huge discrepancy between how SCOM works and how Exchange monitors work. They don't seem to integrate well, at all. Does anyone have any suggestions on getting Exchange 2013 monitors to work properly in SCOM? Is this my error
as a user, or is it just bad software

Hi,
I recommend you use the Get-HealthReport cmdlet to check Exchange Server health again.
What's more, please verify if the account you use has the Organization Management permission and Server Management permission. Also, you can change an account and see the result.
Moreover, please take your time to post the unhealthy information from SCOM monitor about Exchange server for my further research.
Hope my clarification is helpful.
If there is any update, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Get-healthreport unhealthy

Similar Messages

Maybe you are looking for