What causes DF-SAPODP-NotReached?

The SAP application server hostname or IP address in the linked service is wrong or the server was moved. A firewall rule change blocked the RFC port (33XX where XX is the SAP instance number) between the IR host and SAP. The Self-Hosted IR host lost network access to the SAP server — VPN disconnected, routing changed, or NIC failure. The SAP application server is down for maintenance or experienced an outage

How do I fix DF-SAPODP-NotReached?

On the Self-Hosted IR host machine, open a command prompt and run: Test-NetConnection -ComputerName -Port 33 (replacing XX with the SAP instance number).. If the test fails, the network path is blocked — check with the network team whether a firewall rule was recently changed.. If the test succeeds but ADF still fails, verify the hostname and system number in the SAP ODP linked service match exactly — check for typos or environment confusion (e.g. DEV vs PRD).. Check whether the SAP system is running by logging into the SAP GUI or asking the SAP Basis team.. After restoring connectivity, re-run Test connection on the linked service in ADF Studio to confirm access before retrying the pipeline.

High severitydata source

Power BI Refresh Error:
DF-SAPODP-NotReached

What does this error mean?

ADF cannot establish a network connection to the SAP system for the ODP extraction. The Self-Hosted IR cannot reach the SAP application server on the configured hostname and RFC port. Every run fails until the network path is restored.

Common causes

1The SAP application server hostname or IP address in the linked service is wrong or the server was moved
2A firewall rule change blocked the RFC port (33XX where XX is the SAP instance number) between the IR host and SAP
3The Self-Hosted IR host lost network access to the SAP server — VPN disconnected, routing changed, or NIC failure
4The SAP application server is down for maintenance or experienced an outage

How to fix it

1On the Self-Hosted IR host machine, open a command prompt and run: Test-NetConnection -ComputerName <SAP host> -Port 33<XX> (replacing XX with the SAP instance number).
2If the test fails, the network path is blocked — check with the network team whether a firewall rule was recently changed.
3If the test succeeds but ADF still fails, verify the hostname and system number in the SAP ODP linked service match exactly — check for typos or environment confusion (e.g. DEV vs PRD).
4Check whether the SAP system is running by logging into the SAP GUI or asking the SAP Basis team.
5After restoring connectivity, re-run Test connection on the linked service in ADF Studio to confirm access before retrying the pipeline.

Frequently asked questions

What port does SAP ODP use for RFC connections?

SAP RFC uses port 33XX (XX = zero-padded instance number: instance 00 → 3300, instance 01 → 3301). Message server connections use port 36XX. Ask your SAP Basis team for the exact instance number.

If SAP is available from other machines but not the IR host, what should I check?

Check Windows Firewall outbound rules on the IR machine, NSGs on the IR subnet, and recent policy changes blocking RFC traffic. Run a traceroute from the IR host to identify where the path breaks.

Can this error occur if only some SAP application servers are down?

Yes — if the specific application server in the linked service is down, you get NotReached. Update the linked service to point to an available server or the SAP message server for load balancing.

Will downstream Power BI datasets be affected?

Yes — the pipeline fails without loading data. Dependent datasets will show increasingly stale data with each missed run.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide