Some users may be experiencing issues when trying to access customer resources like the Case Portal or the Product Licensing Center. Our team is aware of the issue and is working to resolve it. Click here for more information.
Hi,
We just completed the upgrade from FNMS 2018 R2 to FNMS 2019 R1. However, post upgrade the reconciliation process encountered an error with message Error: Exception has been thrown by the target of an invocation. Addition to that, unable to access few pages from web UI i.e. All Inventory page with Error ID: f73d4b45-4db3-4b4e-9d81-c487eabf27a9
Has anyone encountered this before?
Thank you.
Regards,
Intan
‎Jul 19, 2019 01:53 AM - last edited on ‎Jul 11, 2021 07:27 PM by ChrisG
We managed to solve this. As you pointed out, the cause was the compliance db wasn't properly migrated.
Resolution:
FNMS is working fine now. Thank you.
‎Jul 24, 2019 09:05 PM
Hi Intan,
Does this error occur repeatedly?
Reading the log it looks like the actual reconcile has not begun yet. Instead it is the ManageSoft reader that fails. You could check the reader and find the exact step failing (around "ProcessCSPMetadataJsonBlob").
Best regards,
Markward
‎Jul 19, 2019 05:00 AM
The "Could not find stored procedure" message in the import log is the key one to look at here:
2019-07-19 11:42:23,592 [ERROR] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Could not find stored procedure 'ImportedComputerForCSPMetadataGetAllByComplianceConnectionIDCloudServiceProvider'.
This suggests that there is a mismatch between the version of the database schema and the version of the installed FlexNet components: the ImportedComputerForCSPMetadataGetAllByComplianceConnectionIDCloudServiceProvider stored procedure that was added in the 2019 R1 release has not been configured in the database [yet]. Is it possible that the database upgrade and installation steps for the 2019 R1 release have not been successfully executed yet?
‎Jul 19, 2019 09:30 PM - edited ‎Jul 19, 2019 10:32 PM
We managed to solve this. As you pointed out, the cause was the compliance db wasn't properly migrated.
Resolution:
FNMS is working fine now. Thank you.
‎Jul 24, 2019 09:05 PM
User | Count |
---|---|
8 | |
6 | |
3 | |
3 |