SOAP Receiver error - HTTP 500 Internal Server Error

[PratibhaK]

Hi,

We have a FILE to SOAP Asynchronous scenario to send data from our PI to customer PI.

We are sending PGP encrypted file as the payload. So, foll settings have been maintained:

Do not use SOAP envelope in Sender and Receiver SOAP

nosoap=true in the URL.

Message transform bean in the SOAP channels.

File is successfully sent and received through SOAP protocol.

But, both the SOAP Receiver and Sender channels are in error:

SOAP Receiver error:

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error.

As, this is a asynch scenario, we are not expecting the response.

SOAP sender at customer PI is in error. Error text is not mentioned. It just displays: error occured.

At both the ends, we do not have Repository objects as there is no mapping.

Kindly help...

Thanks,

Pratibha.

[Former Member]

Hi,

This error occurs when your webservice call doesn't accept the SOAP service, Either SOAP Service is not active stage or WS call format is not correct,

Regard's

Sateesh

[PratibhaK]

Hi Sateesh,

SOAP service is not in active stage - how can i check this?

WS call format is not correct - by this, u mean the URL, right?

Also, if any of these were true, still the File would be delivered successfully? as it is getting in our case...

Thanks,

Pratibha.

[PratibhaK]

Hi All,

I have applied the SOAP Adapter Bean parameter and the error in the Receiver channel is gone but, the error persists in the SOAP Sender channel at the customer end.

Please suggest.

Thanks,

Pratibha.

[Former Member]

Hi Pratibha,

 SOAP Receiver error:
SOAP: response message contains an error 
XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. 

Just Check the Adapter Specific Identifiers for your sender and receiver SOAP Channels. (Don't check the Variable Transport Binding.)

The error should be gone.

[PratibhaK]

Hi All,

For the same scenario, we need to Sign the data using the WebServices Security.

(We are sending PGP encrypted data as SOAP payload using MTB, i have ticked "Do not use SOAP envelope")

I have selected WebServicesSecurity as the security profile in the SOAP Receiver and selected "Sign" in the Receiver agreement, have provided our private cert.

Tried sending a message. Communication channel audit Log shows the message:

Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

Success SOAP: request message entering the adapter with user J2EE_GUEST

Success SOAP: Web Services Security processing...

Success SOAP: Web Services Security processing skiped. Empty body...

Success SOAP: completed the processing

Please suggest how I can apply the WSS..

Thanks,

Pratibha.

[baskar_gopalakrishnan2]

>> SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error.

The error could be due to various reasons at the target system. If the target system goes for running a large report and having dump stack errors, you might get this type of error intermittently. Use wsdl in soapui or xmlspy and test locally.

Steps:

a) If your test goes well with soapui or xmlspy, use that WSDL in soap receiver comm channel.

b) if you dont find any operation in wsdl , please leave blank in action field of soap receiver.

Hope this helps.

[PratibhaK]

Thanks Baskar..

But, I have mentioned that, both we and customer are NOT using the Repository objects. So, we do not have the WSDL.

Moreover, file is successfully transmitted.

Only that, both the Sender and Receiver SOAP channels are into error.

Please suggest..

Thanks,

Pratibha.

[Former Member]

I can think of a couple of things:

1. WS is not accessible by PI. Can you try to test the WS using a SOAP UI client ?

2. The format in which you sending the data to WS is not accepted by WS.

[Former Member]

>

> I can think of a couple of things:
> 1. WS is not accessible by PI. Can you try to test the WS using a SOAP UI client ?
> 2. The format in which you sending the data to WS is not accepted by WS.

I agree