CPI:IS- RFC Adapter Issue: Initialization of repository destination failed

[sugata_bagchi2]

Hi Experts,

I have-

1. Created System Mapping under access control for RFC Adapter in SCC
2. Created Destination of type RFC in SAP BTP
3. Used Load balancing option while creating the system mapping in SCC
4. Both connections are working fine when tested individually.
5. But when Iflow is triggered the RFC call is failing with the following error -
Error Details
com.sap.it.rt.adapter.rfc.exceptions.RFCLibraryException: Initialization of repository destination Destination_RFCQA failed: Timeout occurred while establishing the connection to an ABAP system. Remote system accessed via destination Destination_RFCQA did not reply within 60 seconds.Initialization of repository destination Destination_RFCQA failed: Timeout occurred while establishing the connection to an ABAP system. Remote system accessed via destination Destination_RFCQA did not reply within 60 seconds.

could you please let me know why am I receiving this error? I have not configured any repository destination or mentioned any repository config details in BTP destination.

Thanks

Sugata

[sugata_bagchi2 · Accepted solution]

This was an issue due to the internal port was redirecting to another port.

[VijayKonam]

Did the ping from Cloud Connector work? It looks like CC itself is not able to reach to backend system.

[sugata_bagchi2]

Hi Vijay,
The Availability check worked from both SCC and BTP destination.

[PriyankaChak]

Hi Sugata,

Can you please check cloud connector logs also?

Regards,

Priyanka

[sugata_bagchi2]

Hi Priyanka,
Please see my comment below on Vijay's response.

[Ulrich_Schmidt]

Hi Sugata,

Priyanka is right: I would suggest activating the "Payload Trace" for this account in SCC. Then we can see

1. whether the call from CPI is even hitting the SCC (perhaps CPI is accidentally not using the given connection parameters for its DDIC lookups?!)
   --> If payload trace is empty, we know that the problem is between CPI and SCC
2. whether the backend system is perhaps not replying within the 60s
   --> If payload trace shows the RFC request from CPI, but no response from the backend, we know the problem is between SCC and backend

[VijayKonam]

That library exception is being thrown from the backend. You might need to check some basis logs as well. Also did you try hitting the RFC from any other means, from outside of your backend?

[sugata_bagchi2]

Yes, I tried it calling from PI/PO as a RFC lookup and it worked perfectly fine.