UNKNOWN/APPLICATION_ERROR in SOAP

HI
my interface is proxy--> XI --> soap. I post the payload from runtime. I am able to sucess full messge in SXMB_moni. but in Adapter Engine it was showing below error.
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
please help me
Thanks
Srini..

Hi Srinivas,
Can you check your BusinessService you have configured and the Receiver communication channel. The reason, it is not identifying the target system, that your target url is pointing in receiver communication channel.
Places that might cause this problem can be.
-> Your Business Service Configuration
-> Receiver Communication Channel, especially check these fields Adapter Engine, Target URL
-> Better check your Receiver Determination, whether you have given appropriate Business Service.
-> Finally your WSDL you got from the service provider, test it outside whether its work fine or not.
Regards,
Prasanna

Similar Messages

Application/UNKNOWN/APPLICATION_ERROR

Hi Experts,
 I am facing the an issue in production. The scenario is FILE -> XI ->SOAP, asynchronous. The message in the integration engine is successful. But I am able to see the error in the SOAP receiver communication channel. Please find below the audit log and kindly help resolve the issue. Thanks.

Message Data
Attribute Value
Status System Error
Repeatable Yes
Cancelable Yes
Error Category XI_J2EE_ADAPTER_SOAP
Error Code GENERAL_ERROR
Audit Log
Success Processing child message of multi-message with message ID ddcf1970-486b-11dc-995c-001a64092f70
Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the receive queue.
Success The message status set to DLNG.
Success Delivering to channel: CC_UpdateOperationProcInfo_SOAP_Receiver
Success MP: entering
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: completed the processing
Success SOAP: continuing to response message bc9d1030-486c-11dc-bd74-001a64092f70
Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Error Exception caught by adapter framework: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
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 Application/UNKNOWN/APPLICATION_ERROR - application fault.
Success The asynchronous message was successfully scheduled to be delivered at Sun Aug 12 08:43:17 SGT 2007.
Success The message status set to WAIT.
Success Retrying to deliver message to the application. Retry: 1
Success The message was successfully retrieved from the receive queue.
Success The message status set to DLNG.
Success Delivering to channel: CC_UpdateOperationProcInfo_SOAP_Receiver
Success MP: entering
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: completed the processing
Success SOAP: continuing to response message 04513be2-486d-11dc-c461-001a64092f70
Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Success SOAP: sending a delivery error ack ...

Hi All,
Today I faced the same issue. My scenario is File->PI->SOAP asynchronous communication.
Initially I did not provide user authentication information in my SOAP receiver communication channel where as the web service was with basic HTTP authentication. So I was getting error 'Application/UNKNOWN/APPLICATION_ERROR'.
Once I provided the user and password information in the receiver communication channel the scenario is working fine.
This is strange to me. If the problem is due to authentication then I would expect to get 'unauthorized' kind of error.
Anyway, hope this will help others who face same issue.
Regards,
Prasad

Application/UNKNOWN/APPLICATION_ERROR - application fault

Hi!
I am creating HTTP-XI-SOAP synchronous scenario and I've got some error in RWB:
SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
How can I fix that problem??
Any sugestions??

Hi ,
Please refer the following thread , This might help you
Application/UNKNOWN/APPLICATION_ERROR
Regards.,
V.Rangarajan

SOAP : response message contains an error Application/UNKNOWN/APPLICATION_E

Hi All,
I am working in a Proxy to SOAP synchronous scenario. Message is processing successfully through IE but i am getting the below error in receiver (SOAP) communication channel.
SOAP : response message contains an error Application/UNKNOWN/APPLICATION_ERROR.
Please suggest what will be possible way out to resolve this issue.
Thanks,
Priya Ranjan

Dear Priya
Have you configured Fault Message for this scenario.
This kind of error is generally thrown by the end target system where the message is not processed succesfully due to some error in there system.
Sourabh

SOAP: response message contains an error Application/UNKNOWN/APPLICATION

Hi,
My scenario is Proxy>Soap>WS. When I tested proxy using SPROXY,the web service call is working fine and I am getting response. However, when I call proxy in the the program, I am getting "SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault" in adapter engine. I have gone through many similar posts in SDN but did not help.
Thanks for your help.

