OpenLink Universal Data Access (UDA) Wiki
Documentation and guidance on installing, configuring and trouble-shooting UDA
Advanced Search
Help?
Location: / Dashboard / UdaWikiWeb / UDATroubleshootingResources / UDATroubleshootingLicensing / UDATroubleshootLicensingErrors

Licensing

Existing license key does not work

Take the following action to resolve licensing problems:

  1. If you are an OpenLink 6.0+ user, you must shut down your OpenLink License Manager before you do anything with an OpenLink license file. This service resides on the same machine as Single-Tier client drivers or Multi-Tier server components (i.e., the Request Broker and Database Agents).
  2. Remove any extraneous license files from the machine.
  3. Move the new license file into the appropriate directory. Use binary-preserving methods for any machine-to-machine transfers.
  4. Ensure that the OpenLink's Windows and Unix license directories are included in the PATH environment variable. Ensure that Unix license directories are included in an OPL_LICENSE_DIR variable.
  5. Restart the OpenLink License Manager, if you are a 6.0 or newer user.
  6. Test.

If problems persist, examine these possibilities:

  1. You need to restart your computer. This is especially true if you are a 6.0+ user and you moved license files around while the License Manager was still running.
  2. Your license does not match your OpenLink driver version. Product Support staff can check this for you.
  3. Your license does not match the number of processor cores in your machine. You must be licensed for all physical processors. If you have virtual processors such as Solaris containers, you may also have a problem, though you do not need to acquire licensure for such processors. Contact Product Support for additional information.
  4. If you have older Windows drivers, especially Single-Tier drivers, you may need to wipe your registry of references to the license. Then, you need to uninstall and reinstall the product. This is an exceedingly rare problem and is only mentioned for the sake of completeness. Do not proceed with such an undertaking without prompting from Product Support.

See Also: CPU Detection Help

Powered By Virtuoso