RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

[Former Member]

Hello All,

In our XI production system all the interfaces which are indeed connecting to R3 system is getting failed and in the message log it shows...

*********************

MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=ashb01wa06pr SYSNR=01 GWHOST=ashb01wa06pr GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner not reached (host xp0ci01.inside.a

*********************************************

can you kindly advise me on this ASAP,

Best Regards

Raki

[prateek]

Check for the entry in host file at path c:\winnt\system32\drivers\etc\

Regards,

Prateek

[Former Member]

Hi Rakesh,

Try the following steps..

1. Stop the RFC Communication channel in RWB

2. Start the same and check the status

This technique works sometimes.

Regards,

Ananth

[Former Member]

Hi Ananth,

Thanks for the update,

Can you kindly explain me , in what way we stop RFC Communication channel in RWB(procedure).

I did not find that option, but any way the issue resolved after restarting our XI production system as we thought that this might be a bottle neck issue.

Thanks for one and all for helping me ..

Best Regards

Rakesh Reddy

[Former Member]

Hi

In the RWB->Component monitoring->Adapter Engine-> choose comm channel monitoring and then choose u r Comm channel. there you can see the buttons start and stop.

Regards,

Kumar

[Former Member]

Hello Kumar,

Thanks for update,

I got it and able to do that.The problem got resolved..

Thanks for all helping me to resolve the issue.

Best Regards

raki

[Former Member]

Hi Rakesh,

We get this error normally when R/3 system is down / cannot be reached.

Just try to login into R/3 system directly from abap stack.

Nilesh