Remote Hyperion Financial Management and Financial Reporting Clients Cannot Make Connection to HFM Application Server

(Doc ID 1368630.1)

Last updated on NOVEMBER 22, 2017

Applies to:

Hyperion Financial Management - Version to [Release 9.3 to 11.1]
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)


When attempting to connect to the Hyperion Financial Management (HFM) Application Server using either the HFM or Financial Reporting client, the client simply hangs and needs to be killed using the Task Manager. There are no errors seen initially in either the HFM Log, or Windows Event log(s).

This issue applies only to remote machines (be it server to server, or Windows client to server) which have the HFM or Financial Reporting clients installed. A single HFM Application Server machine does not show this behavior when directly on that server.

To diagnose the problem:

  1. Test to see that DCOM is able to communicate between the two machines. This can be done using the Microsoft DCOM Test utility here:
    For this particular issue, the DCOM test utility was showing as successful connecting to port 135.
  2. Enable DCOM Logging as seen here: Once the server is rebooted, recreate the issue (ie. Register a server/cluster on the remote machine) and check the Windows Event Log. Now a DCOM 'Access Denied' should be seen pointing to access issues with the ANONYMOUS User.
  3. In cases where #2 above do not throw an error, install Wireshark ( or similar IP trace utility to the remote machine and recreate the issue. Now an error should be viewable:
  4. Another symptom: check to see if the 'Edit Limits' are greyed out. If they are, this is a good indicator that security was modified on the HFM Application server(s).


Windows Policy security changes were pushed across the domain.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms