Licensing

Licence errors

For licence errors which occur while using the Bladed user interface, running simulations, or using the the SIF to Wdnh Converter, consult the relevant page below:


Applying V2C files

Errors which may occur when applying a V2C licence update file are explained below:

Error message: HASP_UPDATE_TOO_OLD (error code 54)

Cause

The V2C file has already been applied successfully to the dongle previously (it is not possible to apply the same V2C file to a dongle more than once).

This error may occur if:

  • If it is not clear which V2C file needs to be applied, and the wrong file has been applied
  • The Apply File button has been clicked twice quickly by accident

Solution

Please first confirm if the licence is already up-to-date:

  • Check the Features page on the licence manager website (http://localhost:1947/_int_/featrues.html) to see if the expected licence features and expiry dates appear to be correct.
  • You can also try running Bladed 4, to see if the modules and Bladed 4 versions that you expect the licence to support work as expected.

If the licence configuration does not appear to be up-to-date:

  • Please generate a C2V file for the dongle, and send the file to us as an email attachment. We will check if the licence is up-to-date, and send a further pair of V2C files to reset the licence on the dongle if necessary.

Error message: HASP_UPDATE_TOO_NEW (error code 55)

Cause

A previous V2C file for the dongle has not yet been applied. V2C files must be applied in the order that they were generated in (without any gaps).

Solution

Please first check if any previous V2C files that were sent may not have been applied (if you try applying a V2C file that was previously applied successfully you will receive a HASP_UPDATE_TOO_OLD error message).

If you are not able to determine which previous V2C files have not yet been applied:

  • Please generate a C2V file for the dongle, and send the file to us as an email attachment. We will check if the licence is up-to-date, and send a further pair of V2C files to reset the licence on the dongle if necessary.

Error message: HASP_KEYID_NOT_FOUND (error code 18)

Cause

The dongle that the V2C file is for cannot be found on the machine.

This error may occur if:

  • You have more than one standalone dongle, and the incorrect dongle is plugged into the machine.
  • You are trying to update a network dongle plugged into a remote machine, but you are using the licence manager website for the local machine instead of for the remote machine.

Solution

If you are updating a dongle plugged into the local machine, and have more than one dongle, confirm that the correct dongle relating to the V2C file is plugged into the machine.

If you are updating a dongle plugged into a remote licence server, please ensure that you are performing the update on the correct webpage corresponding to the machine that the dongle is plugged into (check the IP address in the browser address bar).

Error message: HASP_INV_UPDATE_DATA (error code 19)

Cause

The contents of the V2C file may have become corrupted while the email that the V2C file was attached to was in transit.

Solution

Please contact us to inform us that you have received this error message. We will resend the V2C file within a ZIP file, which should reduce the risk of the V2C file becoming corrupted.


Generating C2V files

If the following error message is shown when generating a C2V file, this indicates that no dongle is plugged into the local computer.

RUS tool window

If you are attempting to generate a C2V file for a network dongle plugged into a remote licence server computer, this is not possible - you will need to generate the C2V file on the remote licence server computer itself (e.g. using a RDP session, or directly on the computer).

If you have any other issues when generating a C2V file, please let us know by replying to the email sent by the Bladed support team.


Licence manager log files

The licence manager has options to write access and error log files. When using a network licence, repeat the steps below on both the client and licence server machines.

  1. Open http://localhost:1947/_int_/config.html
  2. Set logging options as shown:

    Licence manager log settings

  3. Reproduce the problem.
  4. Inspect log file(s) with the most recent datetime stamp in C:\Program Files (x86)\Common Files\Aladdin Shared\HASP\log.

Need help?

If the information above does not help to resolve your problem, please contact us for further assistance.

When contacting us, please provide all relevant details related to the problem, such as:

  • Dongle number (e.g. DT/1234) or Key ID
  • Screenshots of any error messages or other symptoms
  • Steps to reproduce the problem
  • Any relevant log files