Adding Vcs To Tms Fails; Error Message Received When Enabling Provisioning - Cisco TELEPRESENCE MANAGEMENT SUITE PROVISIONING - TROUBLESHOOTING GUIDE 13.0 Troubleshooting Manual

the following error message appears: "The Provisioning Directory is not running or is still initializing. If
the TMS Server or TMSAgentService were just restarted, please wait for the Directory to finish
initializing. If the Directory does not load after a few minutes, log on to the server and open Control
Panel, Administrative Tools, Services and restart the TMSAgentService.
and/or starting the TMSAgentService fails
Follow this procedure:
1. Check the file log-tmsagentservice.txt for these lines:
10:05:39,297 [4] WARN
Service startup...
10:05:39,313 [4] WARN
Starting TMS agent...
10:05:39,545 [4] WARN
Start script execution failed. Exit Code: 1 Output: Starting Argon
Expecting java located at: D:\Program Files\TANDBERG\TMS\Provisioning\jre
Expecting opends located at: D:\Program
Files\TANDBERG\TMS\Provisioning\OpenDs-2.0
Error:
This confirms that the problem is caused by jar files not being copied into the ... /provisioning/
... folders on the TMS server.
2. Check the log-TMSAgent-console.txt file for a NoClassDefFoundException. Details will differ
based on which specific jar files are missing.
3. If both criteria above are met, solve the issue by uninstalling Cisco TMS (the application only, leaving
the databases untouched) and reinstalling it.

Adding VCS to TMS fails

If you are having problems adding Cisco VCS to Cisco TMS, check the following:
Is SNMP enabled on VCS? Go to Administrative Tools > TMS Agent Diagnostics and run
Provisioning Diagnostic Tool test SNMP to verify that SNMP is being used on the Cisco VCS.
Is the SNMP community name being used in the VCS found in list of 'SNMP Community Names' on
the Cisco TMS on page: Administrative Tools > Configuration > Network Settings? Note that
SNMP community names are case sensitive.
Is the management address on the Cisco VCS the IP address of the Cisco TMS?
Utilise Cisco TMS Tools found on the server under Start > Programs > Tandberg to check and verify
SNMP connectivity to the Cisco VCS. In Cisco TMS Tools, select Utilities > Check SNMP
Ensure that SNMP is not being blocked on the network, that is UDP port 161 (both directions)

Error message received when enabling provisioning

If, when creating a new cluster in TMS and selecting Enable Provisioning, the provisioning fails with the
following error message: Verify that the tmsprovisioningservice is running ... check the following:
Are you running Cisco TMS version 12.5 or later?
Are you running Cisco VCS version X5.0 or later?
Was the Cisco TMS upgraded prior to the Cisco VCS?
Have the time settings on Cisco TMS and Cisco VCS are synchronized, preferably using an NTP
server?
Cisco TMS Provisioning Administrator Guide
TMSAgentWindowsService.TMSAgentWindowsService -
TMSAgentWindowsService.TMSAgentWindowsService -
TMSAgentWindowsService.TMSAgentWindowsService -
The Cisco TMS Provisioning Directory backend
Page 7 of 16