ADAPTER.SOAP_EXCEPTION : soap fault: No such operation

Hi Experts,
I have done File to Webservice scenario. When I am trying to execute the scenario I am getting the following 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>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: No such operation 'InventoryRequest'</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
My receiver SOAP adapter is showing inactive in communication channel monitoring. But I check one of the forum people are saying it is showing like that only until we execute the scenario. Is it correct.
I have checked the webservice for "InventoryRequest" soapAction but in my webservice all soapActions are just empty.As follows
<operation name="InventoryStatus">
<wsdlsoap:operation soapAction="" />
<input name="InventoryRequest">
Is it problem with weservice or my configuration. Please suggest me
Regards
Sowmya

Hi
In configurator if I check the "Do Not Use Soap Envelope" I am gettin "Internal Error 500"
If i dont check that check box I am getting the following error
soap fault: No such operation 'InventoryRequest'
But I didn't specify anything in soapAction.
Could you please tell me how to resolve this issue
I have chec the url from browser it is wroking..
Thanks & Regards
Sowmya

Similar Messages

XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation

Hi,
I am doing a SOAP - PI - SOAP scenario.
When I tested my scenario, I am getting this error in wsnavigator:
Web service returned error. Fault code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" Fault String: "Server Error".
When I checked in SXMB_MONI, I get this error in the response message:
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation</SAP:AdditionalText>
I searched thru the forums but I am not finding this similar issue.
"no such operation" issues posted here usually have an operation name after.
I would appreciate your help.
Thanks,
mae

HI
WSDL is having some problem
When you imported this wsdl how many messages does it show. Check weather it is having SETCOMPANYFIELDVALUE request and response. you can check the messages carried in a wsdl using the messages tab in external definition.
Thanks

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault

Hi Experts,
I am trying to create a scenario SOAP to SOAP through AAE. There is no mapping involved.
Sender is a 3rd Party application and receiver is SAP BusinessObjects [BI].
Following error is coming when posting the message from SOAPUI or through integration engine.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: String index out of range: 0
I have done following workaround.
1) I tried the message flow through AAE, but same error in the channel
2) I checked creating a one to one mapping with soap fault message. Still the same error.
3) "XMBWS.NoSOAPIgnoreStatusCode = true" in module tab -> Module configuration
When I tried this mentioned option, the message is passing through the channel but the passing blank empty payload.
I have checked following links.
http://forums.sdn.sap.com/thread.jspa?threadID=156305
http://forums.sdn.sap.com/thread.jspa?threadID=2111959
http://forums.sdn.sap.com/thread.jspa?threadID=1675917&tstart=0
Any pointers on this subject will be very much helpful
Thanks
Ray..

Hello,
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: String index out of range: 0
When I tried this mentioned option, the message is passing through the channel but the passing blank empty payload.
Probably because the return is blank. If this is expected, can you just use Java Mapping to parse the blank response?
Hope this helps,
Mark

C4C Integration issue XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault

Hi All,
Scenario: ECC to C4C
I am getting below error while pushing message to C4C using SOAP channel with Http Protocol.
SOAP channel has been configured with SSL Authentication.
Regards,
Mani

Hi Manikandan,
Use TCPGW tool to see the response from C4C, it is very useful for trouble shooting this kind of errors.
Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
Regards,
Praveen.

Receiver SOAP Adapter Problem-soap fault: Server did not recognize the valu

I have a scenario for service orders using async call : IDOC-XI-SOAP.
I used the XML Spy tool to test the Service order's web services and it works fine. I imported the same WSDL file in XI. When I send a SOAP message from XI, I get a following error in the adapter engine.
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: AddUpdateCostObjectLevel1.
Can someone please help me...
Thanks in advance!
Mrudula

This problem is resolved by me by passing the "http://company's URL/AddUpdateCostObjectLevel1" in the SOAP action.
Thanks to all for your input.
Mrudula

Error "soap fault: No operation available for request" in proxy to soap Scenario

Hi Experts,
Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
Thank you very much if any one provided the solution
Regards,
Yugandhar

Hi Yugandhar,
Check the below thread,
Connecting from SAP PI To Salesforce
Regards
RK N.

Mapping SOAP Fault during synchronous SOAP call

