You notice that there is an alert in the Operations Console regarding ‘PSTN Peer To Peer Call Synthetic Transaction failed’. You start investigating the situation, but dont know where to look. You also have a few open calls\tickets about Lync Quality Degredation for calls in a specific region. You think that Operations Manager should be monitoring for Quality problems, but also notice this error on the Lync Monitoring Server Operations Manager Log ‘Index was outside the bounds of the array’.
What does this mean:
This could mean several things such as:
- Network Performance problems between Lync Edge and Branch Servers and the Lync Monitoring Server
- There is no test account user setup for this synthetic transaction
- This may be ignored until the synthetic trasaction runs again
- A new test account should be created per this article here:
PSTN Peer To Peer Call Synthetic Transaction failed.
The following error message was returned by the Synthetic Transaction test commandlet: Index was outside the bounds of the array..
-Script Name: Lync Server MP Synthetic Transaction Execution
-Run as account: nt authority\network service
-Execution Policy: Bypass
Lync Server Module is added
Executing ‘Test-CSPstnPeerToPeerCall’ synthetic transaction.
Test-CSPstnPeerToPeerCall synthetic transaction execution completed for server.domain.com
TargetFqdn : server.domain.com
Result : Failure
Latency : 00:00:00.2901838
Error : Index was outside the bounds of the array.
- Log Name: Operations Manager
- Source: Health Service Script
- Event ID: 224
- Task Category: None
- Level: Information
- Keywords: Classic
This monitor represents the availability of PSTN Connectivity as monitored by Synthetic Transactions.
Cmdlet Executed: Test-CSPstnPeerToPeerCall
For more information on this cmdlet, open a Microsoft Lync Server 2010 Management Shell window and type:
Get-help Test-CSPstnPeerToPeerCall -detailed
To configure users for Synthetic Transactions to execute periodically please use the New-CSHealthMonitoringConfiguration cmdlet.
The following are possible causes for this failure:
• Configuration errors
• Server/Component is down for maintenance.
• Network/connectivity issues between Watcher node (where the ST executes) and the Front-end Pool.
• Component specific errors.
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
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 Task LS Start Pool maintenance 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.
Component specific errors: Look at Alert Context tab for more details on the component specific error. The specific Front-end server (within the load-balanced Front-end Pool) that responded to this execution of the synthetic transaction is listed in the Alert Context along with the Exception Message associated with the failure.