Forum Discussion

riaankotze10's avatar
riaankotze10
New Member
9 months ago
Solved

Powerbi Intergration with SAP

Good day,   I've installed the SAP . NET Connector 3.1 NCo. Up until the stage where i have to load the data or transform the data, i receive this error on most of my data sources. Please assist. ...
PowerrBi report server SAP BW
  • riaankotze10's avatar
    riaankotze10
    8 months ago

    Hi it is resolved thanks. It was an authorization issue from the security teams side.

v-kpoloju-msft's avatar
v-kpoloju-msft
Community Support
9 months ago

Hi riaankotze10,

Thanks for the additional details. The error you are seeing usually occurs when Power BI cannot load the correct SAP .NET Connector (NCo) 3.1 libraries. Even though you found the DLLs, the path you shared belongs to another SAP product, so Power BI cannot use those files for RFC/BAPI communication.

Install the official SAP NCo 3.1 package: Please make sure your team installs NCo 3.1 from the SAP Marketplace. Only the DLLs from this installer are supported by the Power BI SAP connector.

Match the installation with your Power BI bitness: If your Power BI Desktop is 64-bit, you must install SAP NCo 3.1 (64-bit). If it’s 32-bit, install the 32-bit version. A mismatch can trigger the exact error you’re seeing.

Ensure the DLLs are installed in the correct location: After installation, the assemblies should be in:

C:\Program Files\SAP\SAP .NET Connector 3.1\

and/or registered automatically in the .NET Global Assembly Cache (GAC).
If the DLLs are only inside the BusinessObjects folder, Power BI won’t detect them.

Once NCo is correctly installed and registered, Power BI will be able to read the SAP metadata and load the data without that error.

Hope this clears it up. Let us know if you have any doubts regarding this. We will be happy to help.

Thank you for using the Microsoft Fabric Community Forum.

v-kpoloju-msft's avatar
v-kpoloju-msft
Community Support
8 months ago

Hi riaankotze10,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

  • v-kpoloju-msft's avatar
    v-kpoloju-msft
    Community Support
    8 months ago

    Hi riaankotze10,

    Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

    Thank you.

    • riaankotze10's avatar
      riaankotze10
      New Member
      8 months ago

      Hi it is resolved thanks. It was an authorization issue from the security teams side.