TM1 provides a log of every action that occurs within TM1.
To investigate any issues within TM1, the ‘TM1Server’ Log is a good place to start investigating.
Locating the Log can be done 1 of 2 ways.
RDP onto the TM1 server.
Use your Welcome Kit pack and RDP onto the Planning Analytics server.
- On the ‘Data’ share directory, navigate to the ‘TM1DBs’ location – > (Database folder) -> ‘Logs’ directory.
Within the Logs directory you should find the file named ‘tm1server.log’
Downloading via PA.
- Log into your Planning Analytics site.
- Click on the ‘Administration’ Tile (only available to Administrators)
- Select the appropriate Database on the Left-Hand Side and select ‘Download Logs’ under the ‘Details’ Tab on the Right hand Side view. You will now be presented with a view of all the available logs to download.
Larger log files may not open in standard text editors such as Notepad.
If this is the case, a text editor that can open large text files (such as ‘Large Text Viewer’) will need to be accessed. (Note: Large text files usually denote something irregular is happening within the environment which needs to be investigated).
Once opened navigate to the time of the issue and look for any error messages.
If the error was at a particular date and time use the ‘Find’ option (Edit–> Find… or Ctrl+F) and search for the date in the YYYY-MM-DD format.
If there were any specific issues with any process that were run recently, they themselves produce their own logs, titled; ‘TM1ProcessError<DateandTime><NameofProcess>.log
Message Field |
Description |
---|---|
Thread ID | ID number of the thread in the TM1 server that generated the logging event.
Example: |
Message Level | Severity level of the message being reported: DEBUG, INFO, WARN, ERROR, or FATAL. |
Date and Time | Date and time the message was logged, based on the TimeZone parameter setting in the logging properties file. Data and time can be recorded as either GMT or Local. For more details, see Configuring logging parameters in tm1s-log.properties.
Reported in the format: yyyy-mm-dd hh:mm.ss,milliseconds Example: |
TM1 Logger Name | Name of the TM1 sub-component that generated the message or activity.
Example:
|
Message Text | Pre-defined text message that describes the error or activity being reported. |