Symptom
Connection "Connection" 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.
Data Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"Not_Datasphere_Tenant_UUID\" and SCC location ID \"Location_ID\". Check the configuration on SCC and cloud side.\nCode: RFC_COMMUNICATION_FAILURE"
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: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"Not_Datasphere_Tenant_UUID\" and SCC location ID \"Location_ID\". Check the configuration on SCC and cloud side.\nCode: RFC_COMMUNICATION_FAILURE"
Environment
SAP Datasphere
Cause
Wrong configuration in SAP Cloud Connector.
Resolution
- Follow guidelines from SAP Datasphere Help: Configure Cloud Connector
In specific Section #2:
- In the side navigation area of the Cloud Connector Administration, click Connector to open the Connector page and click + Add Subaccount to open the Add Subaccount dialog.
- Enter or select the following information to add the SAP Datasphere subaccount to the Cloud Connector.
Note
You can find the subaccount, region, and subaccount user information in SAP Datasphere under System → Administration → Data Source Configuration → SAP BTP Core Account → Account Information.
Even for SAP Datasphere CPEA tenants, use the Tenant UUID (the true subaccount information) instead of BTP's subaccount. See KBA 3290588. - Check Location ID defined in Cloud connector to match same Location ID defined in Datasphere's connection settings.
See Also
Keywords
KBA , DS-DI-CON , Connections , Known Error