What causes SapRfcDestinationAddFailed?

Incorrect SAP system connection parameters (host, system number, client, logon group) in the ADF linked service. The SAP NCo (SAP .NET Connector) library is not installed or is the wrong version on the Self-hosted Integration Runtime node. Network connectivity issues between the Self-hosted Integration Runtime and the SAP application server or message server. SAP user account lacks the necessary RFC authorization objects (e.g., S_RFC, S_TABU_DIS) to establish the destination

How do I fix SapRfcDestinationAddFailed?

Step 1: Verify all SAP connection parameters in the ADF linked service — host/IP, system number, client ID, logon group, and message server — against confirmed working SAP connection settings.. Step 2: Confirm that the correct version of the SAP NCo 3.0 library (matching the IR bitness — 32-bit or 64-bit) is installed on the Self-hosted Integration Runtime node.. Step 3: Test network connectivity from the IR machine to the SAP application server and message server on the required ports (typically 33XX and 36XX for RFC).. Step 4: Work with your SAP Basis team to verify the ADF service account has the required RFC authorization objects assigned in SAP (S_RFC, S_TABU_DIS, and connector-specific objects).. Step 5: Restart the Self-hosted Integration Runtime service after any library or network configuration changes, then re-run the connection test in ADF.

High severityconnectivityAzure Data Factory →

Power BI Refresh Error:
SapRfcDestinationAddFailed

What does this error mean?

The SapRfcDestinationAddFailed error occurs when Azure Data Factory cannot register or add an SAP RFC destination during a connection attempt to an SAP system via the SAP Table, SAP BW Open Hub, or SAP ODP connector. This typically prevents any data extraction from the SAP source.

Common causes

1Incorrect SAP system connection parameters (host, system number, client, logon group) in the ADF linked service
2The SAP NCo (SAP .NET Connector) library is not installed or is the wrong version on the Self-hosted Integration Runtime node
3Network connectivity issues between the Self-hosted Integration Runtime and the SAP application server or message server
4SAP user account lacks the necessary RFC authorization objects (e.g., S_RFC, S_TABU_DIS) to establish the destination

How to fix it

1Step 1: Verify all SAP connection parameters in the ADF linked service — host/IP, system number, client ID, logon group, and message server — against confirmed working SAP connection settings.
2Step 2: Confirm that the correct version of the SAP NCo 3.0 library (matching the IR bitness — 32-bit or 64-bit) is installed on the Self-hosted Integration Runtime node.
3Step 3: Test network connectivity from the IR machine to the SAP application server and message server on the required ports (typically 33XX and 36XX for RFC).
4Step 4: Work with your SAP Basis team to verify the ADF service account has the required RFC authorization objects assigned in SAP (S_RFC, S_TABU_DIS, and connector-specific objects).
5Step 5: Restart the Self-hosted Integration Runtime service after any library or network configuration changes, then re-run the connection test in ADF.

Frequently asked questions

Which version of SAP NCo should I install on the Self-hosted Integration Runtime?

Use SAP NCo 3.0 and ensure the bitness matches your IR installation — 64-bit NCo for 64-bit IR and 32-bit NCo for 32-bit IR. Download it from the SAP Software Center with a valid S-user account.

Can I use a load balancer or message server instead of a direct application server host?

Yes — ADF SAP connectors support both direct application server connections and message server (load-balanced) connections; ensure you populate the correct fields in the linked service for your chosen topology.