Summary
Changes that stop file evidence from being collected from Windows operating system directories may result in a one-time only performance impact during the first full inventory import after completing the upgradeSynopsis
When upgrading from FlexNet Manager Suite prior to release 2015 R2 SP4 to release 2015 R2 SP5 or later, the time taken to perform the first full inventory import may be impacted due to a change made that stops file evidence from being collected from Windows operating system directories. The clean-up task may take a noticeable amount of time ( possibly hours).You may also experience a LOCK error during the compliance import, for example:
2016-07-05 09:10:53,167 [INFO ] Failed to execute Reader 'DeleteFromImportedInstalledFileEvidence' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\sms\FileEvidence.xml
Error: The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
2016-07-05 09:10:53,167 [INFO ] All retries have been attempted for Reader 'DeleteFromImportedInstalledFileEvidence'
2016-07-05 09:10:53,167 [INFO ] Completed with error in 27 minutes, 29 seconds.
2016-07-05 09:10:53,167 [INFO ] Released application lock Reader_d9928d3c-9c28-4e88-846a-3be06e40c5d5_Evidence_ALL
2016-07-05 09:10:53,542 [ERROR] System.Data.SqlClient.SqlException (0x80131904): The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
Discussion
File evidence in the Windows operating system directories do not represent licensable applications. The change was introduced to reduce the importer times and to reduce the load on the database. This is achieved by restricting the imported evidence for the path :\Windows%Due to the amount of collected inventory data, that the server will need to discard, a one-time only performance impact may be experienced. The time of this impact will vary based on the amount of file evidence previously collected from these directories along with the speed of the database server.
Workaround
If you experience the LOCK, the issue is happening because a lot of file evidences that are not used for recognition, need to be deleted. After the deleting process has finished, imports will be faster than they were before. To allow the deleting process to succeed and to avoid the exception, please run the attached sql script, this will reduce the batch size.If it doesn't help, try to run the file with even smaller batch size (just change @BatchSize variable in the sql and run it again)
Before running the script please create database backup 