Users receive error: "The object invoked has disconnected from its clients" in Financial Management web interface
Posted by Priya Doyle on 02 December 2010 08:39 AM
Applies to:Hyperion Financial Management - Version: 220.127.116.11.15 to 18.104.22.168.00 - Release: 3.5 to 11.1
Information in this document applies to any platform.
Users are receiving "The object invoked has disconnected from its clients" errors while using Web Data Entry Forms (WDEFs), Data Grids, Process Control and other modules of the Financial Management web interface.
The Error message displayed may look something like this:
The exact cause of this problem has not been identified. At this time Oracle HFM Development and Microsoft Product Support are involved in an ongoing investigation to discover the root cause.
However Microsoft have recommended that it can normally be solved by restarting the Internet Information Services (IIS) web server on all Hyperion HFM web servers in the same environment. After this the error usually does not reappear for several months.
1. Ask all users to finish working in Hyperion Financial Management and to log out of the application.
2. On each Hyperion Financial Management web server, in Windows Services (services.msc), stop the Services related to Internet Information Services. These are called World Wide Web Publishing Service HTTP SSL and IIS Admin Service respectively.
3. When the services have stopped, restart those same three services and wait until they are all in status "Started".
4. Ask the users to once again try to log on to Hyperion web interface and work as normal.
If the problem is not solved in this way, consider completely restarting the Windows operating system on the affected web servers (reboot the servers).
If all HFM web servers have been rebooted and the problem is still occuring, then please go ahead and create a Service Request with Oracle Global Software Support. Be sure to include a screenshot of the error occuring in the HFM web interface including the "Show Details" extended detail, and be ready to provide further description of what activities in the user interface seem to cause the error most often.