We are building a mediated service scenario where PI is brokering a synchronous SOAP call, without changing any of the information being sent or received (the mappings use the same source and target data types with no transformations). When the service is successfully executed everything works as expected, but when the target service returns a SOAP fault, PI appears to be wrapping the fault in a separate fault before returning it to the client. Why is this happening? Is there a way to simply return the SOAP fault to the client without adding the additional wrapper?
Here is the fault received from the target service when called directly:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Header/>
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>Missing_Required_Data</faultcode>
 <faultstring>**Required data is invalid : Dealer Country**</faultstring>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
Here is the fault received from the mediated PI service call:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text>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/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: **Required data is invalid : Dealer Country**
 at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)
 at sun.reflect.GeneratedMethodAccessor948.invoke(Unknown Source)
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
Why aren't they the same?

are diferents coz the first is a fault message and the second is a exception message.
to send back the fault message define a fault message for both structure and map them in a new message mapping. later in the operation mapping or interface mapping (depends of the pi version) under fault message or fault mappinng (i dont remember) tab assisg the fault message mapping.
thats all you need.

Handling Soap Fault Response.

Hi All,
I have a Proxy to SOAP scenario.
While testing from SoapUI --
I am getting response for the valid input and for the invalid input the response is below.
In the scenario through SAP PI , the valid input given from the HTTP client is getting a valid response and the scenario is running fine.
But while checking the negative test, giving the invalid input, it is ending in a System error in PI.
We have to handle this and send the error back to the source system.
FAULT RESPONSE IN SoapUI :
<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:Client</faultcode>
 <faultstring>System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (6, 45). ---> System.InvalidOperationException: Instance validation error: 'AD' is not a valid value for Currency.
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
 at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 --- End of inner exception stack trace ---
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 --- End of inner exception stack trace ---
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring>
 <detail/>
 </soap:Fault>
 </soap:Body>
</soap:Envelope>
*System error message in SAP PI* :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (1, 328). ---> System.InvalidOperationException: Instance validation error: 'US' is not a valid value for Currency.
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read1_Currency(String s)
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read2_ConversionRate()
 at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer.Deserialize(XmlSerializationReader reader)
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 --- End of inner exception stack trace ---
 at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 --- End of inner exception stack trace ---
 at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
 at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</SAP:AdditionalText><SAP:Stack/><SAP:Retry>M</SAP:Retry></SAP:Error>
I want to capture the text in Fault string in the Fault response and send it back to the Source system.
I have referred many blogs but i am unable to do it.
Will java mapping work as this is a response from the Target Webservice and NOT an errorin PI.

Hello.
If your scenario is ECC -> Proxy -> PI -> SOAP -> WS -> SOAP -> PI -> Proxy -> ECC.
In ESR create a Fault Message Type, and added to your Service Interface (Outboun/Inbound), use a XSLT mapping to take anyway format response, rebuid your proxy ABAP and see your "message fault" on exception tab.
this works for me.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:template match="/">
 <ns0:FMT_ResponseAuth>
 <standard>
 <faultText>
 <xsl:value-of select="//detail"/>
 </faultText>
 </standard>
 </ns0:FMT_ResponseAuth>
 </xsl:template>
I hope this help you.
Edited by: KrlosRios on Nov 2, 2011 5:59 PM

How to catch a SOAP fault

Hi All,
I have a ISU to web service, PROXY to SOAP sync interface. I am getting following as response.
How can I get this into Fault message mapping?
I have followed these blogs:
Fault Message Types - A Demo (Part 1)
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Validation constraint violation: data type mismatch in element 'extraOverhead'</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Aravind

Hi,
Can you please elaborate exactly what you are trying to achieve.....are you trying to display this error message to the user of client proxy...If so, You can catch the exceptions in client proxy using the two standard exception classes.
CATCH cx_ai_system_fault .
CATCH cx_ai_application_fault .
and in the catch block you can receive the error message and display it. The code will look like this
DATA : sys_fault TYPE REF TO cx_ai_system_fault,
 text TYPE string.
CREATE OBJECT sys_fault.
CALL METHOD sys_fault->get_text
 RECEIVING
 result = text.
WRITE : /10 'System Fault ', 30 text.
Regards,
Priyanka

Error message : soap fault: java.lang.NumberFormatException

