- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Suite Known Issues
- :
- Known Issue: Adobe Acrobat DC detection in InventorySettings.xml revision 66 may trigger a Windows I...
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Known Issue: Adobe Acrobat DC detection in InventorySettings.xml revision 66 may trigger a Windows Installer consistency check when inventory is gathered (IOK-932379)
Known Issue: Adobe Acrobat DC detection in InventorySettings.xml revision 66 may trigger a Windows Installer consistency check when inventory is gathered (IOK-932379)
Summary
A consistency check on all installed Windows Installer packages may be performed whenever inventory is gathered on a computer running Windows 10/11 that has Adobe Acrobat DC installed.
Details
The InventorySettings.xml file version 66 contains an update to gather data to support detection of different Adobe Acrobat DC editions (such us Professional, Standard and Reader) for the Acrobat DC unified installer versions 2021 (or later) on desktop machines.
This update contains code that executes the following WMI query on computers that have Acrobat DC installed:
select Version from Win32_Product where name like 'Adobe Acrobat DC'
A consistency check on all installed Windows Installer packages may be performed when this query is executed.
The following learn.microsoft.com page describes how using the Win32_Product WMI class can cause this behavior: Event log message indicates that the Windows Installer reconfigured all installed applications. In particular:
Win32_product class isn't query optimized. Queries such as select * from Win32_Product where (name like 'Sniffer%') require WMI to use the MSI provider to enumerate all of the installed products and then parse the full list sequentially to handle the where clause. This process also starts a consistency check of packages installed, verifying, and repairing the install.
As described in more detail on the above page, a symptom of this behavior occurring includes events appearing in the Windows Application event log with the following description:
Windows Installer reconfigured the product. Product Name: <ProductName>. Product Version: <VersionNumber>. Product Language: <languageID>. Reconfiguration success or error status: 0.
Logging like the following will also appear in the tracker.log file generated by the inventory gathering process. Timestamps on the log messages will match the time when the Windows Installer package consistency checks occur.
[9/26/2022 5:47:38 AM (G, 0)] {9504} Message from script: Fetching Adobe Acrobat DC version started. [9/26/2022 5:47:38 AM (G, 0)] {9504} Message from script: select Version from Win32_Product where name like 'Adobe Acrobat DC' [9/26/2022 5:47:47 AM (G, 0)] {9504} Message from script: Fetching Adobe Acrobat DC version completed.
Mitigation
This issue is fixed in InventorySettings.xml version 67 released as part of Application Recognition Library #2705. It is recommended to deploy version 67.
Configuring the following registry entry on computers where version 66 has already been deployed will stop the problematic step from being executed when inventory is gathered:
HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Tracker\CurrentVersion\ExcludeLocalScriptRule = AcrobatDC
Additional details
See the following additional resources related to this issue:
- Online help describing where you can control the version of the InventorySettings.xml file that is to be used by the Inventory Agent: Inventory Extensions Version
- Announcement of the change to gather additional details about Acrobat DC in inventory: Detection of Adobe Acrobat DC editions for the Acrobat DC unified installer (versions 2021 or later)
Fix status
This issue has been fixed in the following FlexNet Manager Suite release: InventorySettings version 67
Other information
Affected components: Agent, Content libraries, Inventory
Master issue ID: IOK-932379
Also known as: FNML-76829
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.