Troubleshooting Trimble Connect interoperability problems with Tekla Structures

Windows

Trimble Connect

Web

Trimble Connect

Mobile

Trimble Connect

Not version-specific

Tekla Structures

This article lists Tekla Structures specific steps for troubleshooting Trimble Connect interoperability problems. This apply mainly in the situation where you have Tekla Structures model sharing model and you are using automatic upload to Trimble Connect project during write out.

Upload the Tekla Structures model to Trimble Connect - the basic workflow
XS_UPLOAD_SHARED_MODEL_TO_CONNECT - this advanced option defines when Tekla Structures model is uploaded to Trimble Connect project
XS_CONNECT_UPLOAD_MODEL_FOLDER - this advanced option specifies the folder name in the Trimble Connect project to which the Tekla Structures model will be uploaded
Requirements for connecting to Tekla Online services - if your organization restricts internet access, your IT team must allow the necessary https URLs and ports needed for Tekla online services to function properly

Troubleshooting advices to a situation when linking Tekla Structures model to Trimble Connect is not working:

Check the status of online services https://support.tekla.com/article/status-of-online-services
Check that all project users are using the same Service Pack and environment for Tekla Structures.
If you are using Trimble Connect web version, test if it works with desktop version.
If you are using Trimble Connect desktop version, check that you have the latest version.
Ensure you are using the correct license; for instance, use the Trimble Connect Business license instead of the Trimble Connect Free license.
Check that you have been invited to the project and you have the folder permissions in Trimble Connect project.
Try signing out from your Trimble Identity and restarting Tekla Structures and Trimble Connect.
Ensure that you do not have multiple Tekla Structures sessions open. Close them and try again.
Check that all users are using the same system locale Language for non-Unicode programs in Windows Region Administrative settings. If not, special language-dependent characters in the path names might be causing issues because the paths are not interpret correctly.
Check also that users have not checked this setting: Beta: Use Unicode UTF-8 for worldwide language support in Windows Region administrative settings.
Image
Make sure that anti-virus or some other 3rd party software is not interfering the Tekla Structures files and folders.
Check the error logs in your model folder Logs subfolder.
In the log file called PublishToTrimbleConnect.log might be more information for the reason of the error, like for example:
- ```
Trb creation failed 
```
- ```
Error, can't find environment!  
Error in reading Ini file
```
- ```
Error Code FILE_CHECKED_OUT_BY_ANOTHER_USER
```
- Folder issue:
- Loading C:\TeklaStructuresModels\... \environment.db FATAL ERROR: There is no mapping to the Unicode character in the multi-byte destination code page.
If you are using customized environment make sure that all paths and settings are read correctly. When starting Tekla Structures check that there are no errors from these definitions in the session history log. Check the TeklaStructuresModel.xml file, especially that the environment is written correctly.
Check that no files are checked out in the Trimble Connect project. For more information about this functionality in Trimble Connect, see Checkin & Checkout
Check if you can use the Visualize all command in Tekla Structures, that is creating a file in the same format as the Trimble Connect link. If this works, then the problem is usually not Tekla model-specific, but might relate to the upload to cloud.
The problem might for example be that there are some far-away objects added to the model or that there are some broken objects in the model. Use Find distant objects command to list objects which are having big coordinates or far away location. Use inquire command in that list and try removing the broken or far-away objects.
Another troubleshooting step is try to use as little properties as possible for the exported .tekla file: copy the ..\Environments\common\system\UploadToConnect\part.epr to the model attributes folder and remove all the properties
Check from the Windows Task Manager, if you have these processes running when writing out:
- TrimbleConnectInteroperability
- Tekla Structures ModelExporter
We have had issues where some processes work differently on different Trimble Connect servers (Europe, North-America. Asia, Australia) and for example export path changes itself, but they are fixed from 2020 SP10 and 2021 SP3 onwards
Stop / start collaboration with the Trimble Connect project

If needed, contact your local support and inform which Trimble Connect and Tekla Structures versions you are using and which Trimble Identity account you are signed in.

See also

Troubleshooting Connector problems