Share via

How to fix error "ServiceProviderActionFailed" AIS to SAP in Production (working in Test environment)

Billard, Jeanne 0 Reputation points
2026-02-26T14:21:28.9233333+00:00

We are currently setting up our first IDOC in bound interface from AIS --> SAP. It is working in test and failing in Produciton. We do understand this is a connection issue. We are not able to identify the root cayuse, as there is no details on the message. "statusCode": "BadRequest",

    "body": {

        "code": "ServiceProviderActionFailed",

        "message": "The service provider action failed with error code 'ServiceOperationFailed' and error message 'Call to SAP client library failed with error message 'SAP server communication failed with error code '3' and error message 'RETURN CODE: 101 (no message)'.'.'."

    }

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Siddhesh Desai 4,815 Reputation points Microsoft External Staff Moderator
    2026-02-27T01:41:07.7633333+00:00

    Hi @Billard, Jeanne

    Thank you for reaching out to Microsoft Q&A.

    The issue occurs because the inbound IDoc interface from Azure Integration Services (AIS) to SAP Production is failing at the RFC communication layer, before SAP can process the request or create an IDoc. Although the same configuration works in the Test environment, Production environments typically have stricter network, firewall, and gateway restrictions. The error “RETURN CODE: 101 (no message)” indicates that the SAP .NET Connector (NCo) is unable to establish a successful connection with the SAP Production gateway. Since this failure happens during the initial connection handshake, SAP does not return any application‑level or IDoc‑level error details, which is why no information is available in SAP transactions such as WE02 or WE05 and the error message in Azure appears generic. This behavior is expected for low‑level RFC communication failures and usually points to connectivity, gateway configuration, or name/port resolution differences between Test and Production.

    Refer below points to resolve this issue or this is the workaround

    1. Verify network connectivity from AIS to SAP Production gateway Ensure that the AIS runtime or Integration Runtime machine can reach the SAP Production gateway host and port. Production firewalls often block SAP gateway ports even when Test allows them. Example check:
    Test-NetConnection <SAP_PROD_HOSTNAME> -Port 3300

    If this fails, the required gateway port must be opened on the firewall/network path.

    1. Use explicit gateway port instead of service name If the SAP connection is configured with a gateway service name such as sapgw00, service‑to‑port resolution may fail in Production. Configure the connection to use the numeric port directly (for example, 3300) to avoid DNS or OS‑level service resolution issues.
    2. Validate RFC destination configuration in SAP Production (SM59) In SAP Production, verify the RFC destination using transaction SM59 and ensure the correct application/message server host, system number, gateway host, and gateway service (port) are maintained. Use the connection test to confirm SAP‑side connectivity.
    3. Check SAP Gateway logs (SMGW) Use transaction SMGW in SAP Production to review gateway logs and confirm whether connection attempts from AIS are reaching SAP. If no attempts are visible, this confirms a network or firewall issue before SAP is reached.
    4. Confirm SAP user status and authorizations Verify that the SAP user used for the connection in Production is not locked and has the required RFC and IDoc authorizations, to rule out environment‑specific differences.
    0 comments
  2. Q&A Assist
    2026-02-26T14:21:42.54+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error indicates that the SAP .NET Connector (NCo) client library cannot successfully communicate with the SAP server in Production, even though the same setup works in Test. The root cause is almost always in network connectivity, SAP destination configuration, or gateway/service name resolution between the integration runtime / gateway host and the SAP system.

    Use the following checks and fixes on the machine where the SAP client libraries and/or on-premises data gateway are installed for Production:

    1. Verify basic TCP connectivity to the SAP gateway
      • From the Production integration runtime / gateway machine, test the SAP gateway host and port: 
             Test-NetConnection <sap-server-hostname> -Port 3300
      • Replace 3300 with the actual gateway port for the Production SAP system.
      • If this fails, resolve firewall, routing, or VPN issues so that the machine can reach the SAP gateway.
    2. Check service name vs. port number
      • If the connection uses a service name like sapgw00 instead of a numeric port, name resolution to a port might be failing.
      • Option 1: In the SAP connection configuration (Logic App SAP connection / API connection / app settings), replace the service name (for example, sapgw00) with the actual port number (for example, 3300).
      • Option 2 (if using on-premises data gateway): Add the mapping to %windir%\System32\drivers\etc\services on the gateway machine and restart the on-premises data gateway service, for example: 
             sapgw00  3300/tcp
    3. Verify SAP application server name resolution
      • If the SAP application or message server name does not resolve correctly to an IP address from the Production gateway machine, add host mappings in %windir%\System32\drivers\etc\hosts, for example: 
             10.0.1.9 SAPDBSERVER01
     10.0.1.9 SAPDBSERVER01.someguid.xx.xxxxxxx.cloudapp.net
      • Use the actual Production SAP server IP and hostnames.
    4. Confirm SAP NCo client library and prerequisites
      • Ensure the correct SAP NCo version and all required dependencies are installed on the Production gateway / runtime host, matching what works in Test.
      • If the NCo library is missing or mismatched, connection tests and calls to the SAP client library will fail.
    5. Validate SAP-side RFC destination and Program ID
      • In SAP (transaction SM59), confirm that the RFC destination for the Production interface points to the correct gateway host, service/port, and is reachable via Connection Test.
      • If using an inbound IDoc scenario with a registered Program ID, confirm in SAP Gateway monitor (SMGW) under Logged-On Clients that the Program ID from the Production workflow is registered as a Registered Server.
      • If it is not registered, check the on-premises data gateway status and the SAP connection configuration in the Production workflow.
    6. Compare Test vs. Production configuration
      • Compare, parameter by parameter, the SAP connection settings between Test and Production:
        • Application server / message server host
        • System number / gateway port
        • Client, system ID, and logon group (if used)
        • User credentials and authorizations
      • Any mismatch can cause the generic “SAP server communication failed” error.

    If, after these steps, the error persists, enable and review:

    • On-premises data gateway SAP adapter logs.
    • SAP Gateway trace logs (SMGW) for failed connection attempts from the Production gateway host. These logs will usually show the low-level CPIC/NCo error that corresponds to the return code 101.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.