Thanks. I used SOAPUI outside SAP and it works perfectly fine. Even in SAP, it works fine when using Sproxy. Here is the error from adapter engine:
2010-06-24 12:59:34     Success     SOAP: continued from request message 6600174c-8a22-613e-e100-000018280c11
2010-06-24 12:59:34     Error     SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
2010-06-24 12:59:34     Success     SOAP: response message leaving the adapter
2010-06-24 12:59:34     Success     MP: Leaving module processor
2010-06-24 12:59:34     Success     Application attempting to send an XI message asynchronously using connection SOAP_http://sap.com/xi/XI/System.
2010-06-24 12:59:34     Success     Trying to put the message into the send queue.
2010-06-24 12:59:34     Success     The response message for message 6600174c-8a22-613e-e100-000018280c11(INBOUND) was successfully transmitted to the calling application.
2010-06-24 12:59:34     Success     The message status set to DLVD.
2010-06-24 12:59:34     Success     The application sent the message asynchronously using connection SOAP_http://sap.com/xi/XI/System. Returning to application.

SOAP Error: Unknown Application

Hi.
I'm facing a problem while calling a webservice from XI. One the sender side, I have a file and the SOAP is on the receiver side. The web service is deployed on our local EP server and I'm trying to call it from the XI server of our client. We have taken care of all the network connectivity etc,. When I execute the scenario, it is giving an error saying:
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 Application/UNKNOWN/APPLICATION_ERROR - application fault.
But I have no problem calling the same web service from our local XI box.
Could anyone provide me the solution for this.
Thanks in advance.
Regards,
Hari.

Check the soap configuration. Might be calling the web service requires a proxy and an authentication. Generally when you are calling from the local machine, the proxy is automaticlaly detected unless and untill specified. But in most cases, for a SOAP adapter the proxy needs to be specified (unless the network accepts anonymonous connections as XI will be running on admin domain and not on the network user domain).
If that is not the problem then the adapter is not able to resoolve the hostname that you would have provided in the URL. try giving the IP address.
Award if helpful,
Sarath

Syncronous SOAP Receiver Message: APPLICATION_ERROR

Hi Experts,
I am facing a application error in SXMB_MONI for syncronous messages in a SOAP receiver scenario.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In RWB the SOAP adapter shows me that the message was delivery successfully however the guys from the third party application said to me that the message didn't reach it.
I would like to know if you have any idea where the error is.
Have you already faced something like this?
<< Moderator message - Please do not offer points >>
Thanks in advance,
Daniela
Edited by: Rob Burbank on Oct 15, 2010 4:42 PM

Hello,
Based on the exception, this is really not as descriptive as possible. Can you try the following:
1. Execute the WSDL via SOAP UI and let us know of the results.
2. Under SXI_MONITOR, can you double click the response message payload? The response message payload should more or less give an idea as to why this error occurred.
Hope this helps,

WebService no NW DS e utilização no NW PI (RFC to SOAP)

Prezados, bom dia.
Um grande help de vcs ...
Gerei um EJB Stateless bem simples no Developer Studio 2004s. Em seguida criei um WebService (Virtual Interface, WSD e Configuration) a partir do bean criado. Finalmente gerei o EAR e fiz o deploy no Servidor.
Feito isso, o WebService gerado aparece no WebService Navigator e consigo executá-lo perfeitamente.
Agora vem os problemas:
#1 - No WebService Navigator tem uma opção de fazer o download do WSDL. Eu fiz isso e importei no PI (External Definitions). Só que os parâmetros expostos no WS não aparecem na aba Message do PI, com isso, eu não consigo utilizar esse WSDL no Message Mapping, Message Interface, etc. Alguma sugestão de como devo proceder para gerar o WSDL correto ou mesmo o XSD?
#2 - Como não consegui importar o WSDL no PI, gerei o DataType, MessageType, etc na unha, configurei a interface no Integration Configuration, SOAP Adapter, RFC Adapter, Receiver Determination, etc, etc, etc ... Quando executo a RFC, na SXMB_MONI a interface aparece como se tivesse sido executada corretamente, mas no RWB aparece o seguinte erro quando pesquiso pelo canal SOAP configurado: Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
Desde já agradeço toda e qualquer ajuda.
Grande abraço a todos.
Hyalen.

