You are currently offline, waiting for your internet to reconnect

Unable to import a license into the Opalis Integration Server License Manager

This article has been archived. It is offered "as is" and will no longer be updated.

When attempting to import a license into the Opalis Integration Server License Manager, one of the following issues may occur:

  1. The license may seem to import correctly, however, when attempting to connect to components, various error messages may occur.  When connecting the Opalis Integration Server Client to the Opalis Integration Server Management Server the following error message appears:
    “The license for Opalis Integration Server is missing or invalid.  Use the License Manager utility to configure your licenses.”

    In Opalis Integration Server Deployment Manager, when selecting an Action Server, the log entry displays the following error:

    "Enumeration of Action Servers failed. Class not license for use."

  2. An error message appears that includes correct license details, but displays one or more of the following error messages in the licensing details:
    “Invalid key or license”
    “ClientProtector internal failure”
    "The main license was not found"

Outlined below are known causes for varying errors to occur when importing a license file:

  1. The license file provided has become corrupt in transit.
  2. License Manager will not successfully import a license file from a UNC path.
  3. The LICENSES table already has an entry that matches the license key provided (GUID).
  4. The Management Service is using an account that does not have appropriate permissions.
  5. The License Manager is not able to recreate the <GUID>.lic file in one or more of the following folders:

    "C:\Program Files\Opalis Software\Opalis Integration Server\Action Server"
    "C:\Program Files\Opalis Software\Opalis Integration Server\Management Service"

    This failure to recreate the <GUID>.lic file is a result of the <GUID>.lic is currently in use and as a result is locked.
  6. The license key has been incorrectly entered.
  7. Incorrect permissions have been applied to the license file. The user account executing the License Manager must have the ability to modify the license file as the License Manager does a "touch" to the file after importing.

Resolution 1

Contact Microsoft Technical Support to have the license file archived in a ZIP file and sent to you.  If any data is lost in transmission the CRC value of the ZIP file will be compromised and it will be evident. If the file is intact when it arrives, then the license file is confirmed to have transmitted successfully.

Resolution 2

Ensure that the license file is stored locally on the Management Server and attempt to import the license again.

Resolution 3

Inspect the LICENSES table and, if there is an entry currently in the table under ProductID that matches the license key, the record should be deleted. This can be done by executing the following T-SQL query:


Resolution 4

When installing Opalis Integration Server a user account was requested to be entered, but was not validated to ensure that the correct password was entered. If the user account does not have appropriate permissions, or if the password was not correctly entered, the result could be an inability to write the <License key GUID>.lic file.

Ensure that the user account identified in the Log On tab of the Opalis Management Service is using the correct password and has appropriate permissions. Opalis Software, Inc. recommends that this user account be a member of the local Administrators group.

Resolution 5

Determine if the <GUID>.lic file is in fact locked.  If there is an inappropriate handle locking the file, then sever the lock by terminating the offending application.

Identifying open handles can be done via a Windows Sysinternals tool called "Handle".  This tool, and instructions for use, can be found at

Resolution 6

Ensure that the license key is entered exactly as it is provided. A typo, exclusion of the "{" and "}" characters or extra characters at the end of the entered key will cause the encryption scheme to fail.

Resolution 7

Ensure the license file has Read, Write and Modify permissions defined for the user account that is executing the License Manager.

Resolution 8

Please make sure license file that you are importing is not placed in some hidden folder.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2022625 - Last Review: 12/12/2015 07:38:00 - Revision: 4.0

Opalis Integration Server

  • kbnosurvey kbarchive KB2022625