Problem with SOAP FAULT messages

Hi,
I'm developing the flash interface for a .NET application.
The client side (flash) communicate with server side (.NET) by web
services. The problem is that when the server side send a Fault
message flash breaks telling "Unable to connect to
endpoint........". In this case I need to know the error message
send by the server but the fault.faultstring is undefined.
Here the server Fault message:
HTTP/1.1 500 Internal Server Error.
Date: Wed, 23 Aug 2006 09:07:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Content-Length: 419
<?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>SoapHeader</faultcode>
<faultstring>The userid: xxxx is
invalid</faultstring>
<detail />
</soap:Fault>
</soap:Body>
</soap:Envelope>
And this the code that handle the fault case:
pendingcall.onFault = function (fault:Object){
rootObj.gbl_logger.log("WS Fault: "+ fault.faultstring ,
10);
As you can see the real faultstring is "The userid: xxxx is
invalid" but in the faultstring property of the fault object I
found "undefined".
I've read many posts that report that the problem can be
solved in the server side modifing the HTTP HEADER from 500 to 200.
Unfortunately I can't access the server side code. Exists a way to
resolve the problem in the client side? Seems it is a Flash bug as
the SOAP 1.1 specs tells that all SOAP Fault messages must carry a
HTTP 500 header. Exists some patch that solve the problem?
Thanks.

Hi ,
Thanks for joining the Community.
Please get in touch so we can resolve this issue for you.
Click here for contact details.
Thanks
James

Similar Messages

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

ABAP Web Services Exception Valorization in SOAP Fault Message

Hi,
I created a Custom Function Module in ABAP with a custom exception ( "Exception1) in exception list (including a short text description of the exception ("This is the first exception!!!")).
I exposed it as web services by means of 'Web service ABAP creation wizard".
I hard coded the raising of the exception in order to see the valorization of SOAP Fault Message.
The problem is that the field "Text" in SOAP fault message is empty instead of "This is the first exception!!!".
Can you help me?
Thanks in advance
Giuseppe
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
 <soap-env:Body>
 <soap-env:Fault>
 <faultcode>soap-env:Client</faultcode>
 <faultstring xml:lang="it">Exception1</faultstring>
 <detail>
 <n0:Zprova.Exception xmlns:n0="urn:sap-com:document:sap:soap:functions:mc-style">
 <Name>Exception1</Name>
 <Text/>
 </n0:Zprova.Exception>
 </detail>
 </soap-env:Fault>
 </soap-env:Body>
</soap-env:Envelope>

Hi,
in case you want some specific text,you can raise the exception like this in your function module.
MESSAGE I001(ZPLATINO) RAISING EXCEPT1.
message class: ZPLATINO
exception : EXCEPT1
message no 001,
message text : CHECK ERROR PUSHKAR1
and your response will be like.:
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
 <soap-env:Body>
 <soap-env:Fault>
 <faultcode>soap-env:Client</faultcode>
 <faultstring xml:lang="en">EXCEPT1</faultstring>
 <detail>
 <n0:Zpl.Exception xmlns:n0="urn:sap-com:document:sap:soap:functions:mc-style">
 <Name>EXCEPT1</Name>
 <Text>CHECK ERROR PUSHKAR1</Text>
 <Message>
 <ID>ZPLATINO</ID>
 <Number>001</Number>
 </Message>
 </n0:Zpl.Exception>
 </detail>
 </soap-env:Fault>
 </soap-env:Body>
</soap-env:Envelope>
I think this solves your problem.
points..points..:)
Message was edited by:
 pushkar anand

Handling SOAP Fault messages in BPM

Hi,
My scenario is Sync-Async Bridge involving File to SOAP transformation. I have used BPM as 1 file has many records and each record is required to call the web service synchronously.
In the BPM I have
Receive ---> Transform (1:n multimapping ) -
> Block (Par for Each)
In Block I have Send Sync step to call Web service . I have an exception branch for the send step for catching Fault message that is sent back from webservice for Application Fault.
Problem:
Though the Fault message is sent from web service ,in the BPM the block goes in error saying : "No exception defined for fault message ". The Exception brach is not executed.
Please suggest if anyone has come across such a scenario and solution to this.

hi satesh
using "exception handler" in BPM we can handle the error messages
regards
kummari

How to send back the soap fault message without details tag to the sender

Hello Expert,
Is it possible to send the soap fault message(fault String element value) without details tag as shown below to the sender in synchrounous scenario.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Client</faultcode>
 <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.arrayOtrosTributos.otroTributo(1).codigo - El Código de Tributo es obligatorio.</faultstring>
 <detail></detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
I have to send the faultstring element value in one of the element in response message back to sender? Is it possible using BPM?The above fault response does not have a fault payload (no detail element) and would result in a system error message.So how to handle this?
If yes .Please tell me the BPM design
faultstring value will be dynamic.
Thanks in advance

Thanks Yzanagi,
I have gone through the index.htm file.
In my scenario that is RFC -PI-soap(using http(Axis) protocol).when the webservice provider is sending the soap fault as.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Client</faultcode>
 <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1</faultstring>
 <detail></detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
In PI sxmb_moni it is converting to the error (system not application error)as shown below when using receiver soap adapter with https(Axis) transport protocol and Message protocol:Axis.
<?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:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1.</SAP:AdditionalText>
<SAP:Stack></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
As my requirement was (I have mentioned in my first question) that I want to pass
SAP:AdditionalText tag
value back to sender in one of the elements of response message payload or handle using fault message mapping if this error could be converted to application error and map to the RFC exception but unfortunately which is not possible even using AXIS adapter.
so other option to inform the sender RFC is mentioned here http://help.sap.com/saphelp_nw70/helpdata/en/22/0425e0488911d189490000e829fbbd/content.htm
but while handling the SYSTEM_FAILURE exception from PI at sender in report program and displaying the msg variable ,I am not getting complete error message..It is getting truncated.Is there a limit to the no of character the msg variable contains which is set by system.Even if we declare msg variable with more length(for example char length 500) it is just displaying part of the error message from PI.
Any Idea to read complete system error message from PI in report program at RFC sender..
Kind Regards,
Kubra fatima

Another problem with SOAP sender

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

Interface-Mapping with a Fault Message Type

Hi,
we have an abap-proxy and some messages generated errors. The errors can be displayed via sxmb_moni. The proxy raises an "Application Error (Restart possible)".
Now I wanna transform the generated fault message (of the proxy) with a message mapping and send the output to a file.
My problem is, that it is not possible to define an interface mapping with the fault message as well as it is not possible to define a receiver determination.
Any ideas?
Thanks a lot
Regards
Wolfgang Hummel

Hello
As far as I know you can propogate the application error back to the calling application only in case of a Synch Interface? Are you making a Synch call where the proxy triggers a fault message, if yes then all you need to do is to make the change in XI to have the fault message for both the outbound and inbound message interfaces and then a corresponding fault message mapping and select this in the Interface Mapping and then the fault message will be sent to the source / calling application.
In the case of Asynch calls I don't think this is possible until you use a BPM. Have not tried this myself though.
Regards,
Bhavesh

Problems with importing text messages from PC Suit...

Problems with importing text messages from PC Suit 7.1.18.0 to my Nokia 5800
I am trying to import a csv file that contains text messages (Note that this file was created using PC Suit 7.1.18.0) to a subfolder that I have created to My Folders but PC Suits only imports the text messages to the Draft folder. Note that initially it shows that the messages are import in the correct folder but after a refresh it shows them in the Draft Folder. Is their any setting that I should change in the PC Suit or the phone? My computer runs on Windows XP Service Pack 3 and the Nokia 5800 was upgraded to the latest firmware v20.0.012
Thanks for your help

Most phones only allows importing of draft and archived box for SMS.
To do a restoring, you need to backup the SMS as a .nbu file using PC Suite and restore later.
If you got an SD card, you can also do a backup on the SD Card (backup.arc) then restore later (reset and restore: backup.arc and mmc).
What's the law of the jungle?

BPM: System_Error" SOAP fault message received

Hi,
We upgraded SAP system from 4.7 to ERP2004 on 09/17/05.
We have XI-3.0 version from last 9 months and this BPM was working good so far. We have not changed anything in it except we upgraded the SAP system.
We are using ABAP proxy from SAP to send "userid"
message to XI-BPM and then it would make a Synchonous call to SAP system to get roles of those "usrid".
In the first step when it is sending data to XI an exception is raised and in the second step when it tries to make synchronous call to SAP we are getting error:
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="System_Error">SOAP fault message received</Trac
<Trace level="3" type="System_Error">SOAP fault code: Client</Trace>
<Trace level="3" type="System_Error">SOAP fault string: Error during c
I noticed that the XML name tag looks different now
Before upgrade when message was successful.
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:MT_ECA_USRID xmlns:ns1="http://bcm.edu/common"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<USRID>CLARKSON</USRID>
<USRID>2_MA140016</USRID>
</ns1:MT_ECA_USRID>
After upgrade when message is failed
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:MT_ECA_USRID xmlns:nr1="http://bcm.edu/common">
<USRID>AABULIMI</USRID>
<USRID>AB147899</USRID>
<USRID>ACHALL</USRID>
</nr1:MT_ECA_USRID>
You would notice that
" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
missing after upgrade.
I would appreciate if anyone could help me.
Mrudula

Hi,
Can you paste the full error message. Also take a look at the default trace log in Visual Admin. Set the logging for soap to debug.
Naveen

Handling SOAP Fault Message in BPM

Hello XI SDN'ers,
I am getting SOAP Fault Message in my SOAP Scenario and I am not aware of Handling that error in my BPM. Could any one tell me, How to handle such error's in BPM?
Thanks & Regards,
Satish.

hi satesh
using "exception handler" in BPM we can handle the error messages
regards
kummari

A sample web service to return SOAP fault message for application error

Hi,
I need to test behavior of XI, in case of application error (using <detail> tag in soap:fault) from web service in nosoap mode.
If any one is aware of a free web service, which can raise application soap fault message, Kindly provide the details.
Thanks in Advance,
Rahul..

Hi,
What is the URL to which you are posting the SOAP message?
Is it?
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>
If yes, then like mentioned the QOS is picked from the Sender SOAP adapter.
But, if the URL is ,
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Then you need to give the QOS as ,&QualityOfService=ExactlyOnce appended to the above URL.
More, /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh

Having problem with purchases. Message is saying my billing info is incorrect

Having problem with purchases. Message is saying my billing info is incorrect

Make sure your payment information on your iTunes account matches with your bank's. If it's correct and you still cannot purchase, you'll need to contact support and have them check your account.
http://www.apple.com/support/itunes/contact/
Cheers!

Problem with playback device message..

problem with playback device message.. been reading up about this problem but so far nothing has worked for me.. i have windows 7. Been trying to find the place in here to get some help but have no idea how this works. So if someone reads this.. please HELP me. Cheers

What OS are you running? What's the model of your computer/audio device? What does Skype list as your playback/recording device?

Problem with sending text messages replies

After update to OS 3.0 I have problem with sending text messages:
- I CAN send new text message to someone but
- When someone REPLY me, then I CANNOT send next message in conversation
- If I DELETE someone's reply from that conversation text message sends fine.
Anyone have this problem? I have iPhone 3g with OS 3.0 update, previously on 2.x the problem didn't appear. Carrier Orange in Poland

no my girlfriend, was useing my old N75, now she is useing her old phone last night and today. we have been texting with no problems at all. ..so i'm back in the iphone, and we're going to get her a new phone tonight,or she's going to use one of my other back-up phones till we get one for her. called at&t today to see if she could get an early upgrade before oct. just to make me happy with all the BS i've been through (10 hours or more on the phone trying to fix the problem). but at&t came through with their great customer satisfaction!!! NOT!!! so, gonna try and get her a good phone out of contract and see after hers and mine are up might just jump from at&t. very unhappy with them as how they handled this whole thing.

I'm having problems with my I messaging

I'm having problem with my I messaging please help

mine is working now, turn imessage off in settings,close the message app that is opened by double clicking the home button, restart the phone and turn imessage back on

Problem with SOAP FAULT messages

Similar Messages

Maybe you are looking for