Intermittent “Remote Procedure Call Failed” Errors Working With Hyperion Financial Management Application | |||||
|
|||||
Modified 21-SEP-2010 |
Applies to:
Hyperion Financial Management - Version: 3.5.1.0.00 to 11.1.1.1.00 - Release: 3.5 to 11.1z*OBSOLETE: Microsoft Windows Server 2003
Symptoms
Users will intermittently see "The remote procedure call failed." errors while working with a Hyperion Financial Management application.
Cause
This issue can be caused by a firewall located between the Financial Management Web server and the Financial Management application server if the firewall is configured to reset idle connections.Solution
To resolve these errors, decrease the TCP/IP KeepAliveTime setting on the Financial Management web and application server(s) to be slightly less than half the firewall idle connection timeout value. Example, if the firewall timeout is 20 minutes then setting the KeepAliveTime to between 5 and 10 minutes would keep the connection from being reset..
Add the following Value to the key if it does not already exist:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Value Name: KeepAliveTime
Data Type: REG_DWORD
Value (decimal): XXXX
The value of XXXX is in milliseconds, Default value is 7,200,000(two hours). This value controls how frequently TCP tries to verify that an idle connection is still intact by sending a keep-alive packet. If the remote computer is still reachable, it acknowledges the keep-alive packet. Keep-alive packets are not sent by default. New value should be less than half the firewall idle timeout.
Serious problems may occur if you modify the registry incorrectly. You should back up the registry before you modify it.
References
"Windows NT Settings for TCP/IP Timeouts"
|
GKontos
Comments