History | Edit

Problem

During the TCP floating license activation process, the license key becomes bound to a particular license server deployment. This means that a code that uniquely identifies your license server deployment (called Machine Signature) is sent to the Oxygen XML Editor servers, which in turn will sign the license key. The Machine Signature is computed from the list of network interfaces of the machine where you deployed the floating license.

Cause

When starting the license server, if you receive an error stating that your server's Machine Signature does not match the one found in your license key, there are several possible causes:
  • You have moved your floating license key to a new machine that hosts your license server.
  • You have changed, added, or activated a new network interface in the machine that hosts your license server.
    Note: A specific example of when this could happen, is if you activate/deactivate the Bluetooth module or the WiFi module.

Solution

Revert back to your previous configuration or if this is not possible, contact our support team.