Q100526: "Invalid SystemID" and "Wrong host for license" error messages

SUMMARY

A license will only work if the System ID it is generated for is a valid System ID for the machine it is installed on. 

 

MORE INFORMATION

Attempting to use a license with an invalid System ID will produce an error message in the application or prevent a license server from running.

The Foundry Licensing Utility (FLU) will only install licenses for System IDs that are valid for the machine it is running on.

 

Error message within an application

If an application can only find a license with an invalid System ID, it will fail to launch and show an error message saying "wrong host for license" in the Status window of the applications licensing dialog.

invalidID_nuke.png

 

 

Error message from the Foundry Licensing Utility (FLU) 

If you try to install a license with an invalid System ID the FLU with report that the license is invalid due to having a different System ID. 

InvalidID_FLU_install.png

 

If you pass the FLU multiple licenses to install it will install any valid licenses (such as those with valid System IDs) and produce a warning message for any invalid licenses.

Error message from RLM Server log

If you try and float a server license for an invalid System ID the server log will include a message that the license is "not on this host".

06/07 15:20 (foundry) Settings from RLM Version 10.1BL2 for ISV "foundry"
06/07 15:20 (foundry) Server architecture: x64_m1

Copyright (C) 2006-2017, Reprise Software, Inc. All rights reserved.

RLM contains software developed by the OpenSSL Project
 for use in the OpenSSL Toolkit (http://www.openssl.org)
 Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
 Copyright (c) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved.

06/07 15:20 (foundry) ****************************************
06/07 15:20 (foundry) /Library/Application Support/TheFoundry/RLM//foundry_float.lic: not on this host

 

NEXT STEPS

If you encounter one of the error messages above, it is most likely due to one of the following scenarios:

  1. Your license is supposed to work on your machine, but your System ID has changed.
  2. You are attempting to install your license on a different machine than the license was generated for.

In both of these scenarios, the first thing to do is to check what your System ID is on the machine you're attempting to install the license on. The easiest way to check your System ID is to use the FLU, which you can download from here:

https://www.foundry.com/licensing/tools 

We discuss how to locate your System ID in more detail here:

Q100002: What is the System ID and how do I find it?

Once you have found what your System ID is, you will now need to cross-reference it with your license. If the System IDs don't match, then please see the following steps:

  1. Firstly, please try to disable randomized MAC addresses following this article: 
    Q100704: Disabling randomized MAC addresses for Foundry licenses

    Please note that you will have to restart your machine for this to take effect. After restarting, please try to install your license again.
     
  2. If this did not work, you may have to transfer your license's System ID to your machine's System ID. To begin this process, please see the following article: 
    Q100001: How can I transfer my license to another machine, change license types or migrate to Login licensing
     
  3. If you continue to encounter issues, please raise a support ticket. Please attach a diagnostic file from the FLU on your machine to the support ticket so that we can check the licensing setup of the machine.
    Q100105: How to generate a license diagnostic log via the FLU for troubleshooting license issues
    Q100064: How to raise a support ticket

     

FURTHER READING

For more information about licensing please see the Foundry Licensing Online Help

Information about the System ID, installing licenses and install errors messages is available in the following articles:

 

    We're sorry to hear that

    Please tell us why