When performing a manual import of the content libraries the task is failing due to a failed extraction of the EOSL libraries. We are not using the EOSL libraries and I am not creating the EOSL folder under content. I only have ARL and SKU/ After the ARL tasks complete the RecognitionImportTool is beginning the EOSL tasks and attempting to extract the EOSL cab file. It creates a temp-extract file and then fails.
Is there a way to force the tool to disregard the EOSL task and move to the SKU and PURL import?
@dbeckner - Go ahead and create the folder named C:\ProgramData\Flexera Software\FlexNet Manager Platform\DataImport\Content\EOSL. Just do not put the EOSL.cab file into this folder. Your ARL import should run now and no EOSL data will be imported.
Hi @kclausen It looks like the issue is that the customer is licensed for the EOSL library so the process expects the library to be there. Once I get those added in I am confident it will work. Thanks for the response.
