Having trouble activating your CloverDX products? Here are some common issues you might encounter:

• Corrupted license file or incorrectly pasted text
• Mismatched product type
• Incompatible license version
• License expiration and future validity
• Incompatible Java version

Corrupted license file or incorrectly pasted text

When loading a license file: Ensure the license file you're loading isn't damaged. Try obtaining a fresh copy from the Customer Portal.

When pasting license contents: Double-check that the entire license is pasted correctly (it needs to include the header part as well as the part between "BEGIN LICENSE" and "END LICENSE"). Don't miss any part or add extra characters during copying.

Mismatched product type

Make sure that you use an appropriate license for the respective product. You can tell which product a license is intended for by opening the license and reviewing the Products section:

• A Designer license can be loaded only into CloverDX Designer. 
• The following licenses can be loaded only into a CloverDX Server environment:
  • Server license
  • Wrangler license
  • Data Manager license

Example of an incompatible license in CloverDX Server due to mismatched product types. 

Incompatible license version

CloverDX licenses are backward compatible but not forward compatible. This means you can use a license for an older version, but not a newer one. For example, a 6.5 license will work for version 6.5 and all older versions, but it cannot be loaded into version 6.6. 

When upgrading CloverDX products, you'll need a license valid for the version you are upgrading to or a newer one. Licenses downloaded from the Customer Portal are always valid for the latest released version and work for all prior versions.

Example of an incompatible license in CloverDX Server due to mismatched versions (CloverDX Server is version 6.6 while the license is for version 6.5):

License expiration and future validity

Expiration dates: Licenses include their expiration dates. An expired license cannot be used to activate  CloverDX products. If your licenses have been extended in the meantime, ensure that you download the latest license version from the Customer Portal.  

Validity start dates: Some licenses might have a future activation date (see the Valid from date). In this case, the license will be loaded but won't be active until the specified date.

Incompatible Java version

Ensure that your instances of CloverDX Server and Designer run on supported JDKs appropriate for your CloverDX version. Using a different JDK vendor or JDK version might result in license activation issues. 

Example of license issues when running CloverDX Designer on an unsupported JDK - in this case the license is valid but it is not accepted due to Java incompatibility. 

Server environment

For Server JDK requirements in CloverDX version 6.6. or newer, refer here. For version 6.5.0 or older, refer here.

For the easiest way to see the used JDK version and vendor in CloverDX Server, navigate  to Configuration > System Info > JVM tab in the Server Console.

To change the JDK, update the path of the JAVA_HOME system variable to point to a supported JDK.   

Designer

CloverDX Designer is by default installed with a supported JDK version. If you choose not to install it, the Designer will use the Java defined by the JAVA_HOME system variable. If this Java is unsupported, you will receive the following error upon startup in CloverDX version 6.6. or newer. 

For Designer JDK requirements in CloverDX version 6.6. or newer, refer here. For version 6.5.0 or older, refer here.

To resolve this situation, pick on the the solutions below:

• Uninstall the instance of CloverDX Designer and install it again with the recommended JDK. This will also change the runtime JDK to the correct version. 
• Change the JDK specified in the JAVA_HOME system variable. In this case also double-check that the runtime JDK was changed: navigate to Window > Preferences > Java > Installed JREs and double-check that it points to the correct JDK instance. If it does not, you can follow the steps in our documentation to change it. 
• Locate the CloverDXDesigner.ini file in the Designer install directory. Edit it and add the -vm argument to it, pointing to a path with the recommended JDK. After making this change, double-check if the runtime JDK was changed accordingly - you can follow the same steps described in the solution above. 

If the above-listed steps don't resolve your issue, contact CloverDX support at support@cloverdx.com or by logging a ticket for further assistance.