Machine Signature Mismatch Error
Edit online

Problem

I receive an error indicating that the current license was already activated on a License Server or that the License Server's Machine Signature does not match.

During the 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 plugin 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 license.

Causes

When starting the license server, if you receive an error stating that your server's Machine Signature does not match, there are several possible causes:
  1. The license key was moved to a new machine that hosts your license server.
  2. A new network interface was changed, added, or activated in the machine that hosts your license server.
    Note: A specific example of when this could happen is if the Bluetooth or the WiFi module is activated/deactivated.
  3. The license server was restarted from a different location as the previous restart. For example, some server configurations will have the Apache Tomcat server installed in a versioned folder (/usr/local/apache-tomcat-V.V.V) with a symbolic link to the typical folder (/usr/local/tomcat). The server can be restarted from either location, but it is recommended to always restart from the typical folder (/usr/local/tomcat) and always restarted from the same location.

Solutions

  • Revert to your previous configuration.
  • If reverting is not possible, contact the Oxygen support team.
  • In the case of the 3rd cause listed above, the server simply needs to always be restarted from the same location.