LCM Error: "Failed in communicating to Hyperion Financial Management remote service" When Exporting HFM Artifacts
(Doc ID 1615326.1)
Last updated on SEPTEMBER 26, 2022
Applies to:
Hyperion Financial Management - Version 11.1.2.1.601 to 11.1.2.3.702 [Release 11.1]Information in this document applies to any platform.
*June 26,2015*
Symptoms
Unable to export the HFM artifacts through Life Cycle Management. The following error is displayed when trying to export HFM artifacts using LCM:
"Failed in communicating to Hyperion Financial Management remote service at URL "http://<Server_Name>:80/hfmlcmservice/LCMWS.asmx" during "export" operation for application name "<HFM_Application_Name>" and cluster name "<HFM Cluster Name>""
The following detailed error message will be logged in the Sharedservices_LCM.log file
"[FoundationServices0] [ERROR] [EPMLCM-30034] [oracle.EPMLCM] [tid: 28] [userId: <anonymous>] [ecid: 0000KDiW_W82vHpzCOnZ4C1IlmBS0000TL,0] [SRC_CLASS: com.hyperion.lcm.common.LCMLogger] [APP: SHAREDSERVICES#11.1.2.0] [SRC_METHOD: logMessages:937] Failed in communicating to Hyperion Financial Management remote service at URL "http://<Server_Name>:80/hfmlcmservice/LCMWS.asmx" during "export" operation for application name "<HFM_Application_Name>" and cluster name "<HFM Cluster Name>". Nested exception is [MESSAGE - org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement artifactData, LCM METHOD CALL - com.hyperion.lcm.ws.client.LCMWSLCMWSSoapStub.fromOM(16972), ROOT CAUSE - org.apache.axis2.AxisFault.makeFault(430)] ."
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |