Tekla Structures 16.0 Server Address
Channing Arther
Note! There is a known issue that prevents a feature described on this page from working correctly: The XS_LICENSE_SERVER_HOST setting from bypass.ini is currently ignored in Tekla Structures versions 2020 and 2021. We have fixed this issue in Tekla Structures 2020 SP13 and Tekla Structures 2021 SP8.
You can easily define or change the license server address of host computers in the Tekla Structures user interface. But in some cases, you might need to do it without starting Tekla Structures, like when you distribute Tekla Structures on a lot of new computers. Here are some alternative ways:
Check the four alternative procedures above and pick the easiest one for you to use.
All of these procedures can be centralized, for example, using Group Policy in an Active Directory environment in Windows.
Note: when Tekla Structures starts up, it checks the Windows environment until the setting is found. The order of precedence is the following:
A license server is intended to be assigned during the installation of a product. The user is asked to select a license method during the installation process (server in this case), then asked to type either the name (hostname) of the server or the IP address of the server.
When the installation is complete and the product is launched, the product will use the server method and server name assigned during the installation to claim a license.
Question:
I am unable to connect to the model sharing service and get the following error:
"Sharing operation failed. Service Could not be reached - realm or server address could be wrong. Please check the model sharing log, and contact Tekla Structures support if the problem persists."
Answer:
Check the model sharing service logs (ClientLog_cat.txt or ClientLog_dog.txt) to see if the reason is that email is not verified in system.
2021-02-19 12:37:02 UTC: [ERROR]
TS Facade: Connect (cloud) returned error: Connect failed in phase1: NetworkError (10)
Network error: Status: 401 (Unauthorized)
TeklaStructuresFacade 3.13.9.0 failed to connect cloud service using service url -eu.teklamodelsharing.com from Z-USERMACHINE.
Check service documentation for connection requirements.
(ErrorCode: ServiceUnreachable)
[] [] [p=9a9aa999-c99a-999a-a999-99aaa9a9aaaa][]
There can be scenarios where the account.tekla.com email verified and Trimble Identity email verified fields are out of sync so that the Trimble Identity record may show as not verified. To resolve this reset the password via the account.tekla.com Trimble Identity login in screen - this has proven the resync email verified fields.
See also
Trimble Identity for Tekla Online services
With these steps you can try to verify if this is a network problem. Do the following steps on at least one of the client computers where some multi-user error message normally appears (IP address 123.456.7.890 should be replaced with the IP address of your multi-user server):
If there are plenty of Request timed out messages you can suspect that there is a network issue. This could be caused for example by a broken hardware on the network, such as a router or a switch.
If there is nothing suspicious in the Command Prompt, this is not a network problem. We can continue checking where else the problem might be. It could be for example the port, the multi-user server application, or Tekla Structures.
In some cases we have found out that disabling offline files in Windows Sync Center helps with weird multi-user connection problems. You find this setting under the Manage offline files in the Sync Center.
This article is for Tekla Structures Multiuser server version 2.3 or older.
For setting up multiple instances of the Tekla Structures Multiuser server version 2.301s, use the following link:
Setting up multiple instances of Tekla Structures Multiuser Server
Question:
How to set up several Tekla Structures multi-user servers on one computer?
Answer:
To set up the second multi-user server (or more), you do not have to run the Multi-user server installer several times. Just create a new shortcut for the multi-user server:
The new multi-user server will use a different database file for handling the model changes. One multi-user model must always use the same multi-user server so that the system is able to keep track of changes. Agree with your users which models use which multi-user server and make users aware that changing the multi-user server is not allowed. Do not set up several multi-user servers if there is no specific reason to do so - one multi-user server can handle several models.
Make sure that computers running Tekla Structures can access the port you defined earlier (TCP port 1240 in the example above). For example, create a firewall rule that allows incoming communications on TCP port 1240 on the computer where the multi-user server is running.
When using the new multi-user server address in Tekla Structures, type the address in format server_hostname,port
where server_hostname is a hostname (or, alternatively, IPv4 address) of the computer where the multi-user server is running on, port - the TCP port you defined earlier.
For example, if your multi-user server is running on a computer whose name is my_company_server and the TCP port is set to 1240, then you should use the following multi-user server address in Tekla Structures:
The remote connection required that the user has the Tekla PowerFab Remote Service (used for Tekla PowerFab GO, as well as Automated Events like database backups and scheduled reporting) installed and running on the PowerFab server. In PowerFab Office/EPM, create an External User, and give that user permissions to log in and view jobs. You could optionally start out giving the external user full permissions to everything, then when your tool is working, you can remove privileges that are unnecessary. Update the code to use the proper IP address of the remote server, port used by the remote server, username and password, then add any command available.
b37509886e