Register Login

SOAP/HTTP error while calling/consuming a web service in ABAP System?

Updated May 18, 2018

Hello Experts,

What could be the possible reason for getting SOAP/HTTP error while calling/consuming a web service in ABAP System?

What are the various types of SOAP/HTTP errors which occur while calling a Web Service, and how can they be resolved?


Comments

  • 06 May 2016 5:05 pm Sugandh Helpful Answer

    The error may occur if either the Consumer or the Web Service Provider has been configured in the SOA Manager. It is also possible that the system is not properly configured which makes it unable in calling a web service in question.

  • 06 May 2016 5:06 pm Abhijeet Mudgal Helpful Answer

    The different types of errors which mainly occur while calling Web services and their possible solutions are listed below:

    1. ICM_HTTP_PROXY_UNAUTHORIZED:

    For this type of error, the following steps need to be performed:

    • The proxy settings of the system (transaction SICF->F8->Client->Proxy Settings) or the proxy settings in the logical port in SOAMANAGER (transaction SOAManager ->Service Administration->Web Service Configuration) should be checked.
    • Then, Consumer Proxy option should be selected and the Consumer Proxy Name should be specified.
    • Then the relevant configuration should be selected (Logical Port) ->display->Transport settings).
    • There can be instances in which user Proxy host, Proxy Port, user name or Password is missing.
  • 06 May 2016 5:08 pm Abhijeet Mudgal Helpful Answer

    2. “HTTP Code 401: Unauthorized":

    This error usually occurs when the Web Service provider system has an authorization issue. In order to get the error resolved, following steps need to be performed:

    • The credentials/security method should be checked, which are maintained in the logical port via SOA Manager (transaction SOAManager ->Service Administration->Web Service Configuration)
    • Then, Consumer Proxy option should be selected and the Consumer Proxy Name should be specified.
    • Then the relevant configuration should be selected in the consumer system (Logical Port) ->display->Transport settings).

    3. ICM_HTTP_SSL_ERROR:

    To investigate and solve the issues related to SSL setup, one should have a look at 1318906.

    4. IDoc communication with SAP Business ByDesign:

    The communication between a SAP Business ByDesign system (as of FP 2.6) and a system with SAP NetWeaver 7.00 or higher, can be enabled via 1510812. 

    5. HTTP Code 403 Forbidden:

    This error indicates that the server has understood the request, but is declining to fulfill it. This is not considered as an Authorization issue. It completely depends upon the server to describe the reason for the refusal. If server is an ABAP system then it can likely be that the ICF node applicable for this service is not active in SICF transaction. Solution for this problem must be done on the service side. For example, all relevant ICF nodes in transaction SICF often need to be activated by an ABAP service provider.

  • 06 May 2016 5:08 pm Abhijeet Mudgal Helpful Answer

    6. ICM_HTTP_CONNECTION_FAILED:

    This error indicates that an HTTP connection between consumer and provider system has not been established. There can be a number reason for this issue like usage of invalid host or http port, wrong proxy settings etc. 

    In order to find the solutions in such circumstances, one should contact the Network Administrator who understands the setup of the entire Network.

    7. ICM_HTTP_SERVICE_UNAVAILABLE:

    This error occurs when the provider system is unable to process the http requests. In such scenarios one should contact the respective Administrator of the provider system, to get a solution.


×