Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Troubleshooting the Cisco TMS components
Cisco TMS Administration Guide
Page 27 of 37
Troubleshooting the Cisco TMS components
This chapter addresses the different components that Cisco TMS consists of: the five services that are
to be running at all times, the Java applet needed to show the monitoring pages, the web server
needed to display Cisco TMS as web-pages and the database were all information is stored.
to be running at all times, the Java applet needed to show the monitoring pages, the web server
needed to display Cisco TMS as web-pages and the database were all information is stored.
Phonebook (Corporate Directory) errors
You can get the following errors on the endpoint if corporate directory is not working properly:
Message
Explanation or suggested solution
Request timed out, no
response
response
The Cisco TMS server is busy, try again.
Warning: directory data not
retrieved: 404
retrieved: 404
The endpoint is configured with the IP address of a different web
server than the Cisco TMS server.
server than the Cisco TMS server.
The corporate directory path on the endpoint is wrong.
Warning: directory data not
retrieved: 401
retrieved: 401
The “Public” virtual directory on the Cisco TMS server is not
configured to allow Anonymous Access.
configured to allow Anonymous Access.
The most common problem here is that anonymous access is set,
but the account used has been overwritten by a group policy. The
default IUSR user is a part of the guest account, and typically
group policies disable this account.
but the account used has been overwritten by a group policy. The
default IUSR user is a part of the guest account, and typically
group policies disable this account.
TMS: No phonebook(s) set on
this system
this system
No phonebook(s) set on this system in Cisco TMS. Configure the
endpoint to subscribe to phonebooks in Cisco TMS.
endpoint to subscribe to phonebooks in Cisco TMS.
Using NAT on the endpoint can lead to Cisco TMS not
recognizing the system and will not allow it to retrieve any phone
books.
recognizing the system and will not allow it to retrieve any phone
books.
Request timed out, no
response
response
The endpoint is configured with the IP address of a non existing web
server.
server.
No contact with server
The IIS is restarting or in a state where corrupted messages are
received.
received.
TMSDatabaseScannerService
The TMSDatabaseScannerService checks the status and configuration of existing systems. The
scanner will check:
scanner will check:
The connection status
The call status
The system configuration
If a system is unavailable, the service will get that status until the next scan, or until the endpoint
sends a trap to Cisco TMS.
sends a trap to Cisco TMS.
Note: The scanner pauses for 15 min after scan has finished.
The scanner process is a moderately CPU-intensive process for the server, and should be tuned
according to the need for updated system information in Cisco TMS. To scan one system takes from
according to the need for updated system information in Cisco TMS. To scan one system takes from