Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Troubleshooting the Cisco TMS components
Cisco TMS Administrator Guide
Page 33 of 37
This component should have the Directory Security set to Anonymous Access.
This component can be removed if this Cisco TMS installation will not be used with Polycom
endpoints.
endpoints.
XAPSite
Handles communication between Cisco TMS and pre version 7 MGCs.
This component should have the Directory Security set to Anonymous Access.
This component can be removed if this Cisco TMS installation will not be used with a Polycom
MGC with version 6.x or older.
MGC with version 6.x or older.
TMSConferenceAPI
This component warns the old Exchange API (Cisco TMS 7 and 8) that it must be upgraded..
This component should have the Directory Security set to Anonymous Access.
This component can be removed if this Cisco TMS installation does not have an older Exchange
integration (Cisco TMS 8 or older).
integration (Cisco TMS 8 or older).
TMSAgent
Handles the proxies for Cisco TMS Agent requests.
This component should have the Directory Security set to Windows Integrated Authentication
(default), Basic Authentication or both.
(default), Basic Authentication or both.
AnalyticsExtension (if utilized)
Handles the interface between the Cisco TMS and Analytics Extension application.
The component should have the Directory Security set to Windows Integrated Authentication
(default).
(default).
Symptoms
• You cannot access the Cisco TMS page.
• The corporate directory on the Cisco endpoints does not work and statistics from Cisco
• The corporate directory on the Cisco endpoints does not work and statistics from Cisco
TelePresence System MXP endpoints are empty.
• Statistics from Polycom endpoints are empty.
How to fix
• Check that IIS is running.
• Check that you can access the default webpage
• Check that you can access the default webpage
• Check that the virtual directories above exist on the Cisco TMS server.
• Check that they are pointing to valid directories on the Cisco TMS server.
• Check that the permission settings are correct according to the list above.
• Check that the IIS allows for running .net extensions.
• Logs are found in c:\Program Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-web.txt
• Check that they are pointing to valid directories on the Cisco TMS server.
• Check that the permission settings are correct according to the list above.
• Check that the IIS allows for running .net extensions.
• Logs are found in c:\Program Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-web.txt
on the Cisco TMS server.