question

MateuszIwankow-5181 avatar image
0 Votes"
MateuszIwankow-5181 asked DavidBurg-0118 answered

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

Hello,

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)
73780-azure1.png

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

(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

https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-using-sap-connector

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=3.0.0.42, 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-appsazure-sap
azure1.png (164.9 KiB)
azure2.png (57.4 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MayankBargali-MSFT avatar image
1 Vote"
MayankBargali-MSFT answered MayankBargali-MSFT commented

Hi @MateuszIwankow-5181

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.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MayankBargali-MSFT,
thank you for your fast respond!

I looked up the guide and everything should be fine. The SAP .NET Connector was also previously installed, but I used the 'repair' function in the installer to make sure it is working correctly.

Unfortunately, I'm still getting the same error message.

Best regards,
Mateusz

0 Votes 0 ·

Hi @MateuszIwankow-5181

Thanks for sharing the details. This needs to look be looked at from the setup/configuration and I will suggest you to open a support ticket with us so we can assist you further.

0 Votes 0 ·
DavidBurg-0118 avatar image
0 Votes"
DavidBurg-0118 answered

Hi,

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.

https://docs.microsoft.com/en-us/dotnet/framework/tools/fuslogvw-exe-assembly-binding-log-viewer

With regards,

David.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.