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"
Read more...
Environment
SAP Datasphere
Product
Keywords
KBA , DS-DI-CON , Connections , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.