Log files about the operation of Tekla Structures

Tekla Structures writes information about the operation of Tekla Structures to log files when you perform some actions, such as numbering a model or saving a model.


File	Description
analysis.log	Tekla Structures stores information in this file when you run the analysis. The file also contains information about the errors that occurred during load distribution. This log file is saved in the current model folder.
check_database.log	Tekla Structures stores information in this file when you run the Repair command in File menu > Diagnose & repair > Model. This log file is saved in the current model folder.
ClashCheck.log	Contains clashes found in the most recent clash check. This log file is saved in the current model folder.
ClientLog_cat.txt ClientLog_dog.txt	The client log files contain diagnostic information and error messages about the Tekla Model Sharing sharing service, such as connecting to the sharing service or the status of the sharing service. The client log files are saved in the \Users\<user>\AppData\Local\Tekla DataSharing folder by default. There are two client log files with a maximum size of 1 megabyte each, so that the information does not use too much disk space. When the maximum file size is reached in one file, log writing changes to the other file. Each time that the active client log file changes, any information previously saved in the current log file is cleared before any new log information is written to the log file.
ComponentCatalog_<user>.log	Contains troubleshooting information related to the Applications & components catalog and any errors that have occurred in the Applications & components catalog. For example, errors in catalog definition files are stored in the ComponentCatalog_<user>.log file. This log file is saved in the \logs folder under the current model folder. A limited number of older log messages related to the Applications & components catalog are archived and saved in the ComponentCatalog_<user>.bak.log file. This file contains approximately 1024 KB of data.
conflict.log	Contains conflicts that have occurred when more than a one user has modified an object in multi-user mode. This log file is saved in the current model folder.
DocumentManager_<user>.log	Contains troubleshooting information related to the Document manager, and any errors that have occurred in the Document manager. This log file is saved in the \logs folder under the current model folder. A limited number of older log messages related to the Document manager are archived and saved in the DocumentManager_<user>.bak.log file. This file contains approximately 256 KB of data.
DPMPrinter_<user>.log	Contains troubleshooting information related to printing, and any errors that have occurred in printing drawings or reports to a printer, a plot file, or a PDF file. This log file is saved in the \logs folder under the current model folder. A limited number of older log messages related to printing are archived and saved in the DPMPrinter2_ <user>.log file. This file contains approximately 1024 KB of data.
drawing_cloning.log	Contains information about cloned drawings. This log file is saved in the current model folder.
drawing_history.log	Contains information about drawing history. Use the advanced option XS_DRAWING_HISTORY_LOG_TYPE to define the contents of the file. This log file is saved in the current model folder.
dstv_nc.log	Each time you create NC files, Tekla Structures stores information in this file about the processed assemblies. This log file is saved in the current model folder.
error_<user>_<YYYYMMDD>_<HHMMSS>.log	Each time an error occurs in Tekla Structures, the error is saved in an error log file. Error log files contain the description of errors that have occurred at a particular time. For example, if an error has occurred on April 1, 2019 at 9:15:30 AM, the name of the related error log file is error_<user>_20190401_091530.log. This log file is saved in the \logs folder under the current model folder.
filetranerror.log	Used only for cold rolled components, such as Albion, Ayrshire, and Hispan. If the File Transfer components do not work as expected, Tekla Structures stores error messages in this file. This log file is saved in the current model folder.
modelsharing.log	Contains the sharing operations that have been performed in Tekla Model Sharing. For example, opening a shared model and reading in the changes made by other users are stored in the modelsharing.log file. This log file is saved in the \logs folder under the current model folder.
numberinghistory.txt	Contains full details of each numbering session carried out on the model. Each session is in a different block of the file. This log file is saved in the current model folder.
PublishToTrimbleConnect.log	Contains upload information and the errors that have occurred when uploading the Tekla Structures model to a linked Trimble Connect project as a `.tekla` file. This log file is saved in the \logs folder under the current model folder.
save_history.log	Tekla Structures stores information in this file each time you save a model. This log file is saved in the current model folder.
sharingfacade.log	Contains the essential information from the client log files when an error has occurred in the Tekla Model Sharing sharing service. This log file is saved in the \logs folder under the current model folder.
TeklaStructures_<user>.log	Contains information about the entire Tekla Structures session from opening the model to closing it. The file contains, for example, errors and information about which catalogs were used. This temporary log file is saved in the \TeklaStructuresModels folder, and is removed when you close Tekla Structures.
wizard.log	Tekla Structures stores information in this file when you run a drawing rule set (wizard) file. The file contains, for example, errors and the number of drawings created. This log file is saved in the current model folder.

View a log file

You can view most log files in the Tekla Structures log viewer, or in the application that has been associated with the file type, such as Microsoft Notepad.

If the log file contains information about parts or assemblies, you can check the parts or assemblies in the model. In the log file, select a row that contains a part or an assembly.

