Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Troubleshooting the Cisco TMS components
Cisco TMS Administrator Guide
Page 32 of 37
How to fix
Check the logs for symptoms or error messages at c:\Program Files\TANDBERG\TMS\.
1. \wwwTMS\Data\Logs\tmsdebug\log-TMSServerDiagnosticsService.txt on the server.
2. Restarting the service or the Cisco TMS server will normally fix any problem with this service.
TMSAgentService
This service starts the local TMS Agent. The TMS Agent is needed for provisioning Cisco Jabber
Video for TelePresence clients from version 2.0 and newer, and E20 and EX series endpoints.
Video for TelePresence clients from version 2.0 and newer, and E20 and EX series endpoints.
Symptoms
You are unable to browse to or create and edit groups or users within Cisco TMS on page
Systems >
Provisioning > Directory.
How to fix
• Check the logs for symptoms or error messages at c:\Program
Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-tmsagent.txt on the server.
• Restarting the service or the Cisco TMS server will normally fix any problem with this service.
See the
See the
troubleshooting of the TMS Agent.
The web server
Cisco TMS uses Microsoft Internet Information Services to make Cisco TMS available as a webpage.
Since version 9.0, Cisco TMS has been developed with the Microsoft .NET platform and some extra
components are therefore required on the IIS for Cisco TMS to work properly. ASP.NET version 4.0 is
currently in use. All web-related files will be stored on the server in the location you specified during
the installation. The default location is c:\Program Files\Cisco TelePresence Management Suite\TMS\.
Since version 9.0, Cisco TMS has been developed with the Microsoft .NET platform and some extra
components are therefore required on the IIS for Cisco TMS to work properly. ASP.NET version 4.0 is
currently in use. All web-related files will be stored on the server in the location you specified during
the installation. The default location is c:\Program Files\Cisco TelePresence Management Suite\TMS\.
In the Internet Information Server Manager you will see that the installation has created five virtual
directories.
directories.
TMS
The Application that handles the Cisco TMS web interface.
This component should have the Directory Security set to Windows Integrated Authentication
(default), Basic Authentication or both.
(default), Basic Authentication or both.
tms/public
Handles Corporate Directory for Cisco endpoints.
Handles http traps from Cisco TelePresence System MXP and Cisco TelePresence MCU
systems.
systems.
The virtual directory for this component on the IIS is:
This component should have the Directory Security set to Anonymous Access.
pwx
Handles HTTP traps from Polycom systems.
Handles phonebooks for Polycom systems.