Synopsis
Inventory NDI files gathered from devices running MacOS where the inventory agent has been unable to identify a unique ID for the machine or user may fail to import.
Details
When the inventory agent is unable to identify a unique ID for the machine or user, inventory NDI files from the agent may fail to import. When this occurs the import process produces an error like the following:
Expected hex 0x in '{0}'.
File <C:\ProgramData\Flexera Software\Incoming\Inventories\username on machinename at 20201114T092438 (Full).ndi: File content was in invalid format
When inspecting the contents of affected NDI files you will see the MachineUID and/or the UserUID attribute values set to "{}" as follows:
<Inventory Tracker="16.0.1" Audience="machine" MachineUID="{}" UserUID="{}" ...>
Fix details
Two changes have been made which help to address this issue:
- The MacOS agent has been changed to avoid generating NDI files that contain "{}" UID values and subsequently fail to be imported by older inventory servers due to this issue.
- The inventory server has also been changed so it can successfully import NDI files generated by older MacOS agents that have "{}" UID values.
Workaround
This issue can be manually worked around by editing an affected NDI file to remove the "{}" values:
<Inventory Tracker="16.0.1" Audience="machine" MachineUID="" UserUID="" ...>
After editing a file, import the file by placing it in the C:\ProgramData\Flexera Software\Incoming\Inventories directory on the inventory server, or uploading it again.
Fix status
This issue has been fixed in the following FlexNet Manager Suite releases: 2020 R2.3 / Apr 2021 (Cloud), 2021 R1 (On Premises)
Other information
Affected components: Agent, Inventory, Uploaded file importers
Master issue ID: IOJ-2179972
Also known as: FNML-72990
Related Articles
Known Issue: Windows OS name values from .ndi files imported by inventory server (with agent installed on the same server)… 31Number of Views Known Issue: “WriteFileEvidence - Insert unmatched evidence” import writer step may fail with error due to NewFileEvidence… 65Number of Views Known Issue: “WriteFileEvidence - Insert unmatched evidence” import writer step may fail with error due to FileEvidenceFil… 42Number of Views Inventory NDI files fail to import and are saved in BadLogs folder on the inventory server if SoftwareFile_MT.SoftwareFile… 8Number of Views Known Issue: Inventory NDI files from lightweight Kubernetes agent may fail to import due to inventory date of 0001/01/01 … 12Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago