TM1 provides a log of every action that occurs within TM1.
To investigate any issue within TM1 the ‘TM1Server’ Log is a good place to start investigating.
1. Locate the Log.
On the TM1 server, navigate to the TM1DBs location – > Client area -> ‘Logs’ directory.
2. Within the Logs directory you should find a txt file named ‘tm1server.txt’
3. Open the file in any Text editor tool. Larger text files may not open in standard text editors such as Notepad so a text editor that can open Large Text file (such as ‘Large Text Viewer’) may need to be downloaded and installed. (Note: Large text files usually mean that there are error’s happening on the server which need to be investigated)
4. Once open navigate to the time of the issue and look for any error messages.
5. 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. This is also a good way to identify any TM1 Processes that were ran on that day.
Breakdown of the log file.
|Thread ID||ID number of the thread in the TM1 server that generated the logging event.
|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
|TM1 Logger Name||Name of the TM1 sub-component that generated the message or activity.
|Message Text||Pre-defined text message that describes the error or activity being reported.|