Hello,
I have Idoc to SOAP scenario. We I send Idoc, I get following error,
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.NumberFormatException Message being parsed:
To be on safer side, I have populated all the fields with values. I have tested the same scenarion using SOAP UI tool with payload from XI & it works fine.
This is very annoying. Can anybody help?
Regards,
Sunil

Prateek,
Here is my xml which goes to web service via SOAp adopter,
   470 {/ns0:company_code}
   Constant {/ns0:userid}
   Constant {/ns0:password}
   1 {/ns0:acklm}
   20090821 {/ns0:badat}
   1020104878 {/ns0:banfn}
   A {/ns0:banst}
   NB {/ns0:bsart}
   20090821 {/ns0:erdat}
   Constant {/ns0:temp1}
   Constant {/ns0:temp2}
   Constant {/ns0:temp3}
   Sunil.Joyous com {/ns0:email}
   146474 {/ns0:ernam}
   Sunil Joyous {/ns0:name}
   {/ns0:zossatb}
   TEST OSAT {/ns0:afnam}
   1 {/ns0:anln1}
   1 {/ns0:anln2}
   1 {/ns0:aufnr}
   1020104878 {/ns0:banfn}
   1 {/ns0:bednr}
   00010 {/ns0:bnfpo}
   NB {/ns0:bsart}
   1.000 {/ns0:bsmng}
   1.000 {/ns0:bumng}
   1 {/ns0:catalog_info}
   1 {/ns0:ebakz}
   T02 {/ns0:ekgrp}
   IZ {/ns0:ekorg}
   IZ {/ns0:gsber}
   5300642603 {/ns0:infnr}
   1 {/ns0:knttp}
   1 {/ns0:kostl}
   20090812 {/ns0:lfdat}
   1 {/ns0:lifnr}
   X {/ns0:loekz}
   BOX CARDBOARD TELESCOPIC PART {/ns0:maktx}
   00441010 {/ns0:matkl}
   000000000002647430 {/ns0:matnr}
   ST {/ns0:meins}
   10.000 {/ns0:menge}
   1 {/ns0:mfrpn}
   1 {/ns0:peinh}
   10.000 {/ns0:preis}
   0 {/ns0:pstyp}
   X {/ns0:repos}
   1 {/ns0:saknr}
   1 {/ns0:statu}
   470 {/ns0:temp1}
   PACKING {/ns0:temp2}
   20090821 {/ns0:temp3}
   BOX CARDBOARD TELESCOPIC PART {/ns0:txt01}
   TRY {/ns0:waers}
   1 {/ns0:wempf}
   X {/ns0:wepos}
   IZ {/ns0:werks}
   1 {/ns0:zdegsta}
   TEST TEST {/ns0:zsastxt}
   F442617301 ,4085212101 ,JL/QSC-70108949 ,OUT ,7064 58 049 , , , , , , , , , , {/ns0:ztanim}
   {/ns0:zossatd}
   1020104878 {/ns0:banfn}
   00010 {/ns0:bnfpo}
   NB {/ns0:bsart}
   470 {/ns0:temp1}
   Constant {/ns0:temp2}
   Constant {/ns0:temp3}
   PO TEXT {/ns0:zmetin1}
   1 {/ns0:zmetin10}
   1 {/ns0:zmetin2}
   1 {/ns0:zmetin3}
   1 {/ns0:zmetin4}
   1 {/ns0:zmetin5}
   Constant {/ns0:zmetin6}
   Constant {/ns0:zmetin7}
   Constant {/ns0:zmetin8}
   Constant {/ns0:zmetin9}
   {/ns0:zossatt}
Out of these following fields are of decimal type,
BSMNG, BUMNG, MENGE, PEINH, PREIS
Rest all are of string type.
Edited by: Sunil Joyous on Aug 21, 2009 2:01 PM
Edited by: Sunil Joyous on Aug 21, 2009 2:02 PM
Edited by: Sunil Joyous on Aug 21, 2009 2:02 PM

Receiver soap : Error ADAPTER.SOAP_EXCEPTION

