SOAP Fault Invalid connection cookie.

My user, (Firefox 1.5 Windows XP) gets often a Dialog Box:
title: "SOAP Fault -Secure Global Desktop client"
Text:
"The following SOAP Fault was recieved from the server:
Invalid connection cookie.
Please contact your Secure Global Desktop administrator.
(Thats me!)
Button: "Ok"
How can I help him?

Hello,
you say you are using a single machine as a server, try this:
sometimes with a single machine people don't set up full naming services. you need (or should have) DNS entries for your machines.
If you don't have full DNS entries then put them into your host file. this includes any windows servers you are running apps from and any windows clients you may be connecting from.
you may even want to handle DHCP connections in the following way. if you have 20 DNS connections, then make entries in the hosts file like this (example only, use your own network address):
192.168.1.100 dhcp100
192.168.1.101 dhcp101
192.168.1.103 dhcp103
etc. the name is not important. just the entry.
this seems to have worked for me in connecting from hardwired and dhcp addresses.
regards,
tucker

Similar Messages

Invalid session cookie on High latency wan connections

Hello,
I've had users at a remote site complaining that they are getting disconnected regularly from the SGD server here and are then unable to reconnect for several minutes. The connection is a GRE tunnel over the between sites with several firewalls and proxies in between. As well, the clients are behind a NAT. This is a standalone server SGD 4.41. As a test, I set up an SGD server at the remote location and logged into it. I've been disconnected twice at random intervals with a popup dialog that says "Invalid connection Cookie" Please contact your Administrator. In the webtop browser window I attempted a refresh which resulted in a Session Expired message in the webtop message window. I login again and I see my application session still there but upon attempting to connect to it I receive the following:
Web Service Request Failed
The following fault was returned from the server
Code Client.InvalidSessionCookie
String <cookie info etc...> for admin:runCommand
In a subsequent incident I received a popup with the message: The session already has a Secure Global Desktop Client Connection
Once this popped up my webtop session was hung and I could not log back in to the SGD server until I closed my browser and restarted it.
The connection has high latency 365+ ms and is notoriously unstable. Again there are multiple firewalls and proxies between the sites that I have no access to.
Error logs show the following:
Any ideas?
bash-3.00# less jserver988_error.log
2009/06/15 20:01:50.932 (pid 988) server/soapcommands/error #1245076310932
Sun Secure Global Desktop Software (4.4) ERROR:
Invalid session cookie supplied for session 1245075516671:servername:2172620047794735723:Li4uL191c2VyL2VwZWVsZXI=.
The operation will fail.
Repeat the request with a valid session cookie.
2009/06/15 20:07:25.691 (pid 988) server/soapcommands/error #1245076645691
Sun Secure Global Desktop Software (4.4) ERROR:
Unable to write message of type webserver for servername:1245068645735:-3969341831847819217.
Request will fail.
The user should close the Secure Global Desktop Client process, end the
session and start a new session.
2009/06/15 20:07:28.867 (pid 988) server/soapcommands/error #1245076648867
Sun Secure Global Desktop Software (4.4) ERROR:
Invalid session cookie supplied for session 1245075516671:servername:2172620047794735723:Li4uL191c2VyL2VwZWVsZXI=.
The operation will fail.
Repeat the request with a valid session cookie.
2009/06/15 20:08:32.384 (pid 988) server/soapcommands/error #1245076712384
Sun Secure Global Desktop Software (4.4) ERROR:
Invalid session cookie supplied for session 6543220712367266453:servername:1245068645735:-3969341831847819217:1.
The operation will fail.
Repeat the request with a valid session cookie.

Hi DalamarUK83,
"I have seen posts about disabling VMQ on the host/guest servers as there may be an issue with this model - this has had no effect at all, the issue persists after changing VMQ and restarting both the guest and the host OS."
Did you disable the feature in advanced settings of physical NICs ?
I would suggest to re-create virtual switch after disabling VMQ .
What is the make of that NIC ?
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

GWWS_CAT:1022: SOAP Error: Invalid SOAP Body While processing Valid Soap Request

Hi,
I Following tuxedo version on AIX 6.1 Power 7 64 bit.
INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 095
Service Meta Information is :
service=StockQuote
export=y
servicetype=service
tuxservice=STOCKQUOTE
svcdescription=This service is used to demo security and xml buffer interop.
inbuf=XML
outbuf=XML
param=XMLBuffer
type=xml
access=inout
size=1000
this is actually picked from salt sample packaged with version 10.3.
Request Message:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns1="urn:salt.samples.wsdl"
xmlns:ns2="urn:pack.samples_typedef.salt11">
<SOAP-ENV:Body>
<ns2:StockQuote>
<ns2:inbuf>
</ns2:inbuf>
</ns2:StockQuote>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I put GWWS under tracing and found following.
Response Messag:
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --WAKEUP-->Created
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->Receive
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Found-->ParseHTTP
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:HTTP Parsing: Buffer length 1140 -- POST /secsapp HTTP/1.1^M
Host: uaix4070.unix.rabobank.nl:8070^M
User-Agent: gSOAP/2.7^M
Content-Type: text/xml; charset=utf-8^M
Content-Length: 437^M
Connection: close^M
SOAPAction: "StockQuote"^M
^M
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLS
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:chema"
xmlns:ns1="urn:salt.samples.wsdl"
xmlns:ns2="urn:pack.samples_typedef.salt11">
<SOAP-ENV:Body>
<ns2:StockQuote>
<ns2:inbuf>
</ns2:inbuf>
</ns2:StockQuote>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:parse_header_field() return 6
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->HTTPDispatch
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:A HTTP message is received, SCO index=4095
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Finding endpoint, soap->path is /secsapp, request_uri is /secsapp
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Post-->ParseSOAPHeader
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseHeaderRoot
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:A SOAP message is received, SCO index=4095
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --None-->ParseSOAPBody
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->ParseBodyRoot
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->ParseBodyElement
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Begin data transformation of request message, buffer type = XML, SCO index=4095
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Fail-->SOAPFault
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPBody
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackSOAPHeader
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->WSRMHandle3
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->PackHTTP
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:SCO[4095] FSM State Transition: --Default-->Send
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Sending HTTP Header: HTTP/1.1 500 Internal Server Error^M
Server: gSOAP/2.7^M
Content-Type: text/xml; charset=utf-8^M
Content-Length: 311^M
Connection: close^M
^M
150237.uaix4070!GWWS.5767178.1046.0: TRACE:ms:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>GWWS_CAT:1022: SOAP Error: Invalid SOAP Body.</faultstring></SOAP-ENV:Fault><
/SOAP-ENV:Body></SOAP-ENV:Envelope>
Is there something wrong with the request ? Are there known bugs with handling of Soap request in this version ?
Thanks & Regards,
Ajeet Tewari

Ajeet,
I believe that may be caused by the fact that the payload is empty (<inbuf></inbuf>). The gateway is very strict on that...
Regards,
Maurice

Not able to catch soap faults

My process is not able to catch soap faults. I can see the fault being thrown on the TCPMon Tunnel UI.
Following is the fault I see on the Tunnel UI :
HTTP/1.1 500 Internal Server Error
Server: WebSphere Application Server/5.1
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Set-Cookie: JSESSIONID=0000efI8on7qoNUcMQ3EHHBcdwI:-1;Path=/
Cache-Control: no-cache="set-cookie,set-cookie2"
Content-Type: text/xml; charset=utf-8
Content-Length: 555
Content-Language: en-US
Connection: close
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>com.mycompany.e2sc.soap.E2ScWebServiceSoap.endTransaction(com.mycompany.e2sc.xsd.StartTransactionRequest) -- no signature match</faultstring>
<faultactor>/e2sc/servlet/rpcrouter</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Any ideas ??
Thanks
Anand

This is a known regression on 2.0.10. It is fixed in 2.0.11. -Edwin

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>

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 Message on PI

Hi there,
I'm trying to map a SOAP Fault Response From a Legacy system on PI, but i have some doubts on how to create the Data Type and the fault message Type,
Basically the response will look like this:
<SOAP-ENV:Body>
   <SOAP-ENV:Fault>
      <faultcode>SOAP-ENV:Client</faultcode>
      <faultstring>Data failed validation</faultstring>
      <detail>
           <fault xsi:type="ns1:Fault">
                <ns1:code>1002</ns1:code>
                <ns1:errorMessage>Data failed validation</ns1:errorMessage>
                <ns1:detailMessage>Invalid (does not exist) Zone Identity...</ns1:detailMessage>
           </fault>
      </detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
