SAP Connection

You need to download and install the SAP .Net Connector for .NET 4.0 on x64, with at least version 3.0.15.0.

All necessary steps are documented in the SAP Administration guide.

Please note that the same requirements apply, in regards to the SAP .NET Connector for .NET 4.0 Dlls, for the client machine when you are configuring the Synchronization Project without a remote connection.

https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.1.1/administration-guide-for-connecting-to-sap-r3#TOPIC-1253370

https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.1.1/administration-guide-for-connecting-to-sap-r3/2#TOPIC-1253371

https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.1.1/administration-guide-for-connecting-to-sap-r3/2#TOPIC-1253372

https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.1.1/administration-guide-for-connecting-to-sap-r3/2#TOPIC-1253374

Markus Weiss-Ehlers said:

You need to download and install the SAP .Net Connector for .NET 4.0 on x64, with at least version 3.0.15.0.

Makus, tank you for your help. This is my first project with OneIM.
The SAP .NET connector. Where should it be installed, on the SAP server?

Please check the links in my answer. It's all there.

Hi Markus.

 I have installed the module: SAP .Net Connector for .NET 4.0 on x64, with at least version 3.0.15.0. as indicated in the guide and the connection still does not work. The error when doing the test is the same as always

Did you install the assemblies to the GAC during the installation? It‘s a check box option in the SAP setup as far as I remember. 

Thanks Markus. I review the installatión and check de GAC option.

Hello Markus,

I have exactly the same problem as Alberto. Your links are currently leading nowhere.

The following environment with me:

• Windows Server 2019 Datacenter
• x64-based processor
• Installed One Identity Tools Version: 8.2.1
• SAP .NET Connector 3.1 for x64 Version 3.1.2.0 installed
• The following files are stored in the One Identity Manager directory (the first three are also in the GAC)
  • sapnco.dll, Version 3.1.2.0
  • sapnco_utils.dll, Version 3.1.2.0
  • rscp4n.dll, Version 1.1.1.0
  • libicudecnumber.dll, Version 7850.212.32.56810

Worked through the following documentation:

1. https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.2/administration-guide-for-connecting-to-sap-r3
2. https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.2/administration-guide-for-connecting-to-sap-r3/2#TOPIC-1724200
3. https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.2/administration-guide-for-connecting-to-sap-r3/2#TOPIC-1724206
4. https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.2/administration-guide-for-connecting-to-sap-r3/3#TOPIC-1724208

Dokulink under 4 only partially worked through.

Connection via SAP R\3 message server, all required fields filled in.

Up to the point where the connection is tested (test of the connection). The result is the error under [1].

Can you help me here?

What surprises me is that it reports a problem with sapnco version 3.0.0.42 in the error, even though sapnco.dll, version 3.1.2.0 is in the One Identity directory.

[1]

Exact error message:

[System.IO.FileLoadException] Could not load file or assembly 'sapnco, Version=3.0.0.42, Culture=neutral, PublicKeyToken=50436dca5c7f7d23' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

When i installed SAP .NET Connector 3.1 for x64 Version 3.1.2.0 there wasn't a step to check box for selecting the assemblies to be installed in the GAC.

Hi Alexander,

you probably installed the SAP NCo V3.1 connector which is not released in One IM 9.1 yet. Please uninstall it and download / install the SAP NCo V3.0 connector (Patch 25).

Regards,

 Tino

Hi Tino,

that seems to have been the solution to the problem. With SAP Connector for Microsoft .NET 3.0.25.0 for Windows 64bit (x64) this error no longer occurs, but another one does. But that would be a case for another forum thread.

Thank you for your help.