Hi All,
We have installed new FNMS 2019R1 for a customer (on-premises). The inventory beacons also configured, however facing 2 issues, need your help
1. When we click on "New" inventory connection, there is an error message saying " Unhandled exception has occured in your application. Input string is not in correct format."
If we ignore it, we can not see the drop down list for inventory sources, if we cancel it, the beacon application is closed. Other options, all are working fine and beacons reporting properly, status is "uptodate" etc.,
2. There is an alert on all beacons saying "Last download of packages for managed devices is failed". How to fix it
We've checked the packageretriever.log as well, attached the log here. It says "404 not found" for 12.4 packages, and on Inventory Server > IIS >default websites> Packages, we could not find 12.4 node at all (attached screenshot) while only 13.2.0 is present for adoption and upgrades.
Jul 09, 2019 07:23 AM - edited Jul 09, 2019 08:41 AM
Hi,
Some questions:
Best regards,
Markward
Jul 09, 2019 10:33 AM
Thanks Markward, for your response.
Jul 09, 2019 10:43 AM
Hi @ImIronMan ,
For Unhandled exception - Could you please check the Regional and Language settings in the control panel.
Go to Region and Language Settings, change the language to English (US or Australia).
On the Administrative Tab click “Copy Settings”.
Now restart the Beacon,Hopefully it should work now.
Regards,
Sasi
Jul 10, 2019 02:56 AM
That's spot on. Your suggestion worked and I do not see the unhandled exception error any more. Many thanks.
However, the other first issue is still there.
Thanks
Regards
Rajesh Ponnala
Jul 10, 2019 07:02 AM
Hi,
Have you checked if the paths mentioned in the log (where it tries to download the packages from), do actually exist on the parent beacon?
Yopu mentioned this is a new installation (2019 R1) and yet the log is referring to package version 12.4 (which is 2017 R3). Could this be a fresh application installation, but with a migrated database? My best guess is that there are packages registered in the database that are not available form the file system anymore. Please check the "AvailablePackages_MT" table and compare to the file system.
SELECT * FROM AvailablePackage_MT
Best regards,
Markward
Jul 12, 2019 10:54 AM
Yes, you are right. Its a fresh application with migrated database.
Another point would like to mention here is : While other things working fine in the new 2019R1 (besides this only pacakges error), customer again expecting us to restore their latest 2017R3 compliance database and configure whole 2019R1 freshly, because its been more than 10 days the new version is built but customer still using 2017R3.
So I must also ensure this issue is not repeated when I restore FNMS Compliance db and re-configure 2019R1.
Regards
Rajesh Ponnala
Jul 15, 2019 08:33 AM