cancel
Showing results for 
Search instead for 
Did you mean: 

Http-500 internal server error

0 Kudos

Hi Gurus,

  While executing IDOC->SOAP scenario these errors are holding the messages.

SOAP receiver channel getting error "

Exception caught by adapter framework: SOAP: Response message contains

an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal

Server Error.



  New WSDL has been imported to existing running interface and its failing  .It is triggering this error. new Soap action was updated under the channel.

 

  the wsdl file tested using SOAPUI and its giving response http :200. url of soapui and target soap PI channel are same. Observed while testing under Soapui.


  Applied changes suggested  by scn posts still no luck to overcome this error.Please suggest is it config issue or some other.



thanks,

aman

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Did Delta cache, stop and start the channel also updating the soap action and activation makes data processing with out issues. Still wondering what might be the root cause. Thanks for help to all.

Answers (5)

Answers (5)

0 Kudos

Except XPI inspector I applied all the suggested ones, still no luck. having same issue.

@Maheshwar

  Tested with soapui it gave http response 200.

former_member207701
Participant
0 Kudos

Hi Aman,

So  you can cross check the payload between SOAP UI and PI system as Inaki suggested check in RAW tab in soap ui you get more details in that tab like content-type header details etc etc.

or also you may end up creating custom soap envelope as it looks in soap ui.

Br,

Kiran

iaki_vila
Active Contributor
0 Kudos

Hi Aman,

Are you setting the SOAP action in the same way that the SOAPui's way?

Have you checked minutely the output payload between SOAPui and PI test?, pay attention to the namespaces.

Have you tried to refresh CPA cache, stop and restart the channel?

Regards.

maheswarareddykonda
Active Contributor
0 Kudos

there would be problem with content type of data, actually by default channel content type is application/xml which is probably not matching with your target server.

have you tested in soap ui tool?

Former Member
0 Kudos

Hello Aman,

Can you please refer following SAP note:-

1533195 - Receiver SOAP adapter in no-soap mode: target system faults

This might help you.

Regards

Anand

engswee
Active Contributor
0 Kudos

Hi Aman

Firstly I'd suggest that you add TraceHTTP parameter to your SOAP channel so that you can get further details on that error.

If that still does not help you, go for XPI Inspector as the next step so that you will be able to access more log details.

Rgds

Eng Swee