Ola, acho que vc já deve ter conseguido resolver esse problema, mas vamos lá, quanto a interface RFC estar ok no monitor de msgs do PI e com erro no RWB isso ocorre devido ao processo ter transcorrido ok durante toda a msgeria, ou seja, o processo recebeu a msg, fez o mapping transformation, chamou a rfc e finalizou o processo, no RWB porem, que mostra o resultado da chamada desse processo final, retorna o erro que a RFC ou conexao nao foi encontrada, podem ser dois fatores ai, o RFC Destinations (SM59) entre seus ambientes foram criados corretamente e os testes deles estao ok? A RFC realmente existe no ambiente que esta tendo que enviar? O comunication channel esta criado no local correto apontando para o ambiente correto?
Quando ao WSDL, para poder dar uma analisada nele coloque ele aqui no forum por favor, porem vc poderia fazer um testes com o SOAP UI ( aplicativo para testes de webservices ) que é disponivel gratuitamente para verificar se a assinatura do servico esta correta.

File to soap problem

hi i am gettin this problem in file to soap scenario
Error Category XI_J2EE_ADAPTER_ENGINE
Error Code GENERAL_ERROR
SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
plz help me

Hi,
check this
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Regards
Pushkar

Soap Fault mapping issue

Hi,
I have a synchronous scenario of (request) Proxy --> XI --> SOAP and (response) SOAP --> XI --> Proxy. I am having an issue returning the application soap faults back to the sender system. When I enter invalid data while testing this webservice call with a soap client directly without XI I get a soap fault response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Server.generalException</faultcode>
 <faultstring>Login failed</faultstring>
 <detail>
 <LoginFault xmlns="NAMESPACE">
 <exceptionCode>710</exceptionCode>
 <exceptionMessage>Login failed</exceptionMessage>
 </LoginFault>
 <ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">NAMESPACE</ns1:exceptionName>
 </detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
When testing this through XI, the response message after the Soap call is returning the following soap fault in XI payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<LoginFault xmlns="NAMESPACE">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>
Notice just the detail body exists in the payload instead of the soap evelope and body, which I read is stripped off within XI in the case of application errors. I have setup a fault message mapping to tie the wsdl login fault with the standard fault message type and included this in the service interfaces and operations mapping. When the soap fault happens within XI I am getting the following mapping error:
NO_MAPPINGPROGRAM_FOUND: Mapping program is not available in runtime cache:
I am expecting the fault mapping to be executed in this case but doesn't seem to be found. Any ideas why this mapping error is occuring and not being directed to my fault message mapping? Is the mapping expecting the soap envelope and body to be included in the payload?
Any suggestions would be appreciated.
Thanks,
Nate

Here are the errors I am seeing within the sxmb_moni transaction:
Call adapter exception:
<?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>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Response Message Error:
<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="NAMESPACE REMOVED">LoginFault</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and response message payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <LoginFault xmlns="NAMESPACE REMOVED">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>

Abap proxy 2 soap

