The “Calculating consumptions for licenses from devices with history” step in the license import process may fail after an application that is installed on an ignored device is unlinked from a license record that has an IBM-related license type.
When this issue occurs, the license reconcile log will show error details similar to the following:
2022-05-04 20:25:00,775 [INFO ] Calculating consumptions for licenses from devices with history. 2022-05-04 20:25:01,043 [INFO ] Loaded 29625 ComputerResourceData records 2022-05-04 20:25:12,391 [ERROR] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null. at ManageSoft.Compliance.Database.API.ReconcileTemporalInstalledSoftware.set_Item(String p_Field, Object value) at ManageSoft.Database.API.DatabaseObject.FillFrom(DatabaseDataReader p_Reader) at ManageSoft.Database.API.DatabaseObject.ReadFrom(DatabaseDataReader p_Reader) at ManageSoft.Compliance.Importer.Procedures.ManageSoft.DatabaseObjectEnumerator`1.<GetEnumerator>d__1.MoveNext() at ManageSoft.Compliance.Importer.Procedures.ManageSoft.ILMT.SoftwareEventStream.NextInstallation() at ManageSoft.Compliance.Importer.Procedures.ManageSoft.ILMT.SoftwareEventStream.<GetEnumerator>d__5.MoveNext() at ManageSoft.Compliance.Importer.Procedures.ManageSoft.ILMT.HistoricalEventStream.<GetEnumerator>d__5.MoveNext() at ManageSoft.Compliance.Importer.Procedures.ManageSoft.ILMT.PVUProcessorHelper.ProcessHistory() at ManageSoft.Compliance.Importer.Procedures.ManageSoft.ILMT.PVUProcessorHelper.Begin(Int32 licenseMeasurementID) at ManageSoft.Compliance.Importer.Procedures.ManageSoft.LicenseReconcile.ReconcilePVULicenses(Int32 licenseMeasurementID) at ManageSoft.Compliance.Importer.Procedures.ManageSoft.LicenseReconcile.LicenseReconcileCalculate(Int32 p_LicenseMeasurementID) at ManageSoft.Compliance.Importer.Procedures.ManageSoft.LicenseReconcile.ReconcileLicensesCalculate() --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture) at ManageSoft.Compliance.Importer.Logic.XML.ProcedureItem.ExecuteAssembly(IExecutionContext context) at ManageSoft.Compliance.Importer.Logic.XML.Writer.Execute(IExecutionContext context) at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ExecuteWriters(ComplianceReader p_ComplianceReader, IExecutionContext context, String singleConnectionIdentifier)
See the following page for an issue with a different root cause that can result in similar error logging to what is seen for this issue: "Calculating consumptions for licenses from devices with history" license reconcile step may fail with error when running IBM-specific reconcile after removing non-IBM titles from a license: "System.ArgumentNullException: Value cannot be null." (IOJ-2225722)
This issue has been fixed in the following FlexNet Manager Suite releases: 2022 R1.4 / Aug 2022 (Cloud), 2022 R2 (On Premises)
Affected components: Inventory import (read/write/export), SAM for IBM
Master issue ID: IOJ-2260523
Also known as: FNML-76404
Sep 15, 2022 02:31 PM - edited Dec 12, 2022 01:28 PM
Is there a reason why something already fixed in the cloud release is only under consideration for on-prem?
@mfranz - the wording "This issue is under consideration to be addressed in a future FlexNet Manager Suite release" appears because there has been no FlexNet Manager Suite On-premises version released since this issue was fixed.
In this instance, because the issue has already been fixed in the Flexera One ITAM (aka FlexNet Manager Suite Cloud) release 2022 R1.2, the fix for the issue is very likely to be included in the next FlexNet Manager Suite On-premises release. That will be confirmed for certain at the time of the release, at which point the fix status appearing in this post will be updated.
I asked because usually the next on-prem release is mentioned for fixes.
@mfranz - the expected future release version a fix will be included in is not noted in a Known Issue article until the fix has gone through various checkpoints in the Flexera development process. The fix for this issue has not yet gone through those checkpoints in relation to the next FlexNet Manager Suite on-premises release, so the release number is not yet noted in this article.