Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

RFC program is being unregistered frequently

Former Member
0 Kudos

Hi,

I have a RFC LDAP_CRM & it is failing because the program LDAP_CRM is not registered.

I register the program & the RFC connects successfully.

But after some time again it fails with the same error "program LDAP_CRM is not registered."

Please suggest why the program keeps on unregistering frequently & what can be done.

Regards,

Ashutosh

1 ACCEPTED SOLUTION

Ulrich_Schmidt
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ashutosh,

in most cases where we see this problem, it is some firewall or router inbetween the external program and the SAP system, that is closing the connection because of "inactivity". There are two possibilities to fix this problem. Background on this topic can be found in note 1332022.

  1. The CPIC/RFC gateway can be configured to send periodic "pings" to the external program, so that the firewall/router considers the connection as active. See profile parameters gw/keepalive and gw/reg_keepalive. The ping interval should be smaller than the connection idle timeout on the firewall/router.
  2. Similar to the above, the external program can be instructed to send periodic "pings" to the gateway. This can be done via environment variables that need to be set in the environment where the external program is started: see note 1766471.

(And the third "fix" is of course increasing the router/firewall timeout, if the network admins of your network permit this. E.g. it may be possible to grant "unlimited" connection idle time for connections from the host, where the external program is running, to the host, where the gateway is running.)

Best Regards, Ulrich

1 REPLY 1

Ulrich_Schmidt
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ashutosh,

in most cases where we see this problem, it is some firewall or router inbetween the external program and the SAP system, that is closing the connection because of "inactivity". There are two possibilities to fix this problem. Background on this topic can be found in note 1332022.

  1. The CPIC/RFC gateway can be configured to send periodic "pings" to the external program, so that the firewall/router considers the connection as active. See profile parameters gw/keepalive and gw/reg_keepalive. The ping interval should be smaller than the connection idle timeout on the firewall/router.
  2. Similar to the above, the external program can be instructed to send periodic "pings" to the gateway. This can be done via environment variables that need to be set in the environment where the external program is started: see note 1766471.

(And the third "fix" is of course increasing the router/firewall timeout, if the network admins of your network permit this. E.g. it may be possible to grant "unlimited" connection idle time for connections from the host, where the external program is running, to the host, where the gateway is running.)

Best Regards, Ulrich