so basically i defined a data type detail ( named detail aswell in pi ), with a fault element and code errorMessage and detailMessage xsd:String attributes ( i dont know what to do with that ns1 xsi type )
but when i want to creat the whole message PI only allows me to have 1 outter element like this:
<FaultMessage>
   <faultcode>
   <faultstring>
   <detail>
so pretty much i want to have a data type with 4 independent elements cause i know the SOAP-ENV tags wont get to the mapping, im almost sure i'm missing something very dumb here but i dont see it ,
Thanks in advance for all the help you guys can provide,
Regards,
Roberto.

Thanks for the documention it was really helpful,
now i have another problem, i alredy created the data type for the detail tag to match the soap response, but when creating de Fault Message Type on the Data Type Used area, PI inserts me some standard data that is mandatory and does not correspond with the structure im going to receive, it only allows me to import the detail data type as Additional data :S.
Regards,
Roberto.

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

SOAP Fault for Application errors

Hi,
I would like to know whether it is OK to raise a SOAP fault for Application or system level exceptions. For example, I'm searching for a user with an ID as request , If the ID is invalid(User is not found) is it OK to raise the SOAP Fault.
Let me know your views regarding the same.

Hi,
With the above explination , please see the below links..
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7521a237-0701-0010-499b-b3285b789c0d
/people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server
/people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi
Alert rule for SOAP adapter
Monitoring problem in async SOAP receiver adapter
Trapping AF errors using Alert framework in XI 3.0 SP13
Alert Configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f2a9fa2-0a01-0010-32ac-d281db722b86
SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function
Regards
Chilla..
<i>Points rewarded if it is useful..</i>

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.

Authentication Fault: Invalid User Session Token

Hi,
I am trying to protect a call to third party webservices using OWSM and OAM. I followed the steps mentioned in Oracle Web Services Manager
Deployment Guide to integrate OAM in OWSM, but not able to make any break through. I am getting following error if I test my web service using OWSM's inbuilt test tool:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode
xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults">p:Client.AuthorizationFault</faultcode>
<faultstring>Authentication Fault: Invalid User Session Token</faultstring>
null</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
In gateway.log file, I get following oneliner message:
security.SimpleXMLCredsExtractor - SimpleXMLCredsExtractor failed to Extract creds.
I am using standalone OWSM installation.
Installed OAM SDK on the same machine of OWSM.
Added OAM SDK libraries into OWSM's path.
Please advise as I have already wasted 3-4 weeks into it.
.. Paresh
Edited by: user10301925 on Sep 29, 2009 2:24 AM
Edited by: user10301925 on Sep 29, 2009 2:24 AM

Hi,
Yes, I have registered the service in OWSM and calling that service through OWSM testing tool only...
Following is the request message:
<?xml version="1.0" encoding="UTF-8" ?>
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
- <soap:Header>
- <wsse:Security env:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
- <wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Username>owsmuser</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">welcome11</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
- <soap:Body xmlns:ns1="http://service/">
<ns1:getDateTime />
</soap:Body>
</soap:Envelope>
Please advise.
.. Paresh

OSB does not return SOAP fault

