Answer: You or the Tekla Structures administrator in your organization must install the license server on a server computer in your network (so that it can be used by many users) or on the same computer as Tekla Structures (if you do not need to share the license). If you have not 1) installed the license server and 2) activated your license, do so now.
Moving forward, we recommend that you upgrade to the latest license server version when you upgrade Tekla Structures. Each license server version is typically compatible with several Tekla Structures versions, but if you do not upgrade the license server, it will eventually stop working with newer Tekla Structures versions.
Tekla License Server
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:
For example, you could set the license server address to 27007@server1 in Tekla Structures user interface, and set the Windows system environment variable to 27007@server2, and, in addition to that, start Tekla Structures with a batch file that sets the license server address to 27007@server3. When you run your batch file in this case, Tekla Structures uses 27007@server3 as the license server address.
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.
This is one of the most frequently submitted queries to Tekla Support.If the incorrect license method is assigned during installation e.g. selecting Local Computer Locked instead of server by mistake, the installation wizard will not prompt the user to assign a license server.As a result of the above, when launching the product, the License Manager will launch instead due to the product searching for a non existent local license instead of a server license.The steps below run through the changes required to assign a license server and successfully launch the product:
If the "Lock Id" as displayed in the yellow information bar at the top the License Manager is blank the Sentinel RMS License Manager is not installed or running correctly. For further guidance on this issue see the article The Sentinel RMS License Manager Service is not running on the license server...
Products from other software companies may have installed an older version of the SafeNet RMS License Manager. Multiple versions of the RMS license manager can be installed but only one version can run at any one time.
This can occur in some circumstances for multiple server licenses when one or more has been commuted. For more about this situation and what to do see the article Commuter licenses - Incorrect number of In Use licenses
If the Windows firewall is disabled and the client is getting Error 5 then you probably have a third party firewall product (software or hardware e.g. router) preventing incoming connections to the server on the licensing port (default 5093). The license server and client communicate using the UDP protocol on the default port of 5093.
With Tekla License Administration Tool you will get also LMTOOL. This tool is mainly used on a client computer to check the status of the licenses on the license server, manage the license server and find/solve problems.
Now your Tekla is ready to go with default or local environment(s). Next, we recommend to read the article 11 Ways For Beginners To Learn Tekla Structures. There are free resources with links where to start learning Tekla. Why wait if you have the software and license ready for some action?
Tekla Structures Partner licenses are assigned and managed in the Tekla Online Admin Tool. The organization's administrator assigns and manages the licenses in the Tekla Online Admin Tool. To see who is your organization's Tekla Online administrator, check My Organization.
Organization's administrator can transfer Tekla Structures Partner licenses from one person to another, so the same license can be used by different people as the projects progress and resource needs change. If you do not have enough free licence seats for all users who try to use Tekla Structures Partner the same time, some users attempting to join see a message that all license seats are reserved.
You could roll your own in your current office - but then again, why rely on physical offices, and physical servers etc. all liable to problems such as theft, connectivity problems, and staff forgetfulness:
Example #4 - Ransomeware. What if your license server goes down or gets ransom-ware in there? We might loose our entitlement certificates and this would afford a nice opportunity for Trimble to hold us up.
If you want help, you might have to ask an AWS specialist to help you. And you might need a Tekla user to set up: LM Tools and your Tekla License Server Admin Tools properly. All you probably want to do is to press a button and have your Tekla licenses available to whom you want to give access, anywhere in the world. My plan is to set it all up with a click of a button, using Cloud Formation and AMIs - or even better, to use Terraform to set it all up for you.
Discussion: This error indicates that the FLEXlm routines in the application are unable to make a TCP connection to the server and port specified in the license file. Possible causes/solutions for this behavior are listed below 1.) PROBLEM: The wrong license file is being referenced by IDL. SOLUTION: Verify that the application is using the proper license file. Check the paths and spelling of the licenses listed in the "license path" indicated in the error message. 2.) PROBLEM: The server machine specified in the license file is down; SOLUTION: Verify that specified server machine is up and reachable by executing another command that uses TCP, such as ping, from the client to the server. For example, if the IP address of the license server machine "myserver" is 123.456.789.0, open a DOS command prompt on the IDL client machine and issue the command: ping 123.456.789.0 or ping myserver TCP must be available on both the client and the server machines in order to use a floating license. If network problems are suspected, contact your system administrator for assistance. 3.) PROBLEM: The license manager service is running but the IDL vendor daemon specified in the DAEMON line of the license file (IDL_LMGRD.exe) is not running; SOLUTION: Check the license manager debug log file and run the lmstat command to try to determine if the vendor daemon is down and to get clues about how to resolve the problem=: a.) Verify that the vendor daemon is running. Check the license manager debug log file that was specified when configuring the license manager. b.) Examine the license manager debug log file to see if any problems are reported, particularly messages indicating that the vendor daemon has quit. c.) Run lmstat -a from the server machine to verify that the vendor daemon is alive. For example, if your IDL 6.4 installation is located at C:\Program Files\ITT\ IDL64 and license manager was started using a license file with the following SERVER line:
Where 1700 is the number at the end of the SERVER line of the license file and "myserver" is the name of the license server machine as it appears in the license file. 4.) PROBLEM: The host name in the license file is not recognized by the system; SOLUTION: If the license manager or the vendor daemon (idl_lmgrd) is down, make the necessary corrections to the license manager setup on the license server machine and then start or restart the FLEXlm license manager service on that server machine. (Note that the FLEXlm license manager service for an ITT license should only be started (only one instance), on the designated license server machine that is listed in the SERVER line of the license file.) Information about configuring, starting and stopping the FLEXlm license manager on Windows 2000 or XP can be found in the "License Management Guide" (license.pdf) in the IDL Online Manuals of your installation or on your product CD. 5.) PROBLEM: The network between the client machine and the server machine is down. SOLUTION: Run lmstat -a (see item (3c) above) from the client machine to verify the connection from client to vendor daemon across the network. Also run lmdiag to get additional clues about a network related problems and how to resolve them in the context of this problem. For example:
6.) PROBLEM: TCP is not running on your machine. SOLUTION: From the client machine, try using telnet host port where host and port are the same as on the SERVER line in your license file. Using the example license and installation example above, open a DOS command prompt issue the following command: 2ff7e9595c
Comments