Hi,
this scenario is abap proxy 2 soap ,, , source system send some data to target webservice and target webservice return approval number.
I checked target url and soap action in receiver soap adapter, and those value is correct.
on sxmb_moni
i got NO_MAPPINGPROGRAM_FOUND
http://test.test.com/pt/ses001/approvalprocess SES001_IM does not exist in runtime cache</SAP:Stack>
and Applicatoin Error
<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
here is Sent message log on MDT.
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
2006-08-29 13:25:37 Success SOAP: response message leaving the adapter
2006-08-29 13:25:37 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-08-29 13:25:37 Success Trying to put the message into the send queue.
2006-08-29 13:25:37 Success The response message for message 44f23177-e6ed-0270-0000-000046028211(INBOUND) was successfully transmitted to the calling application.
2006-08-29 13:25:37 Success The message status set to DLVD.
2006-08-29 13:25:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
here is Receive message log on MDT.
2006-08-29 13:25:37 Success The message was successfully received by the messaging system. Profile: XI URL: http://xi0034:50000/MessagingSystem/receive/AFW/XI
2006-08-29 13:25:37 Success Using connection AFW. Trying to put the message into the request queue.
2006-08-29 13:25:37 Success Message successfully put into the queue.
2006-08-29 13:25:37 Success The message was successfully retrieved from the request queue.
2006-08-29 13:25:37 Success The message status set to DLNG.
2006-08-29 13:25:37 Success Delivering to channel: R_TEST_SOAP_SSS001
2006-08-29 13:25:37 Success SOAP: request message entering the adapter
2006-08-29 13:25:37 Success SOAP: completed the processing
2006-08-29 13:25:37 Success SOAP: response message received 6bc3e4d0-3716-11db-a265-00145e483080
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
i can see source data on sxmb_moni.
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:APPROVALREQ_SES_MT xmlns:nr1="http://test.test.com/pt/ses001/approvalprocess">
<TITLE>46</TITLE>
<GUBUN />
<REQUESTOR>46</REQUESTOR>
<TEXTLINE>SAFSAFSAFDSAF</TEXTLINE>
</nr1:APPROVALREQ_SES_MT>
request message mapping of request
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws">
<args1>46</args1>
<args2>46</args2>
</ns1:ApprovalRequest>
I can not see any return value comming from target webservice on sxmb_moni.
request message mapping error on response
<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
payload of request message mapping of response
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">ibmr52</ns2:hostname>
please check what was my fault.
thanks
venjamin

Hi Bhavesh.
thanks for the note.,,
please look at the bottom of this content.
i can not see "Method=Approval" between jws and args1 even though i set SOAP Action = Approval on Receiver SOAP Adapter.
is this happening something wrong? or is it normal log?
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
here is detail message log on MDT.
--SAP_512dbe91-372d-11db-b291-00145e483080_END
Content-ID: <[email protected]>
Content-Disposition: attachment;filename="[email protected]"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header>
<sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' 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>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId>
<sap:TimeSent>2006-08-29T07:10:08Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party>
<sap:Service>BS_SAPR3_SSS0017</sap:Service></sap:Sender><sap:Receiver>
<sap:Party agency='' scheme=''></sap:Party><sap:Service>BS_MMM_D</sap:Service></sap:Receiver>
<sap:Interface namespace='http://sds.samsung.co.kr/pt/sessingle001/approvalprocess'>APPROVALREQ_MMM_IB</sap:Interface>
</sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging>
<sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:Hop timeStamp='2006-08-29T07:10:08Z' wasRead='false'><sap:Engine type='BS'>BS_SAPR3_SSS0017</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop>
<sap:Hop timeStamp='2006-08-29T07:09:06Z' wasRead='false'>
<sap:Engine type='IS'>is.00.xi0034</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-29T07:09:08Z' wasRead='false'>
<sap:Engine type='AE'>af.sxd.xi0034</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</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'/></SOAP:Body></SOAP:Envelope>
--SAP_512dbe91-372d-11db-b291-00145e483080_END
content-id: [email protected]
content-type: application/xml
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
thanks
venjamin
Message was edited by: venjamin

Catch soap faults

I have the following scenario: SAP ABAP proxy --> XI --> IIS web service. The IIS web service is not in my hand.
At some request the server has internal server errors. In that case we get SOAP faults from the web service. Now we have the situation that such SOAP faults causes XI mapping errors. But this is not good. I would like to transfer such faults as application faults to the calling ABAP proxy. But I don't know how I can catch these SOAP faults.
Here is the situation in detail.
The response from the IIS web service:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <soap:Body>
 <soap:Fault>
 <faultcode>soap:Server</faultcode>
 <faultstring>error description </faultstring>
 <faultactor>ws user account</faultactor>
 <detail>
 <ServerExceptions>bla bla bla</ServerExceptions>
 </detail>
 </soap:Fault>
 </soap:Body>
</soap:Envelope>
In XI monitoring I have 3 entries: my call and two error messages.
First error message payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<ServerExceptions>blab la bla</ServerExceptions>
Error information:
<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="">ServerExceptions</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The second error message has the same payload but a different error part:
<?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>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>"my mapping program"</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Das Interface-Mapping "my mapping program" ist nicht im Laufzeit-Cache vorhanden.</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Is there any opportunity to catch such SOAP faults or server errors? I would like to map them in the xi fault structure. So the calling ABAP proxy gets the error message. Now I get a XI error and always a mail because I use the alert framework. But this is no XI error and I don't want to get such error messages.

