Inventory Extension Version - Not Updating

[davidle]

Hello all,

I have recently discovered that the Inventory Extension Version that is approved (Revision #45) does not match the Revision # that is displayed after running the query below on the FNMSCompliance DB:

SELECT * FROM ConfigurationFile where Name='InventorySettings.xml'

Does anyone know how we can update the ConfigurationFile Revision on the FNMSComplianceDB to match the approved one?

@mgunnels - Have you seen this type of error before?

Thanks!

- David Le

[AamerSharif]

Hope it is not due to Revision gone out of sync OR configuration set use specific version/revision, please check what is Revision number of the selected version in MasterConfigurationFileSelection table, that is the one should be getting used. Good to check first what is shown as selected version in the WebUI under Discovery and Inventory > Setting page.
You can check in the database by querying the following table.
SELECT * FROM MasterConfigurationFileVersions -- All the available versions
SELECT * FROM MasterConfigurationFileSelection -- Selected version
SELECT * FROM MasterConfigurationFileOptionState -- State of the configuration
If you find them out of sync you can delete inventory settings from configuration table by running

Delete from ConfigurationFile       --(If selected version is different).

Reset the IIS on the batch server and next beacon policy update should kick off update of the ConfigurationFile with the selected version. Good to dump ConfigurationFile table before delete update does not kick in you can put it back by setting the SET IDENTITY_INSERT dbo.ConfigurationFile_MT ON and OFF.
Note: Applies to FNMS version 2019 R1 and later.
Cheers,
Aamer

[davidle]

Hi @AamerSharif ,

After running the queries you provided, it seems as the ConfigurationFile versions are not in-sync. (Selected MasterConfigurationVersion is #45, ConfigurationFile Version is #43)

 Do I run this command "SET IDENTITY_INSERT dbo.ConfigurationFile_MT ON" before deleting from the ConfigurationFile?

Thanks for your help.

- David

[AamerSharif]

SET IDENTITY_INSERT dbo.ConfigurationFile_MT ON command was a reference for dba in case you like to restore old configuration. 

Did you check what is the selected version? if selected version is not the latest configurationfile  would not show the latest (FNMS version 2019 R1 and later give user option to select revision number approved OR latest).

If you don't want to backup existing configuration file in use You can simply delete the configuration and update beacon policy as i mentioned above (by editing beacon and click save one way to increment beacon policy) it should generate new configuration file with latest revision available from the master table.

Delete from ConfigurationFile

HTH

Aamer