Invalid License Key error message

This article applies to:
Briefcase for Windows and Email Manager for Outlook
6.x Briefcase for Windows, Contributor Pro and Email Manager for Outlook

There are two instances where you may see an invalid license key error.

1. During installation

You may see the following message:

This is often the result of trying to install version 6.x with a version 5.x or 4.x license key.

2. On application launch

You may see the following message:

This is often the result of Briefcase for Windows or Email Manager for Outlook being unable to correctly read the license key from the registry. There are two ways to resolve this.

  1. You can run the program as Administrator by right-clicking the Briefcase for Windows icon and clicking Run as administrator.
  2. You can move your license key information in the registry from HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER. Below are instructions on how to move your license key location:
    1. Open your registry and browse to:
      HKEY_LOCAL_MACHINE\SOFTWARE\Colligo\Contributor (If using 32-bit Windows)
      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Colligo\Contributor (If using 64-bit Windows)
    2. Re-create the same two keys seen above at the following location: HKEY_CURRENT_USER\Software\Colligo
      Right-click the open space on the right and select New > String Value.

      Name the first key: LicenseKey6.0.
      Name the second key: InstallationDir
    3. Browse to HKEY_CURRENT_USER\Software\Colligo and copy both the values of LicenseKey6.0 or LicenseKey7.0 and InstallationDir to their new location in HKEY_LOCAL_MACHINE. (See https://support.colligo.com/support/solutions/articles/16000009393-installation-path and https://support.colligo.com/support/solutions/articles/16000009394-license-key for more information about these keys)

      Once these two keys have been recreated in their new location, launching the application should no longer cause the Invalid Product License Key error message to display.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.
Have documentation feedback? Send us an email