Connection issue in SAP Datasphere

[KarthikKumar31]

Hi All,

We are trying to establish a connection from SAP Datasphere (Test Tenant) to an SAP ABAP Test system. The connection between the Datasphere Dev Tenant and Dev ABAP system is working perfectly — the validation is successful.

However, when attempting to connect the Datasphere Test Tenant to the Test ABAP system, the connection fails with the following error:

"Connection "TEST_CONN1" couldn’t be established.
- Data flows can’t be used because of errors in the connection.
- Replication flows can’t be used because of errors in the connection.
- Remote tables are disabled.

Data Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: An invalid handle 'RFC_CONNECTION_HANDLE' was passed to the API call\nCode: RFC_INVALID_HANDLE"

Please refer to SAP Note 2849542 for more information.
Replication Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: An invalid handle 'RFC_CONNECTION_HANDLE' was passed to the API call\nCode: RFC_INVALID_HANDLE"

Please refer to SAP Note 2849542 for more information."

We have already compared and verified the technical user roles in the Test system comparing with the Dev system. Required resources have also been added to the Cloud Connector.

Has anyone else encountered this issue? Any suggestions or solutions would be greatly appreciated.

Thank you in advance!

[ShailendarAnugu]

Hi,

what are the resources exposed in cloud connector? also check if you have added location ID while adding subaccount and select the location id in the connection within datasphere?

refer to https://me.sap.com/notes/0003260800

Thanks,

Shailendar

[MKreitlein]

Hello @KarthikKumar31 

I think I saw this error message in the past as well... but long time ago, 1-2 years.

First thing I would do is to check if the Cloud connector can reach your SAP Test system ... means does the icon in the CC appear in green, showing the system is reached.

If not, this is the root cause.

If yes, maybe you check SU53 for your connection user, after testing it again? Can you find any entries there?

BR, Martin

[Ulrich_Schmidt1]

RFC_INVALID_HANDLE cannot be the cause of the problem, it is a consequence of the problem. It means, that at some earlier point, a connection broke down (or was closed deliberately by DataSphere), but then DataSphere keeps trying to use this no longer existing connection. So you should check for some other (perhaps network related) error preceding this one. Or perhaps turn on RFC trace and check what's going on.