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
------ ----- ---------
---------- ------------------ ------------
xxNotApplicable Compliance Unhealthy 23/04/2015 14:01:26 29
xxNotApplicable MailboxTransport Unhealthy 23/04/2015 13:21:35 25
xxNotApplicable 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