Unable to register a system in SLD

[Former Member]

Hi,

I'm trying to register a system via RZ70 in PI's SLD.

However, SLD_UC fails with the following error:

TP SLD_UC init/busy for more than 60 seconds

Return Code: 677

Increasing the timeout doesn't help.

I've tried setting gw keep alive parameters as 0 on PI too.

Reginfo too has been maintained on PI & loads successfully in SMGW...gw/acl_mode is 1.

SMGW has around 40 active connections...out of a total of 1000.

Please help advise what could be wrong...

Thanks a lot !

saba.

[Reagan · Accepted solution]

Have you checked the trace files dev_rd, dev_icm in the /usr/sap/<SID>/DVEBMGS<NN>/work directory? if so what do they contain?

[Former Member · Accepted solution]

Hi Reagan,

The rfc traces say:

Timeout while waiting for a connection to be established on the satellite system.

The other files offer nothing fruitful...

Thanks !

saba.

[Former Member · Accepted solution]

Hi Saba.

If you test the SLD RFCs directly in SM59 does it also timeout ? I would also try telnet using both the IP and Hostnames to the target system to ensure it is not a name resolution error.

Finally when it is trying to connect do you see the connection at OS Level using netstat i.e. netstat -an

Thanks

Neil Ryan

SAP Active Global Support

[Reagan · Accepted solution]

Hello Saba

That time out error makes me feel there is something blocking from establishing the connection. Check the SAP KBA supplied by Sriram and check if the Gateway parameters help.

Cheers

RB

[Former Member · Accepted solution]

Hi !

The SLD RFC when tested directly times out too.

Telnet works well...so do other Type 3 RFC's.

Also; as mentioned earlier, with gw/acl_mode = 0 on PI, the SLD_UC RFC works fine.

Its only when I set this parameter to 1 & make use of reginfo/secinfo that I run into this issue.

The gw parameters in Note 1791529 too have not helped.

Kernel patch on SLD system: 742-17

Kernel patch on satellite system: 741-31

Thanks a lot !

saba.

[Former Member · Accepted solution]

You need to adjust your reginfo/secinfo files to properly register program and get access to it later. You can activate trace (in SMGW or through gwmon) to check if registered program for SLD has been registered without issues.

[Former Member · Accepted solution]

Hi Saba.

That's good so you have ruled out network, Firewall or name resolution as a possible cause, as such can you please review the following SAP SCN review of SLD and the Gateway / Gatway ACL which covers everything and will help you resolve the issue:

http://scn.sap.com/community/it-management/blog/2014/09/09/sld-migration-and-gwaclmode

Thanks

Neil Ryan

SAP Active Global Support

[Former Member · Accepted solution]

Hi !

I finally got this sorted out (with SAP's help )

Steps:

1. Delete the existing SLD_UC  from SMGW-->Logged on clients on PI (this is the local SLD_UC)

2. Restart PI, goto the SLD page & "Save" the Settings under Administration

3. SLD_UC (the local one) then re-appears in SMGW on PI

4. Once the local SLD gets re-registered (using the current reginfo), RZ70's from other systems work well too...

5. Quote from SAP:

Hello Saba,

As soon as a TP is registered against the abap gateway, it will take a
snapshot from the current reginfo rules and apply them for itself.
Even if the rules are changed later, they will not reflect over the
already active registrations because of this. The only way to apply
the changes for an older registration is through deregistering and
registering the TP again.

Thanks a lot everyone for all the wonderful replies

Happy Thursday !

saba.

[divyanshu_srivastava3]

TP SLD_UC init/busy for more than 60 seconds
Return Code: 677

Have you checked by changing the kernel and network latency ?

Delete SLD_UC and SLD_NUC, then make sure you are logged on PAS from where you have ports opened and network latency minimal, update your kernel, goto RZ20 and re-trigger.

Regards,

[Former Member]

Hi !

Thanks a ton for the super replies

A regular RFC between the PI (SLD) system & the satellite system works fine.

Also, when gw/acl_mode is set to 0 on PI & secinfo/reginfo are deleted...the registration works beautifully.

With gw/acl_mode=1, Reginfo gets loaded successfully in SMGW...have even tried with just:

#VERSION=2

P TP=* HOST=*

In SMGW, I can even see the program in "connecting" state but only till the defined timeout value.

Maybe I'm missing something basic

Thanks a lot !

saba.

[divyanshu_srivastava3]

Hi Saba,

Some KBAs which you should see in your case.

2078066 - JRA: Hanging RFC connections to JCoServers

1791529 - GW: Hanging connections between J2EE and gateway

[srinivasan_vinayagam]

Hi Saba,

SAP Note 1938714:ERROR: timeout during allocate of registered program

1.     the check entries for managed systems in /etc/hosts file.

2.     the check whether both the systems can communicate each other via RFC .

3.     or try to use IP address instead of the host name.

Regards,

V Srinivasan

[nicholas_chang]

If possible, try to update your kernel to latest level as i recalled correctly, registration failed might cause by kernel lower than certain version.

[Sriram2009]

Hi Saba

1. Could you check the central SLD ? or if possible restart the central SLD

2.  Could you check this SAP KBA

1938714 - ERROR: timeout during allocate of registered program

BR

SS

[Former Member]

execute the SLD registration again and then check the work process logs and work process RFC logs also check dev_rd logs. if possible zip the logs and attach.

I hope you have opened the network traffic from your PI and the system you are trying to register in SLD.