Slow Tekla Structures start up

Tekla Structures
Not version-specific
Tekla Structures
start up
Not environment-specific
Tekla Structures starts very slowly. How can I make it faster?

You could try the following things to help your Tekla Structures to speed up more:
1. Replace the server hostname with IP address in tekla.lic and in TS Connect to License Server dialog. This helps if you happen to have delay in your name services.
2. Check that there is a free TCP/IP port defined in the end of the first row of tekla.lic. Check that the port is also defined in the Connect to License Server dialog and/or in user.ini/.bat. This way we can close out the delays that may be caused by the port searching process.
3. Is there any other FLEXnet/FLEXlm service (for example AutoCAD license server) installed on the same server computer? If the other licensing service has not been designed to be compatible with TS License Server, then it might cause delays or even prevent TS License Server from working. You can close out this for example by installing TS License Server into another computer that has no other FLEXnet/FLEXlm services running on it.
4. You can try to set the environment variable TCP_NODELAY on. This may increase the network traffic but it can also speeds up the starting of TS. You can set the variable on in the following way:
- Go to Start > Control Panel > System to open the System Properties dialog.
- On the System Properties dialog, go to Advanced tab. Click the Environment Variables button.
- Under the System variables, click the New button.
- On the New System Variable dialog, type TCP_NODELAY into the Variable name field. Type 1 into Variable value field. Click OK.
- On the Environment Variables dialog, click OK.
- On the System Properties dialog, click OK.
- In LMTOOLS Stop and Start the server. The variable starts to take effect after the first start of Tekla Structures, that is taking the license from the server.
5. Hotfix for Tekla Structures for the problem with the slow startup. For the hotfix please refer to the support article here.
Was this helpful?