Back

Applying a V2C file

Bladed Knowledge Centre Help library Licensing and modules Applying a V2C file

Overview

A license is activated or updated on a dongle by applying a V2C license update file to the dongle. V2C files are sent from the Bladed support team by email as file attachments.

The procedure for applying a V2C file to a dongle depends on whether the dongle is:

  • plugged into the local machine (for standalone or network dongles) - see Section A below
  • plugged into a remote machine (for network dongles only) - see Section B below

Useful information and troubleshooting advice is also provided below.


A. Applying a V2C file to a dongle plugged into a local machine

To apply a V2C file to a standalone or network dongle plugged into the local machine:

  1. Save the V2C file to an accessible location (on the local machine or on the network).
  2. Ensure that the dongle is plugged into a spare USB port on the local machine.
  3. Navigate to http://localhost:1947/_int_/checkin.html in a web browser.
  4. Click Choose File or Select File..., select the V2C file and click Open.
  5. Click Apply File once (if the page does not immediately update, please be patient - do not click the button again, as this may result in an error).
    • If the update was successful, a confirmation message will be shown.
    • If the update was not successful, an error message will be shown - see Troubleshooting section below for further assistance.

B. Applying a V2C file to a dongle plugged into a remote machine

To apply a V2C file to a network dongle plugged into a remote machine (i.e. not plugged into the client machine that you are performing this operation on):

  1. Save the V2C file to an accessible location (on the local machine or on the network).
  2. Navigate to http://localhost:1947/_int_/devices.html in a web browser - this shows any local and remote dongles that are visible on the client machine.
  3. Find the dongle that you wish to update - the name of the server is shown in the Location column. Click the Browse button in the Actions column to open the license server configuration page in a new tab – perform the remaining steps in this new tab.
  4. Click Update/Attach in the left-hand menu.
  5. Click Choose File or Select File..., select the V2C file and click Open.
  6. Click Apply File once (if the page does not update immediately, please be patient - do not click the button again, as this may result in an error).
    • If the update was successful, a confirmation message will be shown.
    • If the update was not successful, an error message will be shown - see Troubleshooting section below for further assistance.

Please note that you can also apply a V2C file to a dongle plugged into a remote machine by connecting to the machine using a remote desktop (RDP) session and following the instructions in Section A above.


Useful information

  • Applying a V2C file only updates the license on the dongle itself - it does not update the machine that the dongle is plugged into. If you wish to move the dongle into a different machine, it is not necessary to apply the V2C file again.

V2C troubleshooting

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 license is already up-to-date:

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

If the license 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 license is up-to-date, and send a further pair of V2C files to reset the license 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 license is up-to-date, and send a further pair of V2C files to reset the license 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 license 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 license 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.


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