Error in Webservice Call HTTP error (return code 404, message conn failed)

Former Member — Tue, 17 Mar 2009 04:01:47 GMT

We wish to call a standard EP7 webservice through ABAP.

When we try to create consumer proxy , we get the following error.

*************************************************************************

HTTP error (return code 404, message "conn failed")

Message no. SPRX090

==> Display Error Document

If you want to generate a proxy for an external WSDL document by specifying a URL, check that the proxy settings of the system are correct (transaction SICF - Client - Proxy Settings). If you want to generate a proxy for an XI Repository object, check the connection to the Enterprise Services Builder as follows:

Check List for Setting Up a Connection to the Service Repository

1. The address of the Enterprise Services Repository must be known in the SAP system

Check with report SPROX_CHECK_IFR_ADDRESS

The address is taken from the following parameters in the exchange profile ('Connections' section):

com.sap.aii.connect.repository.name: Server (for example,pwdf0436)

com.sap.aii.connect.repository.httpport: Port (for example, 1080)

com.sap.aii.connect.repository.contextroot: Root (for example,rep)

The logon data is also read from the exchange profile ('ApplicationSystem' section):

com.sap.aii.applicationsystem.serviceuser.name: User

com.sap.aii.applicationsystem.serviceuser.pwd: Password

As an alternative to using the exchange profile, you can maintain the RFC destination SAP_PROXY_ESR. If this RFC destination is maintained it will be used by the proxy generation in place of data from the exchange profile to access the Service Repository. In this case, the Exchange Profile will even not be read.

The RFC destination has to be set up using transaction SM59 and should look like this:

RFC Destination: SAP_PROXY_ESR

Connection Type: G (HTTP Connection to External Serv)

Description1: ESR for Proxy Generation

Target Host: esr_host

Service No: 1080

Path Prefix: rep

Logon and Security:

Basic Authentication: active

User: esr_user

Password: esr_password

2. The HTTP Framework of the Web Application Server must function

Check with report SPROX_CHECK_HTTP_COMMUNICATION

If necessary, contact your system administrator. Please be aware of the fact, that the HTTP framework is depending on the application server. Thus the result of the report may differ for different application servers.

3. Proxy generation must interpret the data of the Enterprise Services Repository correctly

Check with report SPROX_CHECK_IFR_RESPONSE

you can also login in dev and go to Xn se91

enter msg id SPRX and msg no 090

select the message and click on long text..

you get the same message in a formatted manner..

*********************************************************************

How to get rid of this ?

Regards

Rajendra

Re: Error in Webservice Call HTTP error (return code 404, message conn failed)

Former Member — Tue, 17 Mar 2009 04:07:02 GMT

return code 404 means that the Web server can't find the page you request.

Maybe you called the wrong path.

Re: Error in Webservice Call HTTP error (return code 404, message conn failed)

Former Member — Tue, 17 Mar 2009 04:08:44 GMT

we have given the correct path as we have tested the webserive from

other technology (.net) by providing the same path.

regards

Rajendra

Re: Error in Webservice Call HTTP error (return code 404, message conn failed)

Former Member — Tue, 31 Mar 2009 05:55:50 GMT

Using IP Instead of hostname solved the prob.

Portal hostname entry is required in ECC6 to resolve the hostname.

Regards

Rajendra

topic Error in Webservice Call HTTP error (return code 404, message conn failed) in Application Development and Automation Discussions

Error in Webservice Call HTTP error (return code 404, message conn failed)

Re: Error in Webservice Call HTTP error (return code 404, message conn failed)

Re: Error in Webservice Call HTTP error (return code 404, message conn failed)

Re: Error in Webservice Call HTTP error (return code 404, message conn failed)