Security Compliance

Troubleshooting SAP connector Scan issues in ARM

This article provide steps on show to troubleshoot the SAP connector in ARM

First published date

5/6/2019 10:54 AM

Last published date

3/20/2025 12:37 AM

Overview

An ARM SAP connector which imports the user profiles, permissions-objects, permission-values and transaction of a SAP 3 System into ARM.

The import is based on the SAP-Basic-Function BBP_RFC_READ_TABLE. This method does not require any action within the SAP-System. The connector was developed and tested with SAP 3.

Product section

Access Rights Manager

Cause

Missing assemblies sapnco.dll and sapnco_utils.dll

Resolution

Problem 1: ARM Logs say "Sapnco.dll not found."
After downloading and installing the SAP .Net Connector 3.0 from the SAP Marketplace It is not possible to find the sapnco.dll and sapnco_utils.dll libraries.

Cause:
This happens when the libraries are installed into the "GAC" (Microsoft Global Assembly Cache). In this case they are not copied into the given installation directory, into the GAC. If the DLLs are required for development purposes, they should not be installed in the GAC. The GAC is only for programs that need the DLLs at runtime.

Resolution:
1. Uninstall NCo (just run the .msi file again and choose "Uninstall").
2. Reinstall NCo.
3. During the installation, when required, choose "None" instead of "Install into GAC". Then the files will be copied to the expected directory on the hard drive.

Problem 2: When connecting to SAP, the assemblies sapnco.dll and sapnco_utils.dll could not found.

Cause:
During the installation of ARM and the included package ARMSapConnector the two libraries are not installed.

Resolution:
- You may have to download the package NCo3021_Net20_x64.msi from the SAP Portal and install it on the ARM Server or used ARM Collector(s) for SAP scan.
- Link to SAP https://launchpad.support.sap.com/#/softwarecenter/search/sapnco
Unfortunately, a simple installation of the msi-package is not enough.

1. Install the MSI package NCo3021_Net20_x64.msi
2. Go to C:\Program Files\SAP\SAP_DotNetConnector3_Net20_x64 and copy the file sapnco.dll and sapnco_utils.dll
3. Paste the files into the folder C:\ProgramData\protected-networks.com\8MAN\technologies\server\someguid\63732467f6d84a659c85e7cdaa0f3cde\server\bin

The value for someguid can be found by looking in C:\ProgramData\protected-networks.com\8MAN\data\scanArchive and using the database guid from the folder located here, example a4091aeb-6361-4cb5-9638-cfe1e6d3c176

For further troubleshooting you may want to check the
Log messages of SAP-connector located in folder C:\ProgramData\solarwinds\ARM\tmp\sap8man\Logs

If you still see any problems with the SAP scan job, please upload the above logs + ARM server(or Collector used in scan) logs located in C:\ProgramData\protected-networks\logs

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.