Invoke-MonitoringProbe warning with no results

Question

Running on:
Windows Server 2012
Exchange Server 2013 Cumulative Update 3 (CU3)      15.0.775.38
Problem:
When running command below warning is generated:
Invoke-MonitoringProbe -Identity:"ActiveSync\ActiveSyncCTPProbe" -Server:XXXXXX | fl
WARNING: Failed to find the probe result for invoke now request id bd8d6bf84e5f4189a3209536a039a487 and probe
workdefinition id 549.
No other output is generated, this happens on all the 4 servers we manage.
Additional information running Invoke-MonitoringProbe -Verbose:
[PS] C:\Windows\system32>Invoke-MonitoringProbe -Identity:"ActiveSync\ActiveSyncCTPProbe" -Server:XXXXX001 -Verbose
VERBOSE: [13:35:01.814 GMT] Invoke-MonitoringProbe : Runspace context: Executing user:
DOMAIN.com/Admin/admminuser01, Executing user organization: , Current organization: ,
RBAC-enabled: Enabled.
VERBOSE: [13:35:01.845 GMT] Invoke-MonitoringProbe : Active Directory session settings for 'Invoke-MonitoringProbe'
are: View Entire Forest: 'False', Default Scope: 'DOMAIN.com', Configuration Domain Controller:
'DC001.DOMAIN.com', Preferred Global Catalog: 'DC001.DOMAIN.com',
Preferred Domain Controllers: '{ DC001.DOMAIN.com }'
VERBOSE: [13:35:01.845 GMT] Invoke-MonitoringProbe : Beginning processing Invoke-MonitoringProbe
VERBOSE: [13:35:01.845 GMT] Invoke-MonitoringProbe : Instantiating handler with index 0 for cmdlet extension agent
"Admin Audit Log Agent".
VERBOSE: [13:35:01.860 GMT] Invoke-MonitoringProbe : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
Scope(s): {}, Exclusive Configuration Scope(s): {} }
VERBOSE: [13:35:01.860 GMT] Invoke-MonitoringProbe : Resolved current organization: .
WARNING: Failed to find the probe result for invoke now request id 556ce2e564c540418d51c956d259032a and probe
workdefinition id 580.
VERBOSE: [13:36:50.179 GMT] Invoke-MonitoringProbe : Admin Audit Log: Entered Handler:OnComplete.
VERBOSE: [13:36:50.179 GMT] Invoke-MonitoringProbe : Ending processing Invoke-MonitoringProbe

Answer 1

Hi,
I recommend you refer to the following article to troubleshoot the issue:
Troubleshooting ActiveSync Health Set
ActiveSyncCTPMonitor Recovery Actions
This monitor alert is typically issued on CA servers (CAS).
Start IIS Manager, and then connect to the server that is reporting the issue. Click
Application Pools, and then recycle the ActiveSync application pool that is named
MSExchangeSyncAppPool.
Rerun the associated probe as shown in step 2c in the
Verifying the issue section.
If the issue still exists, recycle the entire IIS service by using the IISReset utility.
Rerun the associated probe as shown in step 2c in the
Verifying the issue section.
If the issue persists, you must verify the health status on the corresponding Mailbox server. The name of the Mailbox server is the
_Mbx: value that’s given in the error message.
Run the following command for the appropriate Mailbox server. For example, run the following command a Mailbox server that’s named mailbox1.contoso.com:
Get-ServerHealth mailbox1.contoso.com | ?{$_.HealtSetName -like "ActiveSync*"}
If any of the monitors that are listed in the command output are reported to be unhealthy, you must address those monitors first. To do this, follow the troubleshooting steps that are outlined in the
ActiveSyncDeepTestMonitor and ActiveSyncSelfTestMonitor Recovery Actions section.
If all monitors on the Mailbox server are healthy, restart the CAS.
After the server restarts, rerun the associated probe as shown in step 2c in the
Verifying the issue section.
If the probe continues to fail, you may need further assistance to resolve this issue. Contact a Microsoft Support professional to resolve this issue. To contact a Microsoft Support professional, visit the
Exchange Server Solutions Center. In the navigation pane, click
Support options and resources and use one of the options listed under
Get technical support to contact a Microsoft Support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.
Hope this helps!
Thanks,
Niko Cheng
TechNet Community Support