Connection to SLD

[Former Member]

HI ,

This is our scenario.We have a ecc 6.0 system we are trying to get that system into sld which is running on host that has only java stack netweaver 2004s.In the process of getting the system into our sld.We have trying to configure these four RFC's

SLD_UC

SLD_NUC

LCRSAPRFC

SAPSLDAPI

when we are testing SLD_UC and SLD_NUC they are working fine.But the other two are not working.

The error log for the other two is shown below.

Logon Cancel

Error Details timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur

Error Details ERROR: timeout during allocate

Error Details LOCATION: SAP-Gateway on host pluto / sapgw02

Error Details DETAIL: no connect of TP LCRSAPRFC_PPIH from host aquarius.hal.hitachi.com aft

Error Details COMPONENT: SAP-Gateway

Error Details COUNTER: 16

Error Details MODULE: gwr3cpic.c

Error Details LINE: 6178

Error Details RETURN CODE: 242

Error Details SUBRC: 0

Error Details RELEASE: 700

Error Details TIME: Thu Feb 19 00:21:53 2009

Error Details VERSION: 2

Logon Cancel

Error Details timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur

Error Details ERROR: timeout during allocate

Error Details LOCATION: SAP-Gateway on host pluto / sapgw02

Error Details DETAIL: no connect of TP SAPSLDAPI_PPIH from host aquarius.hal.hitachi.com aft

Error Details COMPONENT: SAP-Gateway

Error Details COUNTER: 17

Error Details MODULE: gwr3cpic.c

Error Details LINE: 6178

Error Details RETURN CODE: 242

Error Details SUBRC: 0

Error Details RELEASE: 700

Error Details TIME: Thu Feb 19 00:51:21 2009

Error Details VERSION: 2

[Former Member · Accepted solution]

Hi,

Normally the problem is with the program ID does not match with the one in the PI integration server, or the host and the gateway is not pointing to your PI server.

PI server

1. Go to your PI integration server transaction SMGW

2. Goto -> Logged on client

3. Click on column TP name and sort it accordingly.

4. Check the correct program ID registered over there

Back End system

1. Go to your back end system transaction SM59

2. Match your program ID in your back end RFC destination with the program ID registered in PI gateway.

3. Make sure the host and the gateway name of the PI server in RFC destination is populated correctly.

It did happen to me before, and this is the way to solve it. I am sure it works for you too.

Regards,

Lim...