Hi Smitha.
Yes. I have a WSDL from the external web service but the WSDL doesn't contain any fault definition. But I know the fault structure because I catch such an exception with XML Spy SOAP Proxy. The Exception looks like in my first post.
The problem is that I don't get this exception in my hands. When I use the Message Display Tool of the Runtime Workbench I can only see the <ServerExceptions> node of the exception in my payload. So I only can deal with this. So I have specified a xsd for this.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
 <xs:element name="ServerExceptions">
 <xs:simpleType>
 <xs:restriction base="xs:string" />
 </xs:simpleType>
 </xs:element>
</xs:schema>
I load this as external definition and add this to my interface as fault type. After that I'm able to catch the exception and I get the content of this node and map this to the fault message of my outbound interface. Unfortunately the content of this node is useless. I need the values of the other nodes.
O course I tried your proposal and add the complete fault type definition to the given wsdl and after that I re-import this new wsdl. But that doesn't change the behaviour described above.
The key point is that I don't get the whole exception.

SOAP fault message : java.lang.NullPointerException

Hi,
After calling the Webservice from XI, got error message as
java.lang.NullPointerException
What might be the problem.
Thanks in Advance!
Regards,
Sreenivas.

Hi,
In RWB, am getting SOAP resopnse error
and in SXMB_MONI, getting inbound message as
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <INVALID_INPUT>
<description>java.lang.NullPointerException</description>
</INVALID_INPUT>
<?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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="">INVALID_INPUT</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,
Sreenivas.

ApplicationResponseFault with namespace longer than 60 in sync soap message

Hi,
we are on pi 7.0 and our scenario is a async-sync bpm. In the sync soap message, the webservice raise an application error. In the response soap message we get the following detail tag:
<detail><ApplicationResponseFault xmlns="http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10"><DocumentResponse xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"><Response><ResponseCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">BusinessReject</ResponseCode></Response></DocumentResponse></ApplicationResponseFault></detail>
In sxi_monitor this application error isn't caught and a system error is generated.
In the system error message we get:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4271) at com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:572) at com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
In defaulttrace.trc we get ","<sap:ApplicationFaultMessageNamespace> is longer than 60 characters: http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10",":
"09/04/2009","10:22:43:421","unable to generate the header map","Error","","com.sap.aii.adapter.xi.ms.XIMessage.getHeaderMap()","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2300000A6C000472BC344957CC","com.sap.aii.adapter.xi.ms.XIMessage","","","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","0","","","0","com.sap.aii.adapter.xi.ms.XIMessage","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",
"09/04/2009","10:22:43:421","<sap:ApplicationFaultMessageNamespace> is longer than 60 characters: http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10","Error","","com.sap.aii.messaging.mo.xmb.XMBErrorHeader.marshal(XMLWriter)","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2200000A6C000472BC34495771","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10,","http://schemas.datacontract.org/2004/07/BizLayerNT.ServiceLayer.v10,","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","1","","","0","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",
"09/04/2009","10:22:43:421","Could not process message from 192.168.130.21 due to java.lang.NullPointerException.","Error","","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(HttpServletRequest, HttpServletResponse)","sap.com/com.sap.aii.af.ms.app","SAPEngine_Application_Thread[impl:3]_55","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE0083000072F700000A6C000472BC344955F3","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet","192.168.130.21,java.lang.NullPointerException,","192.168.130.21,java.lang.NullPointerException,","SAPDES_TPI_34103150","1d72b100992c11dec67f001a64317eee","PIISUSER","0","0","","1","","","15337","com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet","SAPEngine_Application_Thread[impl:3]_55","","PIISUSER",
"09/04/2009","10:22:43:421","The SAP XI Adapter Framework Messaging Service caught an exception during rendering an XML Message. Details can be found in the trace file for Location com.sap.aii.messaging.mo.xmb. Action: Please contact SAP Support and provide the trace file.","Error","/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK","com.sap.aii.messaging.mo.xmb.XMBErrorHeader.marshal(XMLWriter)","sap.com/com.sap.aii.af.app","SAPEngine_Application_Thread[impl:3]_14","34103150:F:\usr\sap\TPI\DVEBMGS03\j2ee\cluster\server0\log\defaultTrace.trc","001A64317EEE005E00005F2000000A6C000472BC3449559F","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","","","n/a","b82f88e0992b11dea4d8001a64317eee","","0","0","","0","/Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK","","0","com.sap.aii.messaging.mo.xmb.XMBErrorHeader","SAPEngine_Application_Thread[impl:3]_14","","J2EE_GUEST",
So I think the problem is due to the namespace length. I'm right?
We can't change the consumed webservice to reduce namespace length and our customer ask us to solve it in PI. Is there any way to change the namespace before to be treated and get a correct application error?
Thanks in advance,
Marc
Edited by: Marc Mauri on Sep 5, 2009 12:06 PM

