TMS website extended logging

TMS website extended logging

The TMS website offers some extended logging to help debug stubborn errors. This article details how to enable the logging and where to find the resulting log files.

Enabling logging

The TMS website extended logging can be enabled by editing the web.config file and uncommenting a few lines.
  1. Locate the TMS website root folder. By default, this is C:\inetpub\wwwroot\TMS
  2. Open the web.config file in Notepad. Depending on your level of access, you may need to open Notepad as administrator. Note that there is a folder called WebConfig with a web.config file inside it, this is not the correct file.
  3. Navigate to the end of the file
  4. There are 2 sections that are of interest - full logging and specific feature logging.
  5. Once you have made the required changes, the TMS website will automatically reset and begin logging. Other than the website taking roughly 10 - 20 seconds to load the next page, this will be transparent to end users.

Enabling full logging

  1. Remove the highlighted lines

Enabling specific feature logging

  1. Choose which feature you would like to enable logging for
  2. Uncomment the relevant section by adding a "-->" immediately before it and a "<!--" immediately after it
  3. For example, to enable Scheduled Message debugging, uncomment the tMessagingService and tMessageSchedule loggers


The log files

The TMS website will write logs to the tms.log file located in the web root folder (usually C:\inetpub\wwwroot\TMS\). Once this file becomes full, it will be renamed tms.log.1 and a new tms.log file created. Once you have 10 log files, the oldest file will be discarded to make room for further logs.

Increasing log file size and count

The TMS website will often log a large amount of information. Once the website has logged enough information to fill the maximum size and number of log files, it will simply delete the oldest log file and begin logging to a new file.

In order to log large amounts of data, you can increase both the size of each individual log file and the log file count. These settings are found in the web.config immediately prior to the settings for tuning the logging on. Please see the Enabling Logging section above for details.



Additional information

Depending on how many users your TMS website has, the log files could fill up very quickly. Several background processes (notably Scheduled Messages) will also quickly fill the log files.

The IIS Windows user must have Write access to the TMS website root folder. If it does not have write access, no log files will be produced.

    • Related Articles

    • Logging in as a Supervisor

      Before you can log in to your TMS application, you need to navigate to the correct web address in your browser. Please contact your IT department or system administrator for details. When you are connected to the correct web address, the TMS login ...
    • Logging on: the Help button

      On the TMS login page a Help option is available in the bottom right-hand corner: Clicking on Help opens support information in the same browser tab or window. For example: Forgotten password -- information on who to contact if you are having trouble ...
    • SAML Authentication in TMS 8

      What is SAML authentication? Note: This article is intended for someone familiar with the web.config file. It is best utilised by a system administrator. SAML (Security Assertion Markup Language) Single Sign-On allows users to sign in to TMS by ...
    • TMS 8 8.32.0.2 General Release Report

      We are pleased to announce the latest general release of TMS 8: version 8.32.0.2!  Please refer to the table below to view a list of the key features introduced for TMS 8. More information about the features can be found in this PDF, plus details on ...
    • Logging in and out as an Employee

      Log in Note: You will not be able to log in to TMS 8 if you have disabled cookies in your browser. To learn how to enable cookies in your browser, please refer your browser's help section. Before you can log in to your TMS application, you need to ...