SOAP Envelope - HTTP_EXCEPTION - HTTP 500 Internal Server Error

Pessoal, o cliente em que estou utiliza uma solução para NFe que não é o GRC.
Para tentar solucionar o problema do SOAP 1.2 e do message header, estou tentando criar o SOAP Envelope utilizando um XSLT, e no Communication Channel eu estou flegando Do not use soap envelope e colocando os modules para os charset, assim como na nota da SAP.
O que está ocorrendo é que estou tendo o seguinte erro:
com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Conversei com um rapaz na SEFAZ e ele diz que não está chegando nada pra ele.
O SOAP Envelope que estou mandando é:
está dentro de tags CDATA.
Alguém saberia o que está ocorrendo?
Muito obrigao,
Leandro Rocha

Olá Henrique, muito obrigado pela rápida resposta.
O erro que dá no audit log é:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. Setting message to status failed.
A mensagem que aparece no adapter é a padrão do SOAP Document:
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
- <SAP:Main versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:TimeSent>2010-11-04T13:36:35Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="" scheme="" />
<SAP:Service>NFe_recepcao</SAP:Service>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SEFAZ_RS</SAP:Service>
</SAP:Receiver>
<SAP:Interface namespace="http://www.gerdau.com.br/nfe">NFe_recepcao_inbound_sync</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Diagnostic SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:HopList SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2010-11-04T13:36:39Z" wasRead="false">
<SAP:Engine type="PE" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">PE</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2010-11-04T13:36:39Z" wasRead="false">
<SAP:Engine type="IS">is.00.ebsgerd26</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2010-11-04T13:36:41Z" wasRead="false">
<SAP:Engine type="AE">af.p7d.ebsgerd26</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
</SAP:Hop>
</SAP:HopList>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:payload-DFE818873F6A21F1B9330050568169B4">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Mais uma vez, muito obrigado,
Leandro

Similar Messages

ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error, in Receiver soap A

Greetings All,
In my scenario i am calling external service of SFDC using receiver soap adapter but i am facing below error in the response.
ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error
I am creating the soap structure/envelope using Java mapping since need to add additional parameter in soap header.
I am setting the URL in java UDF using parameter TServerLocation.
In comm channel checked "do not use soap envlope" also set the format to text/xml using MessageTransformBean.
The service was working fine when tested in SoapUI tool.
Looking forword for your help and will be appreciated.
Thanks,
Sandip

Hello Sandip, I hope you are doing fine!
I`m not sure if you are using a sync or async scenario...
The behavior that you describe is the expected behavior for SOAP receiver adapter in nosoap mode, asynchronous case.
The explanation that lies behind it is that in nosoap mode the bahavior is just similar to pure HTTP communication. An HTTP 4/5 error received from the target server is treated as HTTP internal error and logged into AFW as an error. The message in an asynchronous scenario without acknowledgements is normally seen as successful on IE side as it is successfully sent to the target system. It can be even successfully consumed by the target webservice, but for amo other reason, the HTTP request from SAP PI to the target system returns HTTP 500 error.
If you ask for system delivery acknowledgements, you should get a non-successful delivery acknowledgement.
In synchrnous scenarios, when a response is expected, the behavior is different.
If this is a sync scenario, there is an official patch released on the service marketplace. SAP Note 1533195 is released.
In addition to deploying the patch, apply the additional configuration steps. As per this note, for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
you will need to set:
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
If you need to bypass the HTTP errors in the communication with the target system, you need to apply note 1055678.
To apply it, just add for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean in your receiver
channel, Modules tab the following:
Module Key = soap
Parameter Name = XMBWS.NoSOAPIgnoreStatusCode
Parameter Value = false
If you need any SOAP fault related behavior or any other SOAP related feature, you should setup the channel to run normal SOAP mode, since as already mentioned nosoap mode is used now.
In addition, check note:
856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
section "1. Sender Connection"
Q: I get a server error "500 Internal Servler Error" from the
adapter's servlet. What went wrong?
and get the trace to give you more details of the error.
One more thing, VERY IMPORTANT.
I STRONLGY recommend you to update all XI-PI components to latest patch available in the Service Marketplace. Thery are:
XITOOLS, XIESR, XIAF, XIAFC, MESSAGING, XIGUI. Some of them might not be present depending on the release of you system. e.g: 3.0, 7.0, 7.1
I hope this helps you.
Cheers
Jorge Eidelwein

WSRM Adapter replaced with soap in PO7.4. Getting error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"

Hello All,
We have scenario proxy->pi->webservice. In older versions of PI system they used wsrm adapter at receiver side and it's working fine.
Receiver interface is asynchronous. So no response structute is present and receiver service is business component(since receiver is a third party).
During migration, we have replaced the receiver adapter with SOAP adapter and used message protocol as SOAP 1.1 but the message is failing and in communication channel it is showing error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error". In this case the receiver interface is stateless xi 3.0 compatible(re using the old), after changing it to just stateless also issue persists.
In target url field if i prefix the url with "http" then above mentioned error is occurring otherwise if i use the hostname:port/path.. then it is giving error
"soap: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: Unsupported protocol". So maintaing the url as http://hostname:port/pat.....
As in old channel wsrm channel there is no userid and password, i haven't given any userid/pwd in receiver channel.
used the bean sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean with parameters
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
and
xmbws.No SOAPIgnoreStatus = true
but not successful.
Please help me. I got stcuk here.

Hello Jannus,
The connectivity is working fine. Network team has confirmed it. I doubt that any strucutre(header) difference might be present in message when sending with wsrm adapter compared to sending with soap adapter.
Please let me know the exact difference between soap and wsrm functionality in receiving end.
By considering the structure issue, i have checked the "do not use soap envelope" check box, then i got error "Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type"
Then i used message transform bean, but not successful.
Regards,
Ch.Venkat.

Invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

Hi,
I have this error on a SOAP Receiver Channel: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
I've found several threads on SDN Forums about similar errors, but I did not find a solution for my problem yet.
I checked this blog: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009 Pt.6 applies to my situation, but the proposed solution doesn't solve the problem.
TRACE Messaging System
u2026
2011-06-06 10:59:41.822 Success Delivering to channel: CC_SOAP_RCV_XXX
2011-06-06 10:59:41.823 Success MP: entering1
2011-06-06 10:59:41.825 Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2011-06-06 10:59:41.828 Success SOAP: request message entering the adapter with user J2EE_GUEST
2011-06-06 10:59:42.012 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
2011-06-06 10:59:42.014 Success SOAP: sending a delivery error ack ...
2011-06-06 10:59:42.014 Success SOAP: sent a delivery error ack
u2026
Message Details
Address   http://aaa.bbb.be:54000/MessagingSystem/receive/AFW/XI
Credential   PasswordCredential(PIISUSER):password=********
Transport Headers   accept-encoding=gzip sap-xi-messageid=4DEA11FE90003094E10000000AE908B4 content-length=7520 http=POST host= aaa.bbb.be:54000 user-agent=SAP NetWeaver Application Server (1.0;711) content-type=multipart/related;boundary=SAP_4DEA47CEAD3A5138E10000000AE908B4_END;type="text/xml";start="" soapaction="http://sap.com/xi/XI/Message/30"
Configuration Details SOAP Communication Channel
SOAP Receiver Channel
No modules configured
Do not use SOAP Envelope -> NOT checked
If I type the target URL in browser it opens (no login required) and I see the available web services.
Anyone any idea what's the reason for this error?
Thanks in advance
Kind Regards
Edmond Paulussen

Hi Edmond,
We faced similar problem & found alternative.
Try out, if it works for u as well.
1) Use HTTP Adapter instead of SOAP.
Transport Protocol : HTTP 1.0
Message Protocol : XI Payload in HTTP Body
Adapter Engine : Integration Server
Addressing type : URL Address.
Target Host:
Service Number :
Path Prefix:
Authentication type : we hv used Ananymus login, as our login details in payload header.
Content Type : application/soap+xml;charset=UTF-8( this is IMP).
Header Fields.
Name         value
Host           target host
XI Payload Manipulation
XML Code : UTF-8
Hope, this helps...
-santosh.

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

I'm getting this message in RWB when trying to send an order:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Weird thing is, other orders have been successfully to the same partner.
Is this something on my side or the receivers side?
What does HTTP 500 Internal Server Error mean and how to fix?
Thanks,
Jeff

More info on this problem:
Discovered that the HTTP 500 error only occurs when a "change" file is sent:
I send an order create file to a partner using a SOAP adapter. They receive it successfully.
I make a change to the sales order and send that file. It uses the same Config Scenario, receiver determination, receiver agreement and comm. Channel.
But this file shows an HTTP 500 error in the RWB.
I send it right after the first order create file, so no overloading is happening, etc.
Conenctivity to the url is fine because the create file went through.
I don't know what else it could be. Any other info/log in RWB to look at to help decipher the error?

ADAPTER.HTTP_EXCEPTION & HTTP 500 Internal Server Error

Hi,
I am working RFC-TO-SOAP(Synchronous scenario) when I try to test this scenario from SE37 using rfc destination I am getting the below error.(from SOAP Response)
In SXMB_MONI the below error is coming...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>HTTP 500 Internal Server Error</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
same scenario when I try to test from Component monitoring in RWB using sender RFC request payload I am getting the response from webservice. It is showing successfullly messages in SXMB_MONI.
I have created TCP/IP Connection that is working fine..
Please can any body through light on this error.
Regards,
Venu.

Hi,
Request message is going to webservice when response is coming back from webservice it is giving me error.
Response Meg ID.
Inbound Message -> Here is the error.
In Response Inboun level it is failing.
RFC sender side adapter right - Yes and I am getting the RFC Request message in SXMB_MONI also the same Request message If test from RWB I am able to see success messages in SXMB_MONI.
Regards,
Venu.

SOAP Receiver error - HTTP 500 Internal Server Error

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.

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.

HTTP 500 Internal Server Error with Large Attachment in SOAP Scenario

Hi,
we have implemented SOAP - XI - SOAP Scenario in our landscape (Sap Neatweaver Process Integration 7.1) .
One of the functionality of this scenario is the Upload of Documents to External Web Service through standard SOAP Attachment.
If we try to upload a small file (smaller than 20MB), task works fine and the document is correctly uploaded.
If we try to upload a larger file, we encountered in this generic error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)
We tried to increase timeout parameters (in communication channel and in ICM Value) but the response is the same.
We verify also if icm/HTTP/max_request_size_KB parameter was set to a value smaller than our file size limit (20MB) but is set to default value (100MB).
The problem isn't on External Web Service Layer because if we try to upload the same documents directly to that web service upload works fine, and in External Web Service's Log there aren''t any indications of this error.
So I ask you: are there any System Parameters to verify to solve this issue?
For additional, in ICM Monitor LOG we can read this WARNING when we call our service:
WARNING => IcmReadFromConn(id=53/454390): temporarily out of MPI buffers -> roll out [icxxthrio_mt 2646]
This warning may be related to the problem? If yes, how can we solve it?
Thanks a lot,
Marcello Ricci

Hi ,
Please answer my following questiosn.
1) which PI version are you using?
2) How many J2EE nodes you have.
please be reminded that SOAP is not for the heavy messages. Then you need to increase your timeout parameters from BASIS.
Rgds
Veeru
Edited by: viru srivastava on Dec 14, 2010 10:18 PM

Http 500 internal server error while calling webservice

I have a scenario Rfc to webservice
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>HTTP 500 Internal Server Error</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In my response pay load i am getting error msg
<b>ClientUnable to parse the incoming request. Please make sure that the request is valid: javax.xml.soap.SOAPException: Unsupported Content-Type: application/xml</b>
</env:Envelope>
Can any one please tell me what would be the problem i have doubled checked the scnrio,i message monitoring i have a messages
Audit Log for Message: ec1dc1d0-f1c7-11da-91dd-0004ac577b32
Time Stamp Status Description
2006-06-01 16:39:52 Success The message was successfully received by the messaging system. Profile: XI URL: http://saptst01.internal.pcshs.com:51000/MessagingSystem/receive/AFW/XI
2006-06-01 16:39:52 Success Using connection AFW. Trying to put the message into the request queue.
2006-06-01 16:39:52 Success Message successfully put into the queue.
2006-06-01 16:39:52 Success The message was successfully retrieved from the request queue.
2006-06-01 16:39:52 Success The message status set to DLNG.
2006-06-01 16:39:52 Success Delivering to channel: ZCH_VERISIGNPPGR
2006-06-01 16:39:52 Success Transform: using Transform.Class: com.sap.aii.messaging.adapter.XSLTConversion
2006-06-01 16:39:52 Success Transform: transforming the payload ...
2006-06-01 16:39:52 Success Transform: successufully transformed
2006-06-01 16:39:52 Success SOAP: request message entering the adapter
2006-06-01 16:39:53 Success SOAP: completed the processing
2006-06-01 16:39:53 Success SOAP: response message received ec89a301-f1c7-11da-a561-0004ac577b32
2006-06-01 16:39:53 Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
2006-06-01 16:39:53 Success The message status set to DLVD.
2006-06-01 16:39:53 Success The message was successfully delivered to the application using connection AFW.
Any help would be greatly appreciated.......
Thanks
sriram

Hi,
Content-Type: application/xml
...check for the content type of the message that is sent ot the WS.....with the above mentioned content-type going to the WS currently...WS is not able to parse the req and hence the error....in other words wrong format being being passed.
Regards,
ABhishek.

Conexão SEFAZ Virtual-RS - HTTP 500 Internal Server Error

Bom dia pessoal,
Desde ontem, por volta de meio-dia, não conseguimos mais conectar na SEFAZ Virtual RS (todos os estados que a utilizam). Antes deste horário, a conexão era feita com sucesso.
Olhando na SXI_MONITOR, o erro é o seguinte:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Alguém está com o mesmo problema ou se não, o que pode causar erro HTTP 500?
Obrigado.

Bom Dia Ricardo,
Estou tendo o mesmo problema que você mencionou. Só acrescentando, isso está ocorrendo apenas para o ambiente de Homologação e para a versão 2.0.
Att.,
Cristian.

HTTP 500 Internal Server Error in SXMB_MONI

Hello,
Getting HTTP 500 Internal Server Error while running some Synchronous Scenario of ECC -> PI -> Legacy system (SOAP adapter). Following are the errors received in SXMB_MONI.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Both the errors are not regular but comes up every now and than. If the scenario is re-run from ECC than it works.
Please advise.
Thanks a lot

Thanks a lot Nidhi. I am looking at the notes provided.
Thanks a lot Lars. Please find the content of HTML content:
java.lang.ClassCastException: class com.sap.engine.interfaces.messaging.spi.transport.TransportHeaders:interface:com.sap.aii.af.ms.ifc9(at the rate)com.sap.engine.boot.loader.ResourceMultiParentClassLoader(at the rate)6f9702b1(at the rate)alive incompatible with class com.sap.engine.interfaces.messaging.spi.transport.HTTPHeaders:interface:com.sap.aii.af.ms.ifc(at the rate)[email protected]1(at the rate)alive
     at com.sap.engine.messaging.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:447)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
     at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Regards

SOAP to RFC Scenerio: HTTP 500: Internal Server Error

Hi Experts,
    I am facing HTTP 500:Internal server Error. We have SOAP to RFC Scenerio. Interface is working fine, suddenly we are facing this error in Interface. On XI server side - ABAP and JAVA stack are on same Service Pack(SP 13). There is no change done in WSDL and RFC Structure and Mapping side.
Please suggest to resolve this Issue.

Hi Subbu,
   I have found this error in adapter monitoring??.. Please find my finding of XI server related to this below:--
*Error categaory - XI_J2EE_MESSAGING_SYSTEM
Error Code - CALL_ CONSUMER _ERROR
Error :Returning synchornous error notification to calling application:com.sap.aii.af.ra.ms.api.RecoverableException: RecievedHTTP Response code 500:internal Server Error.*
   I have refresh the cache already, but problem still exists.
   Please suggest how to resolve this error.

Catch HTTP 500 Internal Server Error

Hi,
in our RFC->XI->SOAP scenario we want to call a WebService from XI via SOAP Adapter. If an error occurs on the webserver, I receive a SAP error message with the following text:
com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint: HTTP 500 Internal Server Error
This causes a shortdump in R/3. Is it possible to catch this error in XI and avoid the shortdump in R/3?
Regards,
Carmen

Hi Carmen,
if u have a bpm at xi, u can define an exception branch in ur block, where u fill a error message, which should be response for rfc. So u avoid dump and ur programm can handle the error.
Regards,
Udo

Failed to call the endpoint: HTTP 500 Internal Server Error

Hi,
We are working with a scenario that use the SOAP adapter to call a web service from XI.
This scenario is working 98% of the time but sometimes we get the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint: HTTP 500 Internal Server Error
I do not think this is a network issue as we resubmit the workflow from SXMB_MONI_BPE and the error is the same. If it was a network issue I guess this would resubmit successfully.
Does anyone have an idea what could cause this intermittant error ?
Also, this is not an easily reproducable error so there is no point raising an OSS call as SAP will need a reproducable example which we cannot easily do.
Any help would be appreciated.
Kind regards
Colin.

Hi Colin,
Since u are getting the error when calling an external webservice from XI, this is an error on the webservice provider's box(webserver). You may wnat to contact the administrator of the webserver and ask him to into the error logs. This is a very common issue when using external webservices from XI. Look at the following for more information on HTTP 500 Error
HTTP 500 Internal Server Error:
This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of your Web server site to locate and analyse the logs which should give further information about the error.
This is a 'catch-all' error generated by your Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of your Web server site to locate and analyse these logs.
Hope it helps,
naveen

Error while run OAF, HTTP 500 - Internal server error Internet Explorer

I have installed R12 on my laptop having windows 2003 Server, which running successfully.
In Same machine i have installed Jdeveloper for OAF customization by following 416708.1.
While running test OAF page from Jdev, following error accruing. I have Run autoconfig as well.
There is a problem with the page you are trying to reach and it cannot be displayed.
Please try the following:
Open the r12.oracle.com:8988 home page, and then look for links to the information you want.
Click the Refresh button, or try again later.
Click Search to look for information on the Internet.
You can also see a list of related sites.
HTTP 500 - Internal server error
Internet Explorer

What is the JDev version?
Check if the below fixes the issue.
Go to Tools -> Embedded OC4J Server Preferences-> Global -> Startup. Select the option -> Default Local IP Address.
Thanks
Shree

SOAP Envelope - HTTP_EXCEPTION - HTTP 500 Internal Server Error

Similar Messages

Maybe you are looking for