Error: The license transfer cannot be confirmed

Error: The license transfer cannot be confirmed

Errorcode 0x18080010


The following error message is displayed in the license web depot if the license transaction is intercepted by a second license transaction and therefore the license confirmation file cannot be processed.
WarningError
The license transfer cannot be confirmed
Please check whether all current license updates have been imported and use the current license confirmation file. You can download the license updates again under "Continue License Transfer". Import it, create a new license confirmation file and try it again.

What could be the reason?

The customer is trying to activate two or more licenses at once with the file based offline web depot license activation process.
  1. Customer creates license request file for license 1 for dongle A.
  2. Customer creates license request file for license 2 for dongle A.
  3. Customer uploads first and second license request file and downloads the license update file
  4. Customer imports both license update files in the license manager and creates a license confirmation file for each.
  5. Customer uploads license confirmation file for license 1 - everything works fine
  6. Customer uploads license confirmation file for license 2: error message is displayed.

Dongles in unexpected state

Following the procedure described above could lead to an 'unexpected state' of the dongle. This causes tremendous problems in updating the license and/or deleting the license.

Imagine the license process like this: the customer uploads an individual fingerprint with the license request file. Based on that fingerprint, the license central calculates the license update and sends out the license update file. Based on the license update file, the license central already knows how the dongle should look like. The customer sends then the confirmation file to tell the license central the actual state of the dongle. If the pre-calculated state and the confirmed state correlate, everything is fine. 
If however the license confirmation does not match the pre-calculated state for that dongle, the dongle is set to a so-called 'unexpected state'.
The license central does not know if it should 'trust' the state of the customer dongle sent with the confirmation file or if it rather uses the calculated state and the customer messed around with the software dongle (internally, the state is called 'manipulated')
Additional reasons for the unexpected state could be (list might not be complete):
  1. customer performs two license activations at once.
  2. customer uses an old confirmation file.
  3. customer resets the PC or virtual machine to a previous state.
















Follow up problems:

Now it really gets bad.
When updating a license the process foresees that the existing licenses on that dongle are withdrawn first. That means that the license central calculates backward to set the dongle to a state where the license was not even on the dongle. But as the current state of the dongle is unknown, this state cannot be calculated.
The license update process is interrupted. The license which should replace the initial license is not created.
This also applies to the license deletion. A license deletion is basically a license withdrawal without the creation of a replacement license, the license deletion can also not be performed.

    • Related Articles

    • Unexpected State detected for License dongles

      The license central indicates an unexpected state for a certain dongle if the state of the dongle - given in a license request or license confirmation file - does not match that one which is calculated by the license central. A reason for this can be ...

    • Checklist: It is not possible to activate a license

      Time estimate: 15 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • License activation with Powershell scripts

      The LicenseManagerAutomation.exe can be used to activate licenses via a powershell script. This works online and offline. The online activation is described in the help of the license manager automation and very easy to implement. For the offline ...

    • License Borrow - Unknown Error - Push in Transit

      A customers has problems with returning a loaned / borrowed license. The customer cannot return the borrowed license although the loan period is not exceeded. An "Unknown Error" is displayed. Get a CmDust log file. Search the CmDust log File for the ...

    • Checklist: Component cannot find the license

      Time estimate: 15 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...