Trouble with connecting a logic app with a on-premises data gateway (SAP)

Mateusz Iwankow 1 Reputation point


I have a problem connecting the on-premises data getaway with my logic app

The gateway is setup correctly considering the status (a screenshot below)

When trying to use the SAP send message, I'm constantly receiving this error message (screenshot below):

(this gateway is the correct one, there is just something wrong with naming)
I was setting up the connection with the help of this guide

and got through all the steps including coping the assembly files to the data gateway installation folder.

To fix this error I made sure I'm using the newest version of .NET framework and visual C++. The gateway is running on a 2019 Windows server. The credentials for the user are valid as well.

The x-ms-client-request ID is: CE4B56F1-297B-42FF-98D6-AF1C83098F92

The error message is:

Please check your account info and/or permissions and try again. Details: Failed to process request. Error details: 'Could not load file or assembly 'sapnco, Version=, Culture=neutral, PublicKeyToken=50436dca5c7f7d23' or one of its dependencies. The system cannot find the file specified.'. More diagnostic information: x-ms-client-request-id is 'CE4B56F1-297B-42FF-98D6-AF1C83098F92'.

Do you know a possible way of fixing this?

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,943 questions
{count} votes

2 answers

Sort by: Most helpful
  1. MayankBargali-MSFT 69,851 Reputation points

    Hi @Mateusz Iwankow

    Welcome to Microsoft Q&A! Thanks for posting the question.

    I have looked into backend logs and I can see the error coming from the gateway service.
    Please review the SAP compatibility and SAP client library prerequisites. As mentioned in the document you need to install SAP .NET Connector (NCo) library. Looks like this is missing, please install the SAP driver from here and then restart the machine as well as the on-premises data gateway.

    Please let me know if you are still facing the issue.

    Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

    1 person found this answer helpful.

  2. David Burg 406 Reputation points Microsoft Employee


    Beware to select the 64 bit version of the client assemblies. The 32 bit version looks just the same (same file names), but will not be possible to load from the 64 bit process of On-Premises Data Gateway.

    Indeed support engineers can help you in a screenshare session to go through the exacting installation steps. You can also self-help with Assembly Binding Logging, Fusion Log Viewer aka fuslogvw.exe
    This tool allows you to see exactly where the system is looking to find the assembly, it will list every file it attempts to load and the reason why a given load was not successful.

    With regards,


    0 comments No comments