Known Issue: "WriteFileEvidence - Insert unmatched evidence" import writer may fail due to NewFileEvidence_MT.FileEvidenceID identity column value reaching limit of 2^31 (IOJ-2082391)
Known Issue: "WriteFileEvidence - Insert unmatched evidence" import writer may fail due to NewFileEvidence_MT.FileEvidenceID identity column value reaching limit of 2^31 (IOJ-2082391)
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 FileEvidenceID identity column in the NewFileEvidence_MT 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 NewFileEvidence_MT table:
SELECT IDENT_CURRENT('dbo.NewFileEvidence_MT') 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).
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.