Hi all,
My Scenario is IDOC -> XI -> WEBSERVICE using BPM & SOAP adaptor.
when i send idoc from R/3 it is going Xi
From Xi to web service using WSDL Request message .it is not reach to web service(connection is ok but wsdl request massage is not going properly) .
sxmb-moni :error is
<?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="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
<SAP:AdditionalText>soap fault: com.sap.webservice.SchemeTopupDeliveryService</SAP:AdditionalText> : this service is not related to my service (It is showing wrong service name)
Pleas tell me where error is happened

this service is not related to my service (It is showing wrong service name)
This is the reason, you somehow call the wrong web service. But are you talking about BI or XI here?
Best regards
Dirk

Soap Receiver Getting "no such operation"

I am trying to access a web service. The operation is importCargo and the data is a string <xml></xml>.
I imported the WSDL...which is working fine in WSNavigator...and used the External Definition for my Message Map. The message map does create a string <xml>stringcontents</xml>.
In the Receiver Communications Channel I specified the url of the web service, checked "Use Query String" and entered importCargo as the Soap Action.
When I call the web service I get an error "soap fault: javax.xml.rpc.JAXRPCException: No such operation 'xml'"
When I look at the soap envelope I see that all that is being sent is the <xml> string there is no importCargo wrapper...at least not that I can see in the trace file.
How can I fix this so that importCargo is sent as the operation rather than xml?

johann,
One WSDL can have multiple actions/functions/services in it. So, where are you specifying which action/function in that WSDL you are calling?
--Archana

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

BPEL Database Adapter "Faulted while invoking operation.." --where to look?

Hi,
I hope that someone can assist me. Occassionally in production a database adapter step will fault. On the BPEL Console flow diagram for the step I can see "Faulted while invoking operation XXXXX on provider YYYYY". The step retries, but the fault never appears to resolve.
The database being accessed is available and I am able to perform the same query manually. Only a reboot appears to solve the problem.
Where do I look to see the cause of this fault? I have looked in the following log but cannot see anything either related to the adapter, flow or flow id. Should I look anywhere else?
Thanks - Anit

Hi,
Below is what the database adapt step shows in the flow diagram. The flow contains several other database adapter accesses prior to this, to the same database, and these completed correctly. I will look in the log file you suggested.
Faulted while invoking operation "DB_ID_PETICION_MNP" on provider "DB_ID_PETICION_MNP".
<messages>
<input>
<Invoke_Obtener_ID_PETICION_MNP_DB_ID_PETICION_MNP_InputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="DB_ID_PETICION_MNPInput_msg">
<DB_ID_PETICION_MNPInput xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/DB_ID_PETICION_MNP">
<id_pedido_crm>13485201</id_pedido_crm>
</DB_ID_PETICION_MNPInput>
</part>
</Invoke_Obtener_ID_PETICION_MNP_DB_ID_PETICION_MNP_InputVariable>
</input>
<fault>
<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="summary">
<summary>null</summary>
</part>
</bindingFault>
</fault>
</messages>
[FAULT RECOVERY] Schedule retry #1 at "Oct 23, 2009 11:28:39 AM".
...same as before. This repeated 4 times.
Finally rebooted the server, and the adapter completed OK:
<messages>
<Invoke_Obtener_ID_PETICION_MNP_DB_ID_PETICION_MNP_InputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="DB_ID_PETICION_MNPInput_msg">
<DB_ID_PETICION_MNPInput xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/DB_ID_PETICION_MNP">
<id_pedido_crm>13485201</id_pedido_crm>
</DB_ID_PETICION_MNPInput>
</part>
</Invoke_Obtener_ID_PETICION_MNP_DB_ID_PETICION_MNP_InputVariable>
<Invoke_Obtener_ID_PETICION_MNP_DB_ID_PETICION_MNP_OutputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="response-headers">[]</part>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="DB_ID_PETICION_MNPOutputCollection">
<DB_ID_PETICION_MNPOutputCollection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/DB_ID_PETICION_MNP">
<DB_ID_PETICION_MNPOutput>
<ID_PETICION_MNP>13485201-37491</ID_PETICION_MNP>
</DB_ID_PETICION_MNPOutput>
</DB_ID_PETICION_MNPOutputCollection>
</part>
</Invoke_Obtener_ID_PETICION_MNP_DB_ID_PETICION_MNP_OutputVariable>
</messages>
Thanks - Anit

ADAPTER.SOAP_EXCEPTION : soap fault: No such operation

Similar Messages

Maybe you are looking for