Troubleshooting the Cisco TMS components
Cisco TMS Administration Guide
Page 33 of 37
How to fix
•
Check that IIS is running.
•
Check that you can access the default webpage
http://TMSServerName
.
•
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
on the Cisco TMS server.
Java Applet – Monitoring
What it does
The Sun Java applet version is used for displaying dynamic information in Conference Control
Center, Graphical Monitor and Map Monitor. The Java applet adds functionality related to graphics,
clicking, right-clicking and drag-and-drop actions.
Symptoms
•
When entering the Conference Control Center, Graphical Monitor or Map Monitor, you are
prompted for a username and password.
•
The applet does not load, and there is no Java (coffee cup) icon in the notification area.
•
The applet does not load, but Java is installed.
•
The applet loads very slowly.
•
Conference snapshots are not displayed on some clients.
How to fix
Authentication
The Java Applet will require the users to authenticate themselves if the Cisco TMS server is not part of
the domain (or a trusted domain) the user is logged into. The solution is to make the Cisco TMS server
part of the domain, or insert the username and password when prompted for each session.
Java installation
The Java virtual machine is not installed on the machine, and the client PC does not have direct
access to the Internet to download it automatically. To retrieve:
Install Java from the Cisco TMS CD.
Go to
http://www.java.com/
to download and install Java.
Proxy issues
A proxy server might be preventing the Java applet from retrieving the necessary data from the Cisco
TMS server. To open the Java console, right-click the Java icon in the notification area and select
Open Console. Error messages stating Unknown source will be displayed. To solve this problem, try
one or more of the points below:
If using the Cisco TMS server’s IP address when accessing Cisco TMS, try again with the Cisco
TMS server’s host name.
Configure the Java client through the Java Control Panel to use Direct Connection rather than
using the browser’s proxy settings.
The proxy server may have to be configured to allow this kind of traffic from the Cisco TMS server
to the clients.