SAP Knowledge Base Article - Public

3369433 - How to troubleshoot Cloud Connector related issues when creating connection in Datasphere

Symptom

This KBA is written for troubleshooting purposes of Cloud Connector issues or in case there is an issue when creating the connection for data flows and replication flows in SAP Datasphere.

Environment

SAP Datasphere

Reproducing the Issue

You are trying to connect Datasphere but you are getting an error message when validating the connection.

Resolution

List of Available Connections + Preparation and SAP Datasphere connection guided answer

Configure Cloud Connector before connecting to on-premise sources and using them in various use cases. In the Cloud Connector administration, connect the SAP Datasphere subaccount to your Cloud Connector, add a mapping to each relevant source system in your network, and specify accessible resources for each source system.

It's necessary for the following features:

  • Data flows
  • Replication flows
  • Model import from: SAP BW/4HANA Model Transfer connections (Cloud Connector is required for the live data connection of type tunnel that you need to create the model import connection)
  • SAP S/4HANA On-Premise connections (Cloud Connector is required for the live data connection of type tunnel that you need to search for the entities in the SAP S/4HANA system)
  • Remote tables (only for SAP HANA on-premise via SAP HANA Smart Data Access)

How to start:

If there is an issue in Remote Tables, the issue could be related to DP Agent. Therefore, please see the SAP KBA 3196950.

Below you will find a list of different issues and its solutions:

CASE A

Problem Description: validating the newly configured connection in Datasphere.
Data Flows: Cause: Error occurred when connecting to Hana database. Error: [10]: authentication failed. Code:1300004
Replication Flows: Cause: Error occurred when connecting to Hana database. Error: [10]: authentication failed. Code:1300004

Cause: wrong User Name and/or Password under Credentials

Solution: make sure to use a valid user/pw combination

...................................................................................................................

CASE B

Problem Description: You are trying to connect Datasphere with ABAP/BW system but you are getting an error message when validating the connection. The error message is the following or similar:

ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Opening connection to backend failed: Opening connection to ldcsb5h.devsys.net.sap:sapgw00 denied. Expose the system in your Cloud Connector in case it was a valid request.\nCode: RFC_COMMUNICATION_FAILURE"

Cause: Virtual host is not entered or incorrectly entered.

Solution: Follow the step 3 in documentation here . 

...................................................................................................................

CASE C

Problem Description: You are trying to connect Datasphere with ABAP/BW system but you are getting an error message when validating the connection. The error message is the following or similar:

ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Client 003 is not available in this system\nCode: RFC_LOGON_FAILURE".  

Cause: You are mapping your source system with wrong virtual host. 

Solution:  Check the client parameter of your source system and map to the correct virtual host.
If there is no virtual host with the matching client parameter, then create a new one. You can refer here .

...................................................................................................................

CASE D

Problem Description: You are trying to connect Datasphere with ABAP/BW system but you are getting an error message when validating the connection. The error message is the following or similar:

Data Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="An Error occurred: Could not invoke function \"RFC_FUNCTION_SEARCH\" | rfcSDKError[Number:000, RFC_ABAP_EXCEPTION, NO_FUNCTION_FOUND, , , 000, , , , ]. 

Cause: ABAP Source system is missing prerequisites for Data Flows and Replication Flows features. You can refer to SAP KBA.

Make sure to have following Function Modules in your ABAP Source system:

  • RFC_FUNCTION_SEARCH
  • RFC_GET_FUNCTION_INTERFACE
  • LTAPE_GRAPH_VERSION
  • DHAPE_GRAPH_VERSION

In case you find a missing function module, apply the latest DMIS 2018 support package.
Function LTAPE_GRAPH_VERSION is part of DMIS addon

SAP Note 2890171 - SAP Data Intelligence - ABAP Integration

For ABAP Connection in Datasphere the DMIS addon is a must.
As mentioned in SAP Note 2596411 - Note Analyzer for ABAP-based Migration and Replication Technology (DMIS2011/DMIS2018/DMIS2020/S/4HANA) 
"In general, corrections for the ABAP Integration are delivered via SAP Notes. To check whether all available SAP Notes are installed, you can use the Note Analyzer tool - for more details, see SAP Note 2596411."
Once DMIS Addon is installed, the connectivity problem will get resolved.

In case the problem still exists, record a cloud connector trace (SAP KBA 2452568) and open a support ticket providing us all necessary information from the SAP KBA 2891554.

...................................................................................................................

CASE E

Problem Description: Data flows: Cause: ABAP Connector (Axino) ABAP connection check FAILED: request failed: rc=1, msg:"could not detect ABAP Pipeline Engine"

Solution:  To solve the issue please see SAP Note 2835207 .
 
1. Upgrade DIMIS version. 
2. Add the resources with name LTAPE, LTAMB & DHAMB to the cloud connector entry of RFC type.

...................................................................................................................

CASE F

Problem Description: You are trying to connect Datasphere with ABAP/BW system but you are getting an error message when validating the connection. The error message is the following or similar: Failed to retrieve connection abc-1h23-1234-12e0-12341234. Server responded with 500 Virtual destination port xyz00 is not valid Code:10706 

Solution: For ABAP-related connection types like S4HANA, when using RFC protocol, the port has to follow the pattern 33xx with xx being the two-digit ABAP system number. See SAP Help for a list of TCP/IP ports (filter for Product Name = Application Server ABAP and look for Port Name = Gateway). This format is also required for the virtual port. To solve this issue:
  1. in the connection definition, change the virtual port to "3300",
  2. in cloud connector, section "Cloud to On-Premise", in the "Mapping Virtual To Internal System" adjust the virtual port to "3300" as well.
In addition, you it is worth to follow the settings mentioned here:
...................................................................................................................

In case the problem still exists, record a Cloud Connector trace (SAP KBA 2452568) and open a support ticket providing us all necessary information from the SAP KBA 2891554.
 
How to record Cloud Connector trace:

1. In the SAP Cloud Connector, increase the Cloud Connector Loggers to Debug, set Other Loggers as Information per KBA 2452568 - Log and Trace files for SAP Cloud Connector

           Turn off other loggers like SSL Trace, CPIC.

2. reproduce the issue

3. Save the SAP Cloud Connector logs (by clicking on the Download all button). Then, attach all the files in the incident:SAP Cloud Connector traces (step 1) - it should contain the ljs_trace.log and scc_about files

4. Take screenshot of the error including the timestamp.

5. Please save all the files to one zip file and attach (so that we will not have too much attachments in one case).

Keywords

KBA , DS-DI-CON , Connections , Bug Filed

Product

SAP Datasphere all versions