HFM Error: "the parameter is incorrect" When Running Intercompany Matching Reports (ICP Matching Reports) After A Metadata Change | |||||
|
|||||
Modified 18-NOV-2010 |
Applies to:
Hyperion Financial Management - Version: 4.0.0.0.00 to 9.3.1.0.00 - Release: 4.0 to 9.3Information in this document applies to any platform.
Symptoms
When running Intercompany Matching reports after a metadata change, user or administrator may start to observe streams of errors appearing in the System Messages and HsvEventLog.log file with summary of "The parameter is incorrect"
On examining these errors using the ErrorLogViewer.exe utility in the Consultant Utilities folder, detail such as the below may be observed
File: DSCommonMetadataI.cpp Version: 9.2.0.0.1106 Line: 1601 Error: (-2147024809)(0x80070057)(The parameter is incorrect.)
File: CHsvDsAd.cpp Version: 9.2.0.0.1106 Line: 425 Error: (-2147024809)(0x80070057)(The parameter is incorrect.)
File: CHsvDSMetadataAccounts.cpp Version: 9.2.0.0.1106 Line: 43 Error: (-2147024809)(0x80070057)(The parameter is incorrect.)
Cause
Invalid records within the HFM database data tables are sometimes not correctly ignored by the Intercompany Matching functionality.
Solution
Since these are orphaned data, which can no longer be accessed by the application, it is safe to remove them.
Use the "Delete Invalid Records" functionality provided by Hyperion Financial Management to remove Invalid Records. This can be found under "Database Management" module in both the web interface and the Windows client interface.
ALWAYS take a backup of your HFM database before running Delete Invalid Records, run the routine at a time of low system activity, and perform first just a "Scan" of the invalid records if you have concerns. If the "Scan" does not reveal any errors about currency corruption it should be safe to run the full routine. It may run for 30 minutes or more before completion.
After running Delete Invalid Records, if the issue is not resolved, consider loading a blank rules file, and then loading your original rules once again. The next time that an Intercompany Matching Report is executed, there should be no further "parameter is incorrect" errors.
GKontos
Comments