First Verify the license location you entered in preferences:
- In MDWorkbench, click "Windows > Preferences" and "MDWorkbench > License".
-
Make sure the server location entered here (e.g. @myserver) is the one your system administrator communicated.
Notes:
-
The server location may include a port number (e.g. 27000@myserver)
only in the case the system administrator explicitly assigned the exact same port number in the license file on server side.
-
If accessing through a VPN, you may need to specify an FQDN [host name].[domain].[tld] (e.g. @myserver.mycompany.com)
Secondly Verify your workstation has network access to the license server:
- Open a Windows Command Prompt.
- Type "telnet host port" (e.g. "telnet myserver 27000") and verify you can successfully connect to this port.
Thirdly Have the site administrator check the license manager is running and accessible, using those steps on license server side:
- Check the license server manager (lmgrd) has been started: In LMTOOLS, click the "Start/Stop/Reread" tab and "Start Server".
- Check the firewall is configured to allow an inbound connection on the port referenced in the license file (or the range 27000-27009, if not explicitly set).
- Check vendor features (e.g. "sodius") are not mixed within the license file. You need to separate licenses of, for example, IBM Rational from the Sodius ones (i.e. use different license files).
If none of these steps resolve the issue, contact Sodius support and communicate all relevant information,
notably the log files of the license server manager for analysis.
|