We created a custom webservice using a WSDL.
We have the following code within the generated Impl class:
LOG.debug("caught Exception sendAlertMessage:" + exc.getMessage());
SOAPFault sf = null;
try {
SOAPFactory fac = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL);
sf = fac.createFault(exc.getMessage(), new QName("http://www.w3.org/2003/05/soap-envelope", "Receiver"));
}catch (SOAPException sfexc){
LOG.debug("error creating SOAP fault. " + sfexc.getMessage());
System.out.println("error creating SOAP fault.");
sfexc.printStackTrace();
throw new SOAPFaultException(sf);
We dont have a fault defined in the WSDL operation, but we were following this article, which says we don't need that to be defined:
http://one-size-doesnt-fit-all.blogspot.com/2009/05/jax-ws-throwing-generic-soapfaults_06.html
The file shows it was generated using JAX-WS 2.1.3
We are using OSB 10gR3 and testing the web service with SOAP-UI. When an invalid message hits this service it gets to this code. The log statements show that the soap fault is created successfully. The throw new SOAPFaultException(sf) line is called but when you check the response headers in SOAP-UI the status is #status# HTTP/1.1 202 Accepted. This should be HTTP 500 if the SOAP fault worked.
This is an async webservice and therefore does not have a response message either.
Any thoughts would be helpful.Thank you.

what does OSB do, it simply routes the SOAP message to your Web Service?
In fact if it's an asynchronous (messaging type, no response) service which is invoked, it seems OK that you don't get any fault;
the message has been successfully routed to destination, if the destination fails it's another story that probably you will only be able to detect by a timeout on the client side.
also, "publish"ing a message doesn't report the error to the caller.
The only case where the caller gets the fault is by routing to a request-reply service.
If I am wrong please correct me.

Oracle SOA Suite - SOAP Fault content not being returned

It starts with a fairly standard scenario: from within a BPEL process in Oracle SOA Suite, I’m making a call to an external web service. The not-so-standard part: the owner of the external web service has decided to return all errors in the form of a SOAP fault. Unfortunately, this error schema is not included in the WSDL. If we call the external web service directly (via SOAPUI, for example), we get the following, including a nice explanation of why it errored out:
<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:err="error.xml.common">
<faultcode>soapenv:Server</faultcode>
<faultstring>Undefined</faultstring>
<detail>
<err:ErrorList>
<err:Error>
<err:Application>CIA</err:Application>
<err:Code>1031</err:Code>
<err:Description>Field value is invalid Credit Card Number V failed mod10 check</err:Description>
<err:ServerTime>2010-02-25T17:37:38.472-05:00</err:ServerTime>
</err:Error>
<err:StackTrace>subscription.memberservices.common.exception.ServiceInvocationException: 1031~Field value is invalid Credit Card Number V failed mod10 check
at subscription.memberservices.common.client.http.CiaHttpClient.checkForErrors(CiaHttpClient.java:120)
at subscription.memberservices.common.client.http.CiaHttpClient.enroll(CiaHttpClient.java:50)
at subscription.memberservices.na.processes.enroll.EnrollProcess.callCiaEnroll(EnrollProcess.jpd:1003)
at subscription.memberservices.na.processes.enroll.EnrollProcess_wf$ImplControlSend14.invoke(EnrollProcess_wf.java:145)
at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
... 38 more</err:StackTrace>
</err:ErrorList>
</detail>
</soapenv:Fault>
No matter what I try, however, I can’t fetch the information in the “detail” element above. When examining the audit trail in SOA Suite, I can only see this:
<fault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>Undefined</summary>
</part>
<part name="detail">
<detail>javax.xml.ws.soap.SOAPFaultException: Undefined</detail>
</part>
<part name="code">
<code>null</code>
</part>
</remoteFault>
</fault>
It seems SOA Suite is “protecting” my service from the other SOAP fault elements instead of passing everything back, only passing the faultstring element. I even tried adding an ErrorList schema to match theirs but to no avail. Anyone out there have any experience, luck or ideas with this problem?
Thanks for the assistance,
Rob

Re: Oracle SOA suite server does not startBut I can see that server has got started -
<21-Jul-2010 12:04:47 o'clock BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>em application gets deployed on admin server and not on SOA server. You may access em console on - http://<hostName>:<admin_server_port>/em
By default admin server port is 7001.
Regards,
Anuj

Invalid connection cache name error while invoking a bpel process

while invoking a service via DB adapter ,it gives invalid connection cache name orabpel 00000 error. the JCA connection is set properly and its reffered via jndi name in code. i tested the connection in EM and its working fine.
Few transactions have passed and thereafter i'm getting this error.
is there any parameter that needs to be set. Someone can help here!!

Have got the same problem. Scenario at my end is little different though.
I am trying to invoke a BPEL process from an ESB Service.
I am trying to look into it..
However, would be grateful, if someone can give some insight into this since many are running into this issue without being able to fix.
Ashish.

SOAP Fault Invalid connection cookie.

Similar Messages

Maybe you are looking for