Electronic Update

Failure to remap custom versions for components (SCA-25737)

The Electronic Update fails to remap custom component versions to component versions in the Data Library (PDL). This issue occurs only when the remapping is enabled for the Update (that is, update.remap.enabled = true in core.properties).

Note that, should this issue occur, it does not cause the Electronic Update to fail. The version remap process throws an exception in the log, but the Electronic Update continues.

Workaround: You can run a script that performs the remapping once the Electronic Update completes. Refer to this KB article instructions:

https://community.flexera.com/t5/FlexNet-Code-Insight-Customer/Using-the-Custom-Data-Remap-Script-to-Remap-Custom-Versions-in/ta-p/150884 

Emails not triggered for remapped custom vulnerabilities for custom component versions associated with inventory (SCA-25844)

Normally, when a custom vulnerability assigned to a given component version is remapped during an Electronic Update and the component version is already associated with an inventory item, an email is triggered, informing users of the “new” vulnerability for the inventory item. However, if a custom vulnerability for a custom component version associated with inventory is remapped, no email message is triggered currently.

This issue will be addressed in a future release.

Unicode data on SQL Server (PAS-11158)

Some PDL columns in the FlexNet Code Insight database schema do not currently support UTF-16 characters. As a result, users may see duplicate key errors in core.update.log when running Electronic Update on SQL server. This issue has been partially addressed in the current release of FlexNet Code Insight, available as part of migration and will be fully resolved in the next release. SQL server users are advised to ignore duplicate key errors when running an electronic update.

Electronic Update buffer pool size

If you experience a failure when running Electronic Update on a MySQL or SQL Server database, ensure that the Buffer Pool Size systems is set to a minimum of 1 GB. Look for an out-of-memory error in the logs. See the Knowledge Base or contact support if you need further instructions.