Web service calls: Performing a problem analysis

"GET_BUSINESS_SYSTEM_ERROR An error occurred when determining the business system (SLD_API_EXCEPTION)"

Check the logical port in transaction LPCONFIG. Has it been created and linked to the correct HTTP connection? No standard port must be defined for the proxy class /AEB/CO_02IATCCONNECTOR_BF.

Only a green tick is displayed in the connection test in the SM59 for an SSL connection.

The service for HTTPS is not running.

'HTTPIO_PLG_CANCELED'

There is probably no service available for the required process (HTTP or HTTPs) or it is not active.

Also check the following: Is the connection in transaction SM59 really of type G? In transaction STRUST: are all PSEs below the SSL client green?

'Create failed: Argument not found'

The problem could be related to the service port – is the port correct, for example "443", or is there a spelling mistake (e.g. space)? Something may also be wrong with the SSL client specified in the destination. Check in transaction STRUST whether this SSL client is in the 'green' status? Have the AEB certificates also been installed there?

'ICM_HTTP_SSL_ERROR'

The problem may be related to the SSL certificates. Have all required certificates been installed in the STRUST? Has the ICM been restarted to reload them?

Furthermore, the correct SSL certificate list must be entered in the connection.

A fixed IP address was entered in the destination. However, for connections to the AEB data center, the host must be rz3.aeb.de.

'ICM_CONNECTION_FAILED' and 'NIEHOST_UNKNOWN’ in the log file dev.icom.

The name resolution for the host address rz.aeb.de does not work because DNS is not set correctly. The problem could also be related to the fact that a proxy is required to connect to external websites. If this is the case, the proxy parameters must be stored in the SM59 destination.

'ICM_HTTP_CONNECTION_FAILED' and 'NIECONN_REFUSED’ in the log file dev.icm.

You may have forgotten to activate SSL in the destination. Furthermore, the correct SSL client certificate must also be selected there.

The firewall may block the connection to the target system. The port of the target system may not be released.

'ICM_HTTP_CONNECTION_FAILED' always occurs

There are several possible causes. For example, the problem could be related to the port entered in transaction SM59. Has the correct HTTPS port 443 or the correct HTTP port of the target system been entered there? Or is a proxy required for connections?

‘ICM_HTTP_CONNECTION_FAILED’ occurs only sporadically

The ICM_HTTP_CONNECTION_FAILED error means that no connection could be established between SAP and the target system. If this message occurs only sporadically, this may be a problem at the TCP level of the server running your AEB application.

Microsoft documents a parameter in the registry for Windows to release TCP connections after a certain waiting time: https://technet.microsoft.com/en-us/library/cc938217.aspx Since the value is usually set to 120 seconds, a reduction of the waiting time can solve the problem.

'ICM_HTTP_TIMEOUT'

The error may be due to the proxy used, where the SSL certificates must be known. The proxy must not store obsolete certificates. If this is the case, remove them from the certificate store, even a decryption of the SSL connection can lead to the error.

Scenario: The system has several instances, for example, central and dialog instances. The connection test in the dialog instance is OK, but errors still occur when AEB jobs run.

Everything is set up correctly in the dialog instance, but not in the central instance. This is where the jobs or message processing run. Log in to the central instance for the test and check all settings in SM59. The HTTPS service in SMICM is set up and started locally for each server. This means that the HTTPS service may run in the dialog instance, but not in the central instance.

The connection test is successful, but a connection error occurs when calling functions of the AEB application, e.g. "..not reached" or "CX_AI_SYSTEM_FAULT".

Check whether a port has also been created for the destination (see transaction SOAMANAGER or LPCONFIG and the corresponding description in the installation guide).

Unsupported xstream found: (HTTP Code 200 : OK)

One possible cause is incorrect SSL settings in the connection or the logical port.

SOAP:1.007 SRT: Unsupported xstream found: (HTTP Code 404 : Not found)

An incorrect path prefix has been entered in the destination or logical port.

SOAP:1.007 SRT: Unsupported xstream found: ("HTTP code 403: forbidden")

In the path prefix, the name of the target system is missing or has been entered incorrectly.

Entry in the log file dev.icm: ‘the verification of the server’s certificate chain failed’ or ‘Untrusted Chain PEER_CERT_UNTRUSTED’

The SSL certificates have not been imported correctly or not all of them are known in the PSE. This error is also described in more detail in SAP Note 1094342.

SOAP:1.023: SRT: Processing error in Internet Communication Framework: (‘ICF Error when receiving the response: ICM_HTTP_CONNECTION_BROKEN’)

This error means that the already established connection has been interrupted. Most likely this is because there are short interruptions in the network or Internet connection. The error may also occur if the password of the connection user is incorrect.

ICF Error when receiving the response: 'ICM_HTTP_CONNECTION_FAILED'

Error pattern: There are interruptions at regular intervals. In between, however, many calls also work. The ICM log contains the error message NIECONN_REFUSED for the affected user, but with the IP address of the proxy server. This user does not have the authorization to establish an external connection via the proxy.

SOAP:1.013 SRT: ASSERT failed: field is initial

See also SAP note 921347

SOAP:1.008 SRT: Couldn't create Object: ICF error when creating HTTP client object by config for URL

Check the settings in SOAMANAGER for the logical port, including the transfer log and the binding type. See also SAP note 2469949:

For example, a pop-up appears during the connection test in SAP and prompts for the user and password for the connection

1. An incorrect password of the connection user has been stored in SM59 or SOAMANAGER

2. The AEB solution runs in the AEB data center and the connection user does not have the I_BUSINESSFACADE role in the AEB application.

SOAP:1.036 SRT: HTTP Code 415: ("Unsupported Media Type")

In SOAMANGER, SOAP 1.2 is set instead of SOAP 1.1.