Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
at Tandberg.TMS.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
The first log entry is from a log-web file. It is logged as a WARN (warning), and shows that a user tried to access a page
they do not have access to. The attempt was denied by the Access Control List mechanism of Cisco TMS, and a cor-
responding log entry was created. In general, a WARN log entry is not critical and indicates no loss of data or func-
tionality.
they do not have access to. The attempt was denied by the Access Control List mechanism of Cisco TMS, and a cor-
responding log entry was created. In general, a WARN log entry is not critical and indicates no loss of data or func-
tionality.
The second log entry is from a log-web-external file. It is logged as an ERROR, and a full stack trace is displayed. In gen-
eral, an ERROR followed by a stack trace indicates that data or functionality has been lost. In this specific case, the root
cause of the ERROR is that a Cisco TMSBA client tried to create a new booking, but had syntactical errors in the con-
ference object it provided. Cisco TMS then discards the booking and logs an ERROR, and unless the client re-tried the
save operation using a valid conference object, the conference is lost.
eral, an ERROR followed by a stack trace indicates that data or functionality has been lost. In this specific case, the root
cause of the ERROR is that a Cisco TMSBA client tried to create a new booking, but had syntactical errors in the con-
ference object it provided. Cisco TMS then discards the booking and logs an ERROR, and unless the client re-tried the
save operation using a valid conference object, the conference is lost.
IIS Logs
Cisco TMS uses Windows Server’s Internet Information Services (IIS) as its web server. The IIS logs could be useful for
troubleshooting certain kinds of Cisco TMS problems, for example:
troubleshooting certain kinds of Cisco TMS problems, for example:
■
CDR data is missing.
■
Intermittent phone book problems.
■
The Cisco TMS web interface loads very slowly.
In default IIS installations, the logs are found in the C:\inetpub\logs\LogFiles folder. When correlating IIS log entries with
Cisco TMS log entries, note that IIS log entries are in UTC.
Cisco TMS log entries, note that IIS log entries are in UTC.
For assistance on configuring the IIS logs, see the following Microsoft TechNet article:
Purging IIS Logs
Note that IIS logs are not part of the Cisco TMS purge log plan. We recommend setting up your own purge plan or manu-
ally removing these logs at regular intervals.
ally removing these logs at regular intervals.
Website Scenarios
This section describes troubleshooting scenarios involving Cisco TMS as a website.
Cisco TMS does not Load
In the event of Cisco TMS not loading, the problem might be network, web server, or database related. Troubleshooting
steps for possible web server and database issues are included below.
steps for possible web server and database issues are included below.
Basic Steps
Web Server
■
Verify that IIS is running.
■
Check whether you can access the default webpage http://<tms_server_name>.
■
See the logs in c:\Program Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-web.txt.
271
Cisco TelePresence Management Suite Administrator Guide
Troubleshooting