cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to Call SOAP Adapter

nikhil_bose
Active Contributor
0 Kudos

in SOAP to SOAP, the wsdl is generated, when tested with XML SPy it gives error 500. and shows the message Failed to call Adapter Engine - Soap Fault.

can anyone trigger where the problem is?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Nikhil,

I think this is related with server which as encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.

Also there varoius reasons for this error, kindly refer to the link given below:

http://www.checkupdown.com/status/E500.html

Reward with points if helpful

Regards

Sai Ganesh

Answers (2)

Answers (2)

nikhil_bose
Active Contributor
0 Kudos

checked with TCPMON, the name space and the data element are different. The WSDL generated from ABAP was of RPC Style. When generated as Document style, it put the correct element and namespace which solved the problem.

thanks all

Former Member
0 Kudos

Hi Nikhil.

I feel that the system is unable to connect to the web service.

Try calling the webservice from the WSNavigator of your XI system and check if it is displaying the wsdl.

Go to http://xihost:port/wsnavigator and give the webservice url there and click next. If it displays the wsdl, then check your SOAP comm. channel config. else, check your server setttings.

Hope this helps.

Regards,

Hari.