DriveWorks Pro 15: How To: Troubleshoot Licensing (KB13010807) [send feedback...]

Unable to Connect to the Internet

The Licensing Wizard displays a message if activation failed due to an internet connection issue.

  • Check your network status.
  • Check that your web browser can reach other sites.
  • A proxy server may be blocking access. Please see the section sub-headed Proxy Server blocking communication with license server below.
  • A firewall may be blocking the communications port used. Please see the section sub-headed Firewall below.

Floating License Retrieval Failed

When connecting to DriveWorks License Manager to obtain a network license you may see the above message. There could be a number of reasons for this, these are listed below:

  • License unavailable on the DriveWorks License Manager.

    Common cause of the license being unavailable include:

    • License not activated on the DriveWorks License Manager. See Floating License Server Licenses for information about this.
    • The license on the DriveWorks License Manager is not a valid license. 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.
    • The Network License Service has not been started on the DriveWorks License Manager. See Floating License Server Licenses for information on starting the license service. If any firewall setting have been changed since the service was started, stop and restart the service.
  • Firewall on the machine with DriveWorks License Manager installed is preventing access.

    There are 2 methods of adjusting firewall settings so the DriveWorks License Manager machine can be discovered by the DriveWorks application trying to obtain the license. Choose one of the following options that best suits your IT policy:

    1. Add the DriveWorks Licensing applications to the list of exceptions. Open the Firewall application on the machine with DriveWorks License Manager installed and:
      • Add the program C:\Program Files\DriveWorks\ Version\ lmgrd.exe to the list of exceptions.
      • Add the program C:\Program Files\DriveWorks\ Version\ drivewks.exe to the list of exceptions.
    2. Add the required discovery and communication ports on the firewall application. Open the Firewall application on the machine with DriveWorks License Manager installed and:
      • Add the discovery Port to the Firewall application, use the TCP protocol. By default DriveWorks License Manager will use port 27000 for this. 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. The port number allocated in DriveWorks License Manager and the port number added to the Firewall exception must match.
      • Add a communication port to the Firewall application, again use the TCP protocol. Communication ports are typically dynamic (constantly change) which itself can cause issues. The step below will force DriveWorks License Manager to use a pre-determined port number. The number allocated to the Firewall exception and the port number used in the license file below must match.
      • Force DriveWorks License Manager to use the communication port added above. Modify the license file to force DriveWorks to use the same port that was added to the Firewall exception above.

        How to modify the license file

        Locate the file C:\ProgramData\DriveWorks\ Version\LicensingData\Licenses.lic

        Open the file in a text editor (Notepad), the file should contain the data:

        SERVER this_host ANY
        VENDOR drivewks
        USE_SERVER

        This can be modified to force DriveWorks to always use the same port number to obtain a license. Open the license file in Notepad and modify the contents to read

        SERVER this_host ANY
        VENDOR drivewks PORT= 28001
        USE_SERVER

        where 28001 is the port number to force DriveWorks to use.

  • The machine trying to obtain the license cannot see DriveWorks License Manager. Common causes of this happening include:
    • Incorrect server information added to the Licensing Wizard (see image below) for the DriveWorks application trying to communicate with DriveWorks License Manager. See table below for examples of server names.
    • Incorrect port number identified. 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.

Example Server Names

Server Name ExampleDescription
MyserverUse 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@MyServerUse 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.localUse 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 a different domain to the machine with DriveWorks License Manager installed.
2800@MyServer.DomainName.localUse 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.

Fixed License - Activation Failed

Possible causes of failure to activate a fixed license are listed below.

Proxy Server blocking communication with license server

How to determine if you are behind a Proxy Server

Using Internet Explorer

  1. Left-click the "Tools" down arrow and select "Internet Options" from the drop-down list. This will open the Internet Options window.
  2. Left-click the "Connections" tab.
  3. Left-click the "LAN settings" button. This will open the Local Area Network (LAN) Settings window. If the "Use a proxy server for your LAN" box is checked, and there is an address and port number present, you are behind a proxy.

Using Firefox

  1. Left-click on the "Tools" menu item and select "Options ..." from the drop-down menu.
  2. Left-click on the "Advanced" icon.
  3. Left-click the "Network" tab.
  4. Left-click the "Settings..." button. If the "Manual proxy configuration" radio button is checked, and there are addresses and port numbers, you are behind a proxy.

Using Google Chrome

  1. Click the Customize and Control Google Chrome button and then click settings.
  2. At the bottom of the menu click +Show Advanced Settings.
  3. Find Network and then click the Change Proxy Settings button.
  4. Left-click the "LAN settings" button. This will open the Local Area Network (LAN) Settings window. If the "Use a proxy server for your LAN" box is checked, and there is an address and port number present, you are behind a proxy.

Configure DriveWorks Licensing for a Proxy Server

Step 1

Follow the steps to activate the license automatically see Automatic Activation.

When the dialog that shows the attempt to activate is displayed (image on the left) click the Stop button.

Step 2

Click the radio button to Configure proxy details

Click Next

Step 3

Enter the proxy details.

Click Next to begin activation again.

Firewall

If you do not use a proxy server it may be an issue with the communications port the license is configured to use. To test this type the following link into your internet browser

http://lserver.driveworks.co.uk:8080/flexnet/services/ActivationService?wsdl

You should see a web page as below

If you can view the xml page in the browser your communications port is configured correctly and you should contact your DriveWorks reseller for more assistance.

If the browser reports an error page you will need to allow access through port 8080 on your firewall. Your computer administrator will be able to assist with this.

Activation Failure

When licensing activation fails the dialog will give an accurate description of the issue.

Common Activation Issues

The chart below lists the common causes of activation issues and recommends a course of action to rectify the problem.

Problem Code is the last 4 digits of the code given in the Activation Failed dialog.
Problem CodeMessageCourse of Action
7109The code you entered was not recognized.
  • Check the code you have been issued and re-enter carefully.
  • If you have the code in digital format (in an email or text file for example) copy and paste the code directly into the activation dialog.
7174The code you entered is obsolete.
  • Obtain your new code from your reseller.
7288The code you entered has already been used the maximum number of times.
  • Return a license from a machine it is no longer required on.
  • Purchase additional licenses from your reseller.
7343The code you entered has expired.
  • Obtain a new activation code.
  • Purchase a license from your reseller.
7288The code you entered has already been activated on a different machine.
  • Return a license from the machine it was activated on.
  • Purchase additional licenses from your reseller.


Knowledge Base Article Ref:KB13010807

A Proxy Server is a server that acts as an intermediary for requests from clients seeking resources from other servers (such as the internet).

A Proxy Server can be used to restrict traffic to the internet from client computers.

A Proxy Server is a server that acts as an intermediary for requests from clients seeking resources from other servers (such as the internet).

A Proxy Server can be used to restrict traffic to the internet from client computers.

Table of Contents