3923

How to resolve error “CLLFloatingLicenseInitialize failed to start the license thread”

Note: Multi-user systems are not tested by L3Harris and therefore are not officially supported.

Cause:
If one of the following errors occur on a multi-user system, the below workarounds can be tested to fix the license issue.


Error Message:
Trusted storage is corrupted. : Trusted storage is corrupted. (code : 1879048229)
(null): [1,7e3,2,0[74100008,1,1202014d]] Internal. : Internal. (code : 1947205640)
(cll_internal.cpp : 495) (code : 1947205640) (CLLFloatingLicenseThread.cpp : 470)
CLLFloatingLicenseInitialize failed to start the license thread.
Unable to obtain an IDL license.


Solutions:
1) If the machine is not hosting local licenses and is client of a license server, delete all files inside the following flexera folders:
Windows:
C:\Program Files\Harris\license\flexera
C:\Program Files\Harris\license\flexera-sv

Linux/Mac:
/usr/local/harris/license/flexera
/usr/local/harris/license/flexera-sv

The files inside these folders can be hidden, so be sure the system file explorer is showing hidden items. (View > show hidden Items)
After deleting the files, try again to start ENVI/IDL on the client machine.
If the problem persists, try the next step.



2) Delete all files starting with “cllshm...” inside the following license folder: 
Windows:        C:\ProgramData\Harris\License
Linux:               /tmp/Harris/License

These folders and files can be hidden, so be sure the system file explorer is showing hidden items. (View > show hidden Items)
After deleting the files, try again to start ENVI/IDL on the client machine.
If the problem persists, try the next step.



3) Check needed permissions:
All users needs the following permissions on the following folders and files:

Permission 755 or 777 on below folder:
Windows:       C:\Program Files\Harris\license
Linux:             /usr/local/harris/license

Permission 777 on below folders:
Windows:       C:\Program Files\Harris\license\flexera
                       C:\Program Files\Harris\license\flexera-sv
Linux:             /usr/local/harris/license/flexera
                      /usr/local/harris/license/flexera-sv

Permission 666 on files started with “amd…” in the below folders
For example: 
Windows:       C:\Program Files\Harris\license\flexera\amd…
Linux:             /usr/local/harris/license/flexera/amd…


Permission 777 on below folder and the files inside this folder:
Windows:       C:\ProgramData\Harris\license
Linux:             /tmp/Harris/license

Additional Information can be found on the following Help Article:
https://www.l3harrisgeospatial.com/Support/Self-Help-Tools/Help-Articles/Help-Articles-Detail/ArtMID/10220/ArticleID/19874/INTERNAL-review-Error-Failed-File-Open-when-attempting-to-Activate-ENVI-54-or-IDL-86
If the problem persists, try the next step.


4) Try to move both flexera folders to a different directory than the default one:
If the above permissions cannot be set for both flexera folders in the default directory, or if there are conflicts when multiple users are accessing and writing in those folders at the same time, try moving both folders to another custom directory using the following workaround:
https://www.l3harrisgeospatial.com/Support/Self-Help-Tools/Help-Articles/Help-Articles-Detail/ArtMID/10220/ArticleID/21289/How-to-move-flexera-and-flexera-sv-folders-to-a-different-directory-than-the-default-one


5) Disable new Systemd protection on newer Linux operating systems
New Linux Operating Systems can have extra Systemd protection that makes files inside the /tmp directory read-only for certain users, which will lead to additional issues for some programs. This protection can cause read/modify issues with the file starting with fne.xxx in the /tmp directory. The following steps can help:

1) If available, delete the fne.xxx file in the /tmp directory and try to start the program again.

2) Deactivate the extra Systemd protection with the following terminal command:
   sysctl fs.protected_regular=0

Additional Information can be found in the below external links:
- https://www.phoronix.com/scan.php?page=news_item&px=Systemd-241-Linux-419-Sysctl
- https://itectec.com/ubuntu/ubuntu-user-root-cant-write-to-file-in-tmp-owned-by-someone-else-in-20-04-but-can-in-18-04/
- https://unix.stackexchange.com/questions/503111/group-permissions-for-root-not-working-in-tmp

It may be possible that you need to manually delete the fne.xxx file again, after turning off the extra protection. Afterwards, each user should be able to start ENVI/IDL again.

 

________________________
Created by MT, 05/05/2021, Reviewed by BC, 05/10/2021

SIGN UP AND STAY INFORMED

Sign up to receive the latest news, events, technologies, and special offers.

SIGN ME UP