cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

End of lif library update checking


Hello Experts,


Our FNMS is 2019-R2 On-Prem. I would like to check if we have latest EOL library imported.
EOSL-Recognition.log shows below:
------------------------------------------------------------------------------------------------------------------------
5/26/2020 11:13:57 AM :D:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport\ArlContent\EOSLStagingSoftwareTitleData.dat: successful extraction!
5/26/2020 11:13:57 AM :EOSL update is ready to be executed. This process may take from several minutes to several hours.
5/26/2020 11:13:58 AM :Detecting and updating existing EOSL dates
5/26/2020 11:13:58 AM :
5/26/2020 11:13:58 AM :***********************************************************************
5/26/2020 11:13:58 AM :Database collation is: SQL_Latin1_General_CP1_CI_AS
5/26/2020 11:13:58 AM :This EOSL (version 357) is already installed. Updating will not be done.
5/26/2020 11:13:58 AM :
5/26/2020 11:13:58 AM :
5/26/2020 11:13:58 AM :The command: sqlcmd.exe -S ZNWDBCDP05052V -d FNMSCompliance -b -i "D:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport\ArlContent\EOSLUpdate.sql" -E
5/26/2020 11:13:58 AM :was executed. Please check the log for possible error messages.

-----------------------------------------------------------------------------------------------------------------------
In the FNMS System Health Dashboard, the version of SKU library is 454 and the version of PURL is 450.

Does the log state we have imported the latest EOSL (version 357) in FNMS?


Should the version EOSL library be same as the version of PURL Library?


Is the EOSL log file in temp folder only place that I can check if it imported successfully?

 

 

 


Thanks!

(1) Solution

Hi @HPNZNB ,

 

The latest build released for EOSL is 357 and hence can confirm that your FNMS has the latest build of EOSL imported. 

The build number for EOSL is not same as SKU or PURL. To keep yourself updated with each release, please subscribe to https://community.flexera.com/t5/FlexNet-Manager-Content-Release/bg-p/FlexNet-Manager-Content-Release-Blog

Updates w.r.t EOSL can be found along with ARL release blog. For ex: https://community.flexera.com/t5/FlexNet-Manager-Content-Release/FlexNet-Manager-Update-Application-Recognition-Library-2517-and/ba-p/148694

 

To check for successful import of EOSL cab file, one other way is by querying the database. If you have access to DB, please check EOSLImport table.

 

Thanks,

Shabina  

View solution in original post

(1) Reply

Hi @HPNZNB ,

 

The latest build released for EOSL is 357 and hence can confirm that your FNMS has the latest build of EOSL imported. 

The build number for EOSL is not same as SKU or PURL. To keep yourself updated with each release, please subscribe to https://community.flexera.com/t5/FlexNet-Manager-Content-Release/bg-p/FlexNet-Manager-Content-Release-Blog

Updates w.r.t EOSL can be found along with ARL release blog. For ex: https://community.flexera.com/t5/FlexNet-Manager-Content-Release/FlexNet-Manager-Update-Application-Recognition-Library-2517-and/ba-p/148694

 

To check for successful import of EOSL cab file, one other way is by querying the database. If you have access to DB, please check EOSLImport table.

 

Thanks,

Shabina