This topic gives solutions to resolve issues with Floating (Network) Licenses.
For troubleshooting issues with a Fixed License please see How To: Troubleshoot Licensing.
When connecting to DriveWorks License Manager to obtain a network license you may see this message.
This topic covers the possible reasons for this and how to resolve them.
Common causes of licenses being unavailable include:
See Floating License Server Licenses for information about this.
Check the application trying to connect to the network license with the code that has been activated on the DriveWorks License Manager.
See Info: Identifying Activation Codes for information on license codes.
Check the Floating License Server Licenses for information on each the Status of code.
See License Management for information on the Status of license codes.
See Floating License Server for information on starting the license service.
If any firewall setting have been changed since the service was started, stop and restart the service.
Only the firewall on the DriveWorks License Manager machine needs to be adjusted.
DriveWorks floating licenses require two routes of contact with the license server:
By default, DriveWorks always requires inbound TCP 27000 to make the License Server discoverable.
If this is already in use it can be changed in the DriveWorks License Manager, see Floating License Server Licenses for information on how to do this.
Dynamic by default meaning this port constantly changes.
There are two methods of adjusting firewall settings so DriveWorks applications can obtain a license from the DriveWorks License Manager machine.
Both methods require the discovery port to be added to the firewall:
The port number allocated in DriveWorks License Manager and the port number added to the Firewall exception must match.
After adding the discovery port choose one of the following options that best suits your IT policy:
C:\Program Files\DriveWorks\Version\lmgrd.exe
C:\Program Files\DriveWorks\Version\drivewks.exe
C:\ProgramData\DriveWorks\Version\LicensingData\Licenses.lic
Original Licenses.lic file
SERVER this_host ANY VENDOR drivewks USE_SERVER
Modified Licenses.lic file
SERVER this_host ANY VENDOR drivewks PORT=28001 USE_SERVER
This forces the DriveWorks License Manager to use TCP port 28001 as the communication port.
The ports cannot be the same as the License Manager port (27000).
The port number allocated in the Licenses.lic file and the port number added to the Firewall exception must match.
Common causes stopping the machine from seeing the DriveWorks License Manager machine include:
See table below for examples of server names.
If the discovery port has been changed on the DriveWorks License Manager machine it will need to be identified in the server path name on the machine obtaining the network license.
See table below for examples of server names.
Server Name Example | Description |
---|---|
Myserver | Use when default discovery port 27000 is in use on the DriveWorks License Manager.
And the machine with the DriveWorks application trying to obtain the network license is on the same domain as the machine with DriveWorks License Manager installed. |
28000@MyServer | Use when default discovery port 27000 has been changed on the DriveWorks License Manager (replace 28000 with the port number selected on the DriveWorks License Manager).
And the machine with the DriveWorks application trying to obtain the network license is on the same domain as the machine with DriveWorks License Manager installed. |
MyServer.DomainName.local | Use when default discovery port 27000 is in use on theDriveWorks License Manager.
And the machine with the DriveWorks application trying to obtain the network license is on a different domain to the machine with DriveWorks License Manager installed. |
28000@MyServer.DomainName.local | Use when default discovery port 27000 has been changed on the DriveWorks License Manager (replace 28000 with the port number selected on the DriveWorks License Manager).
And the machine with the DriveWorks application trying to obtain the network license is on a different domain to the machine with DriveWorks License Manager installed. |
The table below lists the common causes of retrieval issues and recommends a course of action to rectify the problem.
Problem Code | Message | Course of Action |
---|---|---|
-5 | No such feature exists. |
|
-9 | Invalid host. The hostid of this system does not match the hostid specified in the license file. |
|
-15 | Cannot connect to license server system. |
|
-97 | The desired vendor daemon is down. |
|
Knowledge Base Article Ref: | KB20112701 |
---|