Cisco Cisco TelePresence Management Suite (TMS) Version 15
3.
If the circle is still red, check the log. If the tmsprovisioningextension.log file contains the following line:
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
a.
Place your certificate file somewhere on the Cisco TMS server.
b.
Update the JRE keystore from JRE_HOME\bin on the server using the following command:
keytool -import -alias myprivateroot -keystore ..\lib\security\cacerts -file c:\hello.cer
c.
Enter the password for the keystore when prompted. The default password is changeit.
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 Users page. No alarms will be raised in the diagnostics, but red indicators will show that the services are
not functioning.
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.
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.
See
.
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.
tmsprovisioningextension.txt log as indicated below, you are most likely running an unsupported version of Java.
To address the issue:
1.
Stop the Provisioning Extension Windows service.
2.
Uninstall unsupported Java version.
3.
Install Java 7 update 51 (32-bit or 64-bit).
If changing from a 32-bit to a 64-bit version of Java, you must also re-install Cisco TMSPE.
4.
Restart the Windows service.
Log Excerpts
Look for messages like these in the log:
2012-10-25 15:02:24,951 [common] [JettyThread-24] ERROR U:administrator c.c.ts.mgmt.lib.api.i18n.Localizer - key Lock prevents
new connection, parallell connections not supported due to underlying os operations. is not localized
new connection, parallell connections not supported due to underlying os operations. is not localized
2012-10-25 15:02:24,951 [common] [JettyThread-24] ERROR U:administrator c.c.t.m.l.a.i18n.ExceptionLocalizer - Key not localized:
com.cisco.ts.mgmt.ur.service.userimport.settings.UserImportCommunicationException
com.cisco.ts.mgmt.ur.service.userimport.settings.UserImportCommunicationException: null
com.cisco.ts.mgmt.ur.service.userimport.settings.UserImportCommunicationException
com.cisco.ts.mgmt.ur.service.userimport.settings.UserImportCommunicationException: null
Also look for messages containing the following or similar statements:
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_34]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.6.0_34]
87
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide