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

Allen,

thanks for your reply, I have run the "Test-OutlookConnectivity" cmdlet and the response is below

[PS] C:\Windows\system32>Test-OutlookConnectivity -ProbeIdentity "OutlookRpcSelfTestProbe"
WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to find the probe result for
invoke now request id becb13affecb41dbac5c9e586978a234 and probe workdefinition id 201.
Failed to find the probe result for invoke now request id becb13affecb41dbac5c9e586978a234 and probe workdefinition id
201.
    + CategoryInfo          : NotSpecified: (:) [Test-OutlookConnectivity], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.Tasks.TestOutlookConnecti
   vity
    + PSComputerName        : oakexc.oak.local

Any pointers that could help me solve it?

Thanks

Simon

Has anybody any suggestions to what I can do to find out what it wrong with the outlook health probe?

Thanks

Simon

Hi,

Please run below command to double check the state of Exchange system component: Get-ServerComponentstate -Identity servername
If the state is Inactive, please run below command to active relevant component:
Set-ServerComponentState <Identity> -Component component name -Requester HealthAPI -State Active

More details about Server Component States in Exchange 2013, please refer to:
http://blogs.technet.com/b/exchange/archive/2013/09/26/server-component-states-in-exchange-2013.aspx

Thanks

I have run the "Test-OutlookConnectivity" cmdlet and the response is below

[PS] C:\Windows\system32>Test-OutlookConnectivity -ProbeIdentity "OutlookRpcSelfTestProbe"
WARNING: An unexpected error has occurred and a Watson dump is being generated: 

Any pointers that could help me solve it?

Thanks

Simon

Hello,

I had the same issue, and resolve it with the following:

Test-OutlookConnectivity -ProbeIdentity OutlookRpcCtpProbe -MailboxId justkarl@contoso.com -RunFromServerId CAS1

My test succeeds and I still have the OutlookRpcCtpMonitor in an unhealthy state on only 1 CAS.

It would be nice if there was some information on how to get the monitors into a healthy state....

Karl