Parts and assemblies have the prefix guid.

Tekla Structures highlights the part in the model. If there are several parts or assemblies on a row and you select that row, Tekla Structures highlights all the parts in the model. You can also select parts on different rows.

Tip:

You can open the right-click menu for a part or an assembly from the log file by right-clicking a row that contains a part or an assembly. Tekla Structures shows the same menu as when you right-click a part or an assembly in the model.

Open the model for which you want view the log history.
On the File menu, click Logs, then select a log file.
- Clash Check history log (ClashCheck.log)
- Session history log (TeklaStructures_<user>.log)
- Numbering history log (numberinghistory.txt)
- Saving history log (save_history.log)
- Drawing history log (drawing_history.log)
- Analysis history log (analysis.log)
View the log file in one of the following ways:
- To view the log file in the log viewer, in File > Logs select View with Tekla Structures log viewer.
- To view the log file in the application associated with the file type, File > Logs select View with default application.

Change the name and location of session history log file

You can change the name and location of the session history log file (TeklaStructures_<user>.log).

If someone else manages your installation of Tekla Structures, do not change these settings unless you are instructed to do so.

Windows username and the .log file extension are always added after the customizable part of the name.

Open a suitable initialization file for editing.

For example, user.ini or company.ini.
To change the name of the session history log file, add the following line to the initialization file:

set XS_LOG_FILE_NAME=<name of the file>

For example:

set XS_LOG_FILE_NAME=sessionhistory

If the Windows user name is "achilles", this example would result in a log file named sessionhistory_achilles.log.

The default name is TeklaStructures_<user>.log.
To change the location of the session history log file, add the following line to the initialization file:

set XS_LOGPATH=<location of the file>

If there is no other location set, the file is stored in the parent folder for model folders (by default c:\TeklaStructuresModels).
Save the initialization file.
Restart Tekla Structures for the changes to take effect.

Numbering history log file

The numberinghistory.txt log file contains full details of each numbering session carried out on the model. Each numbering session is in a different block of the file.

If one numbering series overlaps another, the errors are written to the log file.

Note:

If you remove or delete the numberinghistory.txt log file, Tekla Structures generates a new file with the same name the next time you run numbering. The new file does not contain a history of previous numbering sessions.

Example

This example shows the contents of a numberinghistory.txt log file.


1	User name, date and time of the numbering.
2	Numbering method. `Modified numbering` is displayed when you run the Number modified objects command. `Modified numbering for selected series` is displayed when you run the Number series of selected objects command. `Diagnose & Repair Numbering: All` is displayed when you run the Diagnose & repair numbering: All command. `Diagnose & Repair Numbering: Series of selected objects` is displayed when you run the Diagnose & repair numbering: Series of selected objects command. `Renumber all` is displayed when you select the Renumber all option in the Numbering Setup dialog.
3	Some Compare options set in the Numbering Setup dialog are displayed in the numbering.history log file only if they are set differently than the default value: `Compare modified to old parts` `Compare new to old part` `No holes comparing` `No part name comparing` `Beam orientation` `Column orientation`
4	Numbering options. `Use old numbers` is displayed only when you have selected the Re-use old numbers option in the Numbering Setup dialog. `Check for standard parts` is displayed only when you have selected the Check for standard parts option in the Numbering Setup dialog.
5	Tolerances are set in the Numbering Setup dialog.
6	Changes in the position numbers and in the numbering series during one numbering session.

Numbering series in the numbering history log file

Tekla Structures lists information about the numbered parts and assemblies in the numberinghistory.txt log file.

Example 1

The numberinghistory.txt log after one concrete beam B/20 has been created and numbered:


1	Part position number. The part with the GUID `ID510F595D-0000-0030-3133-353939383335` is a part of the numbering series `Concrete_B-20/1`. The part becomes the first part in the numbering series: `Concrete_B-20/0 -> Concrete_B-20/1`.
2	Assembly position number. The assembly ID of the part is `ID510F595D-0000-002F-3133-353939383335`. The part belongs to the `B/20` assembly numbering series, which is also the cast unit numbering series. The part gets the assembly position number: `B/20: B/0 -> B/20`.

Example 2

The numberinghistory.txt log after another concrete beam B/21 has been created and numbered:


1	Part position number of the new part. The part with the ID `ID510F595D-0000-0030-3133-353939383335` is part of the numbering series `Concrete_B-20/1`. The part becomes the second part in the numbering series: `Concrete_B-20/0 -> Concrete_B-20/2`.
2	Assembly position number. The assembly ID of the part is `ID510F595D-0000-002F-3133-353939383335`. The part belongs to the `B/20` assembly numbering series, which is also the cast unit numbering series. The part gets the assembly position number: `B/20 B/0 -> B/21`.