Symptoms
There could be any number of reasons for an ARL update failure. The first place to check is at the end of the recognition.log file which resides in either of the following directory locations -1. If the ARL scheduled task is set to run under the SYSTEM account -
C:\Windows\Temp\
2. If it's set to run under a specific user or domain account -
C:\Users\<username>\AppData\Local\Temp
There are some instances where the failure can occur prior to anything being written to this log file. If this is the case, you'll need to run the ARL updater executable manually from the a command line in order to capture the error message. It can be launched without any additional command parameters -
"X:\Program Files (x86)\ManageSoft\DotNet\bin\MgsImportRecognition.exe"
See below if this process returns the following error message -
'Command could not be executed - make sure SQL Client Tools are installed at Core Server'
Resolution
If the 'SQL Client Tools' error message is returned, check to see if the Recognition.exe file exists in the DotNet\bin folder. If it is not, please contact technical support so that they can supply you with the appropriate version of this file.Was this helpful?
Related Articles
The installed application recognition library (ARL) is incompatible with this release of FlexNet Manager Platform 5Number of Views Where can I access end of support life (EOSL) data for applications in the application recognition library (ARL)? 7Number of Views Why some SQL Server components such as Reporting Service / Integration Service / Analysis Service are classified as Commer… 8Number of Views Compliance Import fails with the error "Cannot open database "<Databasename>" requested by the login. The login fail… 29Number of Views Imported file evidence and application recognition results may fluctuate over time if inventory NDI files contain both pro… 14Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago