Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
8. Save and close the file.
l
For all logs related to services, you must restart the relevant Windows service for the change to take
effect.
effect.
l
For all IIS-based logs, the new log level takes effect immediately.
We strongly recommend reverting the log level back to its initial value after debugging, as increasing the log
level significantly increases the size of the log.
level significantly increases the size of the log.
The steps to revert are the same as above.
Reading the logs
The Cisco TMS version and the user account the component uses are logged every time the component
starts.
starts.
Example log entries:
2013-06-19 20:14:29,108 [6] WARN Tandberg.TMS.Framework.AccessControl.AclService - Acces
s denied to: SystemRead
2013-06-20 14:53:04,503 [75] ERROR ASP.global_asax - System.Web.Services.Protocols.SoapEx
ception: Unspecified Error
at Tandberg.TMS.External.SoapExceptionThrower.Throw(ExceptionContext exceptionContext)
at Tandberg.TMS.External.SoapExceptionThrower.Throw(Exception e, String actor)
at Tandberg.TMS.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutio
nStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchron
ously)
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 corresponding log entry was created. In general, a WARN log entry is not critical and
indicates no loss of data or functionality.
access a page they do not have access to. The attempt was denied by the Access Control List mechanism
of Cisco TMS, and a corresponding log entry was created. In general, a WARN log entry is not critical and
indicates no loss of data or functionality.
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 general, 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 conference 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.
displayed. In general, 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 conference 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:
be useful for troubleshooting certain kinds of Cisco TMS problems, for example:
n
CDR data is missing.
n
Intermittent phone book problems.
n
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.
log entries with Cisco TMS log entries, note that IIS log entries are in UTC.
Cisco TelePresence Management Suite Administrator Guide (14.5)
Page 318 of 340
Troubleshooting
Using the logs