Knowledge Base

KB #240134: Error message: The current license has failed validation.

Type:

Information.

Summary:

When launching the Main Menu or “License Management” dialog , you receive a message that the current license has failed validation. This is may be because you have a license that is tied to the machine fingerprint, and there has been a significant enough change that invalidates the license. This article provides methods to remedy your license.

Additional Information:

Encryptionizer licenses are tied to the machine on which they are installed. A significant change can invalidate the license. An invalidated license could result in Encryptionizer not properly functioning, including inaccessible encrypted data from your secured applications or services.

You may be able to remedy your license by deactivating the license via the License server and then reactivating it, if you have deactivations remaining on your license. Launch the License Management dialog from the Main Menu, and follow the instructions to deactivate the license.

Once deactivated, you may return to the License Management dialog to activate the same license if you have activations remaining.

If you are not able to use the same License ID, use one of your Temporary Licenses that you can find in your License portal (https://netlibsecurity.com/license).

Why did my machine fail validation?

Our licensing software is tied to hardware characteristics. If portions of the hardware appear to change, the license may fail validation. This is more likely to happen on Virtual machines if they change host machines, are cloned or have other changes to their “hardware characteristics”.

You might notice that the NetLib Encryptionizer Key Management service is running and your databases are online, but when you run one of the GUI’s (Main Menu, License Management, etc) you receive this message.  This is a known issue with older verssions of our software which has been fixed. The user interfaces in our older versions of our software were stricter on the hardware fingerprint checks than the drivers which perform the transparent encryption activities.
In our newer versions of our software (2311.1.4.31103, released Dec 2023 and later) the UI and driver hardware checks are coordinated and use the same criteria. This issue is much less likely to happen. If you have not done so, we recommend updating to the latest version available in your License Portal.

If you are not able to reactivate your software, contact NetLib Security Support (https://netlibsecurity.com/support)

Related Topics:

KB #240102: Encrypted Databases not accessible

Last modified: 12/11/2024