You are not licensed to use this DataDirect Technologies product under the license you have purchased
search cancel

You are not licensed to use this DataDirect Technologies product under the license you have purchased

book

Article ID: 384379

calendar_today

Updated On:

Products

VMware Tanzu Data Suite Greenplum VMware Tanzu Greenplum Pivotal Data Suite Non Production Edition VMware Tanzu Data Suite

Issue/Introduction

License error occurs with a Connect for ODBC driver 15 days after installation with a license key:

SQLSTATE = S1000
NATIVE ERROR = 6060
MSG = [DataDirect][ODBC SQL Server Native Wire Protocol driver]You are not licensed to use this DataDirect Technologies product under the license you have purchased. If you wish to purchase a license for use with this application, then you may use this product for a period of 15 days, during which time you are required to obtain a license.

SQLSTATE = S1000
NATIVE ERROR = 6062
MSG = [DataDirect][ODBC SQL Server Native Wire Protocol driver]You can order a license for a DataDirect Technologies product for use with this application by calling DataDirect Technologies at 800-876-3101 in North America and +44 (0) 1753-218 930 elsewhere. Thank you for your cooperation. Reason Code: 000000000000000000000001

Cause

  • File does not exist.
  • User or group has no permissions to access the file
    e.g. License file only has permissions -rwx---r-x. (i.e.: where a user running the application has group permissions to the driver directory, but the license file has no read permission for group)
  • Driver is not on library path
  • The license file found by the driver was a previously existing license file for an older product version.
  • Misspellings in the library path

Resolution

Note: To get the DataDirect License Key for use with Grennplum Database see "DataDirect ODBC Drivers for VMware Greenplum" in the Greenplum documentation.

Other steps which may help:

  • Ensure the license file exists.
  • Ensure the user / group has read permissions on the license file so all users can read it.
  • Ensure the directory containing the ODBC driver is first on the library path (LD_LIBRARY_PATH on Solaris and Linux, LIBPATH on AIX, SHLIB_PATH on HP)
  • Ensure the library path contains no misspellings.