- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Suite Known Issues
- :
- Known Issue: FileEvidenceFile.FileEvidenceFileID 32 bit INT identity column in compliance database m...
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Known Issue: FileEvidenceFile.FileEvidenceFileID 32 bit INT identity column in compliance database may run out of values, causing "WriteFileEvidence - Insert unmatched evidence" import writer to fail (IOJ-1898355)
Known Issue: FileEvidenceFile.FileEvidenceFileID 32 bit INT identity column in compliance database may run out of values, causing "WriteFileEvidence - Insert unmatched evidence" import writer to fail (IOJ-1898355)
Summary
On FlexNet Manager Suite systems where a large volume of unique filenames have been imported, the “WriteFileEvidence - Insert unmatched evidence” inventory writer step may fail due to the FileEvidenceFileID identity column in the FileEvidenceFile table in the compliance database growing too large and running out of available values.
Details
When this issue occurs, inventory imports are likely to fail with an error similar to the following:
2019-11-15 06:57:00,735 [INFO ] WriteFileEvidence - Insert unmatched evidence 2019-11-15 07:00:24,730 [INFO ] Failed to execute Writer 'WriteFileEvidence - Insert unmatched evidence' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\\Writer\FileEvidence.xml, at step line 108 Error: Arithmetic overflow error converting IDENTITY to data type int. Arithmetic overflow occurred.
The following SQL query can be executed against the compliance database to identify the current identity value in the FileEvidenceFile table:
SELECT IDENT_CURRENT('dbo.FileEvidenceFile') AS CurrentIdentity
This issue is likely to occur if the value returned by this query is at or near 2,147,483,647 (being the maximum value that can be stored in a SQL Server INT value).
Mitigation
This issue may be mitigated by executing the following SQL query against the compliance database to reseed the FileEvidenceFile table to use negative identity values:
DBCC CHECKIDENT('dbo.FileEvidenceFile', RESEED, -2147483647)
Note that this mitigation can only be done once. If this mitigation has been previously applied and the database has continued to grow such that all negative identity values have been subsequently used then imports are likely to start to fail again.
Related issue
Also see the following issue which can result in the same symptoms as this issue, but with a different root cause: NewFileEvidence_MT.FileEvidenceID 32 bit INT identity column in compliance database may run out of values, causing "WriteFileEvidence - Insert unmatched evidence" import writer to fail (IOJ-2082391).
Fix status
This issue is still open but not currently scheduled to be addressed.
Other information
Affected components: Database, Inventory import (read/write/export)
Master issue ID: IOJ-1898355
Also known as: FNMS-63615
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.