What causes DF-SAPODP-DependencyNotFound?

The SAP NCo 3.0 or 3.1 library (sapnco.dll and sapnco_utils.dll) is not installed on the Self-Hosted IR host machine. The NCo DLLs are installed but in a location that is not in the system PATH or registered in the .NET GAC. The installed NCo version (32-bit vs 64-bit) does not match the bitness of the .NET runtime used by the IR. The NCo library was removed or corrupted during a system cleanup or antivirus action

How do I fix DF-SAPODP-DependencyNotFound?

Download the SAP NCo 3.1 library from SAP Service Marketplace (search for 'SAP Connector for .NET 3.1') — get the 64-bit version for a 64-bit IR host.. Install the NCo library on the Self-Hosted IR host machine — the installer registers the DLLs in the GAC automatically.. Alternatively, copy sapnco.dll and sapnco_utils.dll to the ADF Self-Hosted IR installation directory (C:\Program Files\Microsoft Integration Runtime\ \Shared\).. Restart the Self-Hosted IR Windows service after installing or copying the DLLs.. Re-run Test connection on the SAP ODP linked service in ADF Studio to confirm the dependency is now found.. If the error persists, check the IR host Event Viewer (Application log) for .NET assembly load errors that identify the missing component.

High severitydata source

Power BI Refresh Error:
DF-SAPODP-DependencyNotFound

What does this error mean?

A required component for the SAP ODP connector was not found on the Self-Hosted Integration Runtime host. This means the SAP NCo (NetWeaver RFC Connector) library is not installed or the DLL cannot be located, preventing ADF from establishing an RFC connection to SAP.

Common causes

1The SAP NCo 3.0 or 3.1 library (sapnco.dll and sapnco_utils.dll) is not installed on the Self-Hosted IR host machine
2The NCo DLLs are installed but in a location that is not in the system PATH or registered in the .NET GAC
3The installed NCo version (32-bit vs 64-bit) does not match the bitness of the .NET runtime used by the IR
4The NCo library was removed or corrupted during a system cleanup or antivirus action

How to fix it

1Download the SAP NCo 3.1 library from SAP Service Marketplace (search for 'SAP Connector for .NET 3.1') — get the 64-bit version for a 64-bit IR host.
2Install the NCo library on the Self-Hosted IR host machine — the installer registers the DLLs in the GAC automatically.
3Alternatively, copy sapnco.dll and sapnco_utils.dll to the ADF Self-Hosted IR installation directory (C:\Program Files\Microsoft Integration Runtime\<version>\Shared\).
4Restart the Self-Hosted IR Windows service after installing or copying the DLLs.
5Re-run Test connection on the SAP ODP linked service in ADF Studio to confirm the dependency is now found.
6If the error persists, check the IR host Event Viewer (Application log) for .NET assembly load errors that identify the missing component.

Frequently asked questions

Where do I download the SAP NCo library?

From SAP Service Marketplace (support.sap.com) — search for 'SAP Connector for Microsoft .NET 3.1'. You need an S-User account. Download the 64-bit version for a 64-bit IR host.

Why is SAP NCo not included automatically with ADF?

SAP NCo is a proprietary library requiring a separate SAP license — Microsoft cannot bundle it with ADF. Customers must download and install it from SAP Service Marketplace.

Does this affect only SAP ODP or all SAP connectors?

All SAP connectors in ADF that use RFC connections (SAP ODP, SAP BW, SAP Table, SAP HANA via SAP NCo) require the NCo library. Installing NCo once enables all of them.

Will downstream Power BI datasets be affected?

Yes — every SAP-sourced pipeline on this IR will fail without loading data. All dependent datasets will show stale data. MetricSign links the failed pipelines to their downstream datasets.

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