Hi Neetesh,
we developed our own adapter module. We use it in our receiver soap adapter, module tab, before and after the standard module sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean.
In this audit log secuence you can see that the problem seems not to be solved, because the error is triggered when processing response message inside adapter module sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean, so our module is not called and the problem remains.
2009-09-22 19:06:41 Success Message successfully received by messaging system. Profile: XI URL: http://sapdes:50300/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2009-09-22 19:06:41 Success The message status set to DLNG.
2009-09-22 19:06:41 Success Delivering to channel: CC_WS_DOS
2009-09-22 19:06:41 Success MP: Entering module processor
2009-09-22 19:06:41 Success MP: Processing local module *localejbs/AM_OWN_MODULE*
2009-09-22 19:06:41 Success GetHostName: Module called
2009-09-22 19:06:41 Warning Inside my own adapter Module <-- THIS IS A TRACE MESSAGE CODED INSIDE OUR MODULE
2009-09-22 19:06:41 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2009-09-22 19:06:41 Success SOAP: request message entering the adapter with user J2EE_GUEST
2009-09-22 19:06:41 Success SOAP: Web Services Security processing...
2009-09-22 19:06:41 Success SOAP: apply Web Services Security...
2009-09-22 19:06:41 Success SOAP: Web Services Security applied.
2009-09-22 19:06:42 Success SOAP: completed the processing
2009-09-22 19:06:42 Success SOAP: continuing to response message 4d2c88e0-a79a-11de-9ffa-001a64317eee
2009-09-22 19:06:42 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault <----
THIS ERROR IS DUE TO NAMESPACE LENGHT (WE CAN SEE THIS ERROR IN DEFAULT_TRACE.LOG)
2009-09-22 19:06:42 Success MP: Processing local module localejbs/AM_OWN_MODULE
2009-09-22 19:06:42 Success MP: Leaving module processor
2009-09-22 19:06:43 Success The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System. 2009-09-22 19:06:43 Success The message status set to DLVD.
Any suggestion?
Thanks in advance,

SOAP Adapter + asynchronous message + Runtime Workbench

Hi
I have problem with error monitoring in Runtime Workbench -> Message Monitoring
I have SOAP adapter deployed on Apache Axis.
I have flow SOAP->XI->SOAP (asynchronous mode)
It works great until receiver adapter generate error.
I can see error message in defaultTrace log but in
Message Monitoring-> Details I see only "SOAP: response message
contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault".
SOAP message from receiver adapter (with error) looks like that
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
 <soapenv:Fault>
 <faultcode>Client</faultcode>
 <faultstring>Internal Server Error</faultstring>
 <detail>
 <myfaultmessage>
 <type>RABAX_STATE</type>
 <message>Divide by 0 (type 1).</message>
 </myfaultmessage>
 <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">pslupkowski</ns1:hostname>
 </detail>
 </soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
I'm think that this message is not well formated and
Adapter Engine can't find some tags during parsing this
message. Any ideas how to solve this problem?
I'm just want to see error description from <myfaultmessage> tag in Message Monitoring

Hi,
Did you check the log on adapter engine?
http://<host>:<port>/MessagingSystem/monitor/monitor.jsp
Take a look to this monitor, here you can see both messages (request and response).
Cheers,
Ricardo.

UNKNOWN/APPLICATION_ERROR in SOAP

Similar Messages

Maybe you are looking for