FDM Integration with HFM Error: "Server/Cluster is incorrectly configured. Please reconfigure your Cluster or Server connection.

FDM Integration with HFM Error: "Server/Cluster is incorrectly configured. Please reconfigure your Cluster or Server connection.
		Modified 19-APR-2010     Type PROBLEM

---

Applies to:

Hyperion Financial Data Quality Management - Version: 8.3.1.0.00<max_ver> and later   [Release: 8.3 and later ]

Symptoms

When integrating between FDM and HFM, receive the following error:

Error: "Server/Cluster is incorrectly configured.  Please reconfigure your Cluster or Server connection.

This error can be received when browsing out for target maps, running the Validate step or exporting data to the target HFM application.

Cause

This can be because the Server/Cluster that is specified in the Machine Profile is incorrect or because the Target App that is specified is incorrect.

Solution

To resolve this, two things should be checked in FDM. 

From the FDM workbench make sure the Machine Profile has the correct HFM server or cluster name in the Target Machine field.

#1 Launch Workbench 

#2 Bottom left-hand corner, go to Adapters tab. 

#3 Drill down in Adapter to Machine Profile 

#4 Double-click existing Machine Profile for the FDM Application Server 

#5 Change the Target Machine so that it reflects the HFM Cluster name (to check HFM cluster name, launch HFM client local to FDM Application server and view HFM cluster name in the drop-down prior to connecting to HFM Application) 

From the FDM workbench make sure the target application is set. From the menu click Tools > Integration settings. The first option is the "Application Name" this should be set to the target HFM application. 

In HFM 


Log into the HFM client on the FDM application server, open the HFM app you are using FDM to connect to. (Be sure to set the server working folder if prompted) at this point you should be able to confirm the HFM app name and the Server/Cluster. If there are any problems connecting to the HFM client and logging into the HFM app they will need to be resolved for FDM to connect to HFM. 


If the HFM client is functioning properly and the Machine Profile and Target Application are set correctly this should resolve this error.