Tenant Powershell Synthetic Transaction Internal Health Monitor

  • ID:  Microsoft.LS.2015.Monitoring.UnitMonitor.SyntheticTransaction.TenantPowershell.Internal
  • Description:  Tenant Powershell Synthetic Transaction Internal Health
  • Target:  Tenant Powershell Watcher
  • Enabled:  Yes

Operational States

Name State Description
Tenant Powershell Synthetic Transaction Internal Health - SuccessState Success  
Tenant Powershell Synthetic Transaction Internal Health - ErrorState Error  

Alert Details

Monitor State Message Priority Severity Auto Resolution
Tenant Powershell Synthetic Transaction Internal Health - ErrorState (Error) [Skype] Tenant Powershell Synthetic Transaction Internal Error Occurred. High Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This monitor represents internal health state of synthetic transactions that monitor User Unified Contact Store. If this monitor is unhealthy, then it means that Synthetic transactions are unable to monitor User Unified Contact Store.

Cmdlet Executed: Test-CSTenantPowershell

For more information on this cmdlet, open a Skype for Business Server 2015 Management Shell window and type:

Get-help Test-CSTenantPowershell -detailed

Causes

The following are possible causes for this failure:

  • Watcher Node Configuration issues

  • Server/Component is down for maintenance.

  • Network/connectivity issues between Watcher node (where the ST executes) and the Front-end Pool.

  • SCOM maintenance

Resolutions

Configuration errors: Most common issues are: Test user password is invalid or expired, Test users have not been configured correctly for this Pool. Please refer Synthetic Transaction Internal Alerts View for more details. To fix this problem, check if test users are assigned correctly for the pool being monitored, using the New-CSwatcherNodeConfiguration cmdlet. Also ensure that these test users are correctly provisioned and enabled for services.

Server/Component is down for Maintenance: Please ensure that you put Synthetic Transactions in maintenance mode before performing server/pool maintenance. To do this, use the Start Pool maintenance task in the Pools view.

Network/Connectivity issues: Look at Alert Context tab for more details on the exact connectivity error such as DNS resolution errors or Connection Timeout. You can also get more details on Connectivity errors by looking at Port Check Alerts view.

SCOM maintenance: Ensure that SCOM agent on the Synthetic transaction watcher node is healthy and heartbeating correctly.

External References
This monitor does not contain any external references.

See Also for Lync Server 2015 Monitoring Management Pack


Downloads for Lync Server 2015 Monitoring Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED