Troubleshooting IPS/DS 4.x install error "The product key is not valid. INS00140"

[Former Member]

The error "The product key is not valid. INS00140" is sometimes produced on Unix/Linux platforms during the installation of BO products and  it  is most likely to be due to a missing library/libraries.

First you need to make sure that the used key is actually valid, then follow these troubleshooting steps to find out what exact libraries or their dependencies that  are missing:

(NB: if in doubt about the license key validity, use Temporary License Key, this is perpahs  more relevent  to BI platform, as IPS uses an embeded key but the latter can also be tested with the temp key).

1. cd "/<Install_media_location> /IPS/DATA_UNITS/IPS_lnx/dunit/product.minibip-4.0-core-32/actions/"  This path is   for IPS 4.1, but BI,  DS and IS should have   other path for their own license program.
2. export LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH. This sets the environment variable for the libraries required for the key validation and ‘pwd’ is meant for the path in step 1 above.
3. ldd ./isKeycodeValid. This command will list all the libraries required for this execution.
4. Run ./isKeycodeValid"  -keycode XXXX-XXXXXXX-XXXXX-XXXXXXX-XX -version 140 -property BOE.EnableBO. This validates any key for IPS and you would expect to  an error poiting to a missing library.
5. When getting an error in step 4 make a note of the library.
6. Run commad ldd <missing_library_name> to print the shared library dependencies
7. If you know that the libraries  and  their  dependencies, actually exist in a specific location, then you need to  update the $LD_LIBRARY_PATH with their path before you can perform the install.
8. Once you identify the missing libraries from the system ie. libstdc++XXXX, try to find out the package name in Linux which includes them (ask system admin or Google for the rpm name) and install it. It would most likely be a missing 32 bit libraries in a 64bit system.

If a similar error is encountered in DS:

1. Navigate to the LicenseManager path
2. ldd <Install_media_location>/dunit/product.dataservices64-4.0-core-32/actions/utilities/LicenseManager
3. The result from the above step may look like this:

linux-vdso.so.1 =>  (0x00007fff923ff000)

        librt.so.1 => /lib64/librt.so.1 (0x00007f7fa9d68000)

        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7fa9b4b000)

        libdl.so.2 => /lib64/libdl.so.2 (0x00007f7fa9946000)

        libboeim_kd_64.so => not found

        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f7fa963c000)

        libm.so.6 => /lib64/libm.so.6 (0x00007f7fa93c2000)

        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f7fa91ac000)

        libc.so.6 => /lib64/libc.so.6 (0x00007f7fa8e33000)

        /lib64/ld-linux-x86-64.so.2 (0x00007f7fa9f81000)

     4.  You can notice that libboeim_kd_64.so is  not found

     5.  On this occasion this library is found on the installation media when searched for,  so only the $LD_LIBRARY_PATH needs to be added/appended.

     6.  export LD_LIBRARY_PATH <Install_media_location>/dunit/product.dataservices64-4.0-core-32/actions/utilities/

     7. The LicenseManager/Installation would now be able to validate the key without errors.

Your comments are welcomed.

Nawfal Tazi