Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Troubleshooting
Cisco TMSPE Provisioning Deployment Guide
Page 75 of 88
Cisco VCS will now resume provisioning with Cisco TMS Agent Legacy, but no replication will occur
between Cisco VCS or Cisco TMS. This will allow troubleshooting Cisco TMSPE while provisioning
continues. Do not leave Cisco TMS and Cisco VCS with different provisioning modes for a long period of
time, as this will cause information to become out of sync.
between Cisco VCS or Cisco TMS. This will allow troubleshooting Cisco TMSPE while provisioning
continues. Do not leave Cisco TMS and Cisco VCS with different provisioning modes for a long period of
time, as this will cause information to become out of sync.
To revert Cisco TMS to Cisco TMS Agent Legacy:
1. Go to
Administrative Tools > Configurations > General Settings
.
2. Change Provisioning Mode to TMS Agent Legacy and click Save. You have now reverted the process
3. Go to the
Services
on the Windows server and restart the TMSAgentservice.
4. In
Systems > Navigator
, navigate to the Cisco VCS and select it.
5. Go to the
TMS Agent
tab, or to the
Clustering
tab if in a cluster.
6. Check Enable TMS Agent Data Replication or Enable TMS Agent Data Replication for All Cluster
7. Go to
Administrative Tools > Activity Status
and verify that replication is re-enabled.
Note that when going back to Cisco TMSPE after having reverted to Cisco TMS Agent Legacy, you must
restart the Windows service, see
restart the Windows service, see
.
Provisioning problem scenarios
Database connection failure
When Cisco TMSPE fails to connect to the database, an error message will appear in the lower right corner
when accessing the
when accessing the
Users
page. No alarms will be raised in the diagnostics, but red indicators will show that
the services are not functioning.
"The specified network name is no longer available"
If Cisco TMS is set up with Microsoft SQL Server Data Engine using the Named Pipe protocol and
connections to the database start failing with the error message "The specified network name is no longer
available", the required hotfixes for Windows Server have not been applied.
connections to the database start failing with the error message "The specified network name is no longer
available", the required hotfixes for Windows Server have not been applied.
AD import with Kerberos fails
If you have configured a user import from Active Directory with Kerberos authentication and it fails with an
error in the tmsprovisioningextension.txt log as indicated below, you are most likely running an
unsupported version of Java.
error in the tmsprovisioningextension.txt log as indicated below, you are most likely running an
unsupported version of Java.
To address the issue:
1. Uninstall Java 6 update 34.
2. Install a supported version; Java 6 (32-bit) updates 4-33 are supported.
Log excerpts
Look for messages like these in the log: