Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Warning: directory
data not retrieved:
401
data not retrieved:
401
■
The "Public" virtual directory on the Cisco TMS server is not configured to allow
Anonymous Access.
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.
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.
Cisco TMS: No
phonebook(s) set
on this system
phonebook(s) set
on this system
■
No phonebook(s) set on this system in Cisco TMS. Configure the endpoint to subscribe
to phonebooks in Cisco TMS.
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.
not allow it to retrieve any phone books.
Request timed
out, no response
out, no response
The endpoint is configured with the IP address of a non existing web server.
No contact with
server
server
The IIS is restarting or in a state where corrupted messages are received.
Table 177 Possible errors displayed on endpoint due to problems with corporate directory (continued)
Polycom Endpoints do not Get Phone Books
If Polycom endpoints are not receiving phone book data, try the steps below.
Basic Steps
■
pages for detail on phone books failing.
■
Check the logs for symptoms or error messages at C:\Program
Files\TANDBERG\TMS\data\Logs\TMSDebug\log-plcmdir.txt on the server.
Files\TANDBERG\TMS\data\Logs\TMSDebug\log-plcmdir.txt on the server.
■
Restart TMSPLCMDirectoryService. For more information about this Windows service, see
■
Reporting Scenarios
This section covers troubleshooting scenarios related to Cisco TMS reporting functionality.
Bridge Utilization Report
Data Inconsistencies
Past Data Inconsistencies
A bridge that was replaced with a bridge of a different capacity, or reconfigured in the past, for example from HD to
Full HD, will lead to inaccurate past data and could lead to more than 100% usage being reported.
Full HD, will lead to inaccurate past data and could lead to more than 100% usage being reported.
Purging bridges does not delete their historical Bridge Utilization data. The same applies when transitioning to a
TelePresence Conductor-managed bridge.
TelePresence Conductor-managed bridge.
If the ETL job fails, a TMS ticket will be generated: check the ETL log that is available in the Download Diagnostic
Files zip in TMS Server Maintenance.
Files zip in TMS Server Maintenance.
281
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting