Troubleshooting

First Verify the license location you entered in preferences:

1. In MDWorkbench, click "Windows > Preferences" and "MDWorkbench > License".
2. 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:

1. Open Windows PowerShell.
2. Type the following command: Test-NetConnection -ComputerName myserver -Port myPort
   The command should look like Test-NetConnection -ComputerName myserver.company.com -Port 27000
3. Verify you see TcpTestSucceeded : True in the output, that should look like:

   ComputerName     : myserver.company.com
   RemoteAddress    : xxx.xxx.xxx.xxx
   RemotePort       : 27000
   InterfaceAlias   : xxxx
   SourceAddress    : xxx.xxx.xxx.xxx
   TcpTestSucceeded : True
   

Thirdly Have the site administrator check the license manager is running and accessible, using those steps on license server side:

1. Check the license server manager (lmgrd) has been started: In LMTOOLS, click the "Start/Stop/Reread" tab and "Start Server".
2. 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).
3. 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.

The hostid of your workstation does not match the hostid specified in the license file. This usually means your actual hostname is not exactly the one you gave to Sodius.

Your actual host name is displayed in the license error message. You can also verify your workstation host name by opening a Windows Command Prompt and typing "hostname".

Contact Sodius support and provide the actual host name as displayed in the error message.

Here are the possible causes:

• Your license file does not contain a feature required for the capability you are trying to use.
• Your license file contains the feature required but not for the actual version of the product. This can happen if you have a license for a previous version of the product and have upgraded the product without upgrading the license.

Contact Sodius support to verify you have the adequate license for your evaluation or for the product you purchased.

This error occurs when the maximum number of concurrent of users is reached. You may wish to purchase additional licenses to avoid this error message appearing.

Floating licensing, also sometimes known as concurrent licensing or network licensing, is a software licensing approach in which a limited number of licenses for a software application are shared among a larger number of users over time. When an authorized user wishes to run the application they request a license from a central license server. If a license is available the license server allows the application to run. When they finish using the application, the license is reclaimed by the license server and made available to other authorized users.

This error occurs when the license file has been moved to a different place within your file system. You can change the license location in the preferences:

1. In MDWorkbench, click "Windows > Preferences" and "MDWorkbench > License".
2. Click "Browse..." to select the license file is your file system.

The license file is not perpetual and has all or some features that have expired. Contact Sodius support to request a new license file if required.

This error occurs when an invalid (inconsistent) license key or signature is found. The license key/signature and data for the feature do not match. This usually happens when a license file has been altered. Contact Sodius support to request a new license file if required.

This error occurs when the port number is incorrectly set. The license location notation is port@host and not host@port. In MDWorkbench, click "Windows > Preferences" and "MDWorkbench > License" to fix the license location.

Your license file does not contain the required version of a feature. This can happen if you have a license for a previous version of the product and have upgraded the product without upgrading the license.

Contact Sodius support to verify you have the adequate license for your evaluation or for the product you purchased.