SOAP 1,007 unsupported xstream found

Dear experts-
We are implementing Learning portal. We have done the setup most of our services are working as desired. Except for iview in course admin, to publish course content.
In the publish course content iview when users select the browse functionality next to source file we are getting a
SOAP 1007 unsupported xstream found: (TTP code 401 : un authorized")
Has any one seen this error before?
I dont see any entries in the logs either.
You suggestions are most welcome.
Thanks,
John.

Hi,
Did you resolve your problem????? could you tell me how did you do that?
Thnahs a lot

Similar Messages

SOAP:1.007 SRT: Unsupported xstream found: ('HTTPCode 503 : Service Unavail

Hello ,
while importing the message mapping (in which RFC look up is used) from development to quality server, we are getting RC = 12 .
The error log shows the following error:
SOAP:1.007 SRT: Unsupported xstream found: ('HTTPCode 503 : Service Unavailable')
The server is Up and the credentials are also correct.
Can anyone suggest what can be the solution for this?
Do we need to include any specific objects in the Transport?
Thank you,
Siva

Hi Ranjani,
Please refer this forum thread discussed on a similar issue. [CTS+ For Portal Error: SoapFaultCode:1 Authentication failed; It might help you to move further.
Thanks
Uaruna

("HTTP Code 200 : OK") SRT: Unsupported xstream found

Hi,
when I am trying send a request to an external webservice
I am getting this message. Do you have an idea what can cause this error.
Regards
ilhan
Server: SAP Web Application Server (ICM)
HTTP/1.1 500 Internal Server Error
set-cookie: MYSAPSSO2=AjQxMDMBABhBAFIAQwBIAEkAQgBVAFMAIAAgACAAIAACAAYyADgAMQADAB
BFAFMAUgAgACAAIAAgACAABAAYMgAwADAAOQAwADUAMgA2ADAAOQAwADcABQAEAAAACAYAAlgACQACRA
D%2fAPswgfgGCSqGSIb3DQEHAqCB6jCB5wIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBMYHHMIHE
AgEBMBkwDjEMMAoGA1UEAxMDRVNSAgcgCAYQFiMnMAkGBSsOAwIaBQCgXTAYBgkqhkiG9w0BCQMxCwYJ
KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA1MjYwOTA3NDNaMCMGCSqGSIb3DQEJBDEWBBThnsmT
%2f90RLKhrO%2fWjjbrvDvw%21czAJBgcqhkjOOAQDBC8wLQIUTDMZiy9E9buJoePGCdCDg5BwYvsCFQ
DQGyevsV2OfRgF9ol%2fQJKRj9l%214Q%3d%3d; path=/; domain=apslidl
content-type: text/xml; charset=utf-8
content-length: 675
accept: text/xml
sap-srt_id: 20090526/110743/v1.00_final_6.40/DE49D4AA07D6C6F1BC1E000C29A9F676
server: SAP Web Application Server (1.0;700)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><s oap-env:Header></soap-env:Header><soap-env:Body><soap-env:Fault><faultcode>soap-
env:Server</faultcode><faultstring xml:lang="en">SRT: Unsupported xstream found:
("HTTP Code 200 : OK")</faultstring><detail><ns:SystemFault xmlns:ns="http://w
ww.sap.com/webas/710/soap/runtime/abap/fault/system/"><Host>undefined</Host><Com
ponent>COREMSG</Component><ChainedException><Exception_Name>CX_SOAP_CORE</Except
ion_Name><Exception_Text>SRT: Unsupported xstream found: ("HTTP Code 200 : OK")
</Exception_Text></ChainedException></ns:SystemFault></detail></soap-env:Fault><
/soap-env:Body></soap-env:Envelope>

hi
the error message comes if I use this tool http://curl.haxx.se/
When I use this tool I dont get an error. http://www.eviware.com/
To sum up:
What do you thing what the error causes ?
- the wsdl format is not correct
- you are saying "just compare the two clients"
what can I compare with them
Regards
ertas

SRT: Unsupported xstream found: ("HTTP Code 400 : Bad Request")

hi,
I get the error message
SRT: Unsupported xstream found: ("HTTP Code 400 : Bad Request")
what can cause that. I have created a RFC Connection have tested it, it workd well.
But when I call CALL METHOD r_user->MAP_R3USER i get this message.
Regards
sas

Thanks.
Kindly take note that the "Comment" field is not mandatory, so there is no need to bounce all 200 threads to the top again.
You can leave threads unanswered when you still hope or suspect that an answer might be searched be someone, but if it is a "dead duck" (like many cross-posted threads are - which often cause this problem) then please close them.
People who neglect following up on their threads, often neglect thanking those who put in an effort to help with helpfull answers. But many people notice this and stop answering. That does not apply in your case in posts since about July this year, so if you clean up then I am sure that you will further benefit from it.
Please take this in a positive way. Personally I enjoy reading some of your questions and learn from them as well.
Cheers,
Julius

"Unsupported xstream found: ("HTTP Code 200 : OK")

Hi,
I am trying to consume an webservice using ABAP (standrad web service provided by SAP). I am getting an error "Unsupported xstream found: ("HTTP Code 200 : OK")".
Has anybody faced this problem before ?
Regards
Goutam

Hey,
This is the description.along with the note.
1) Error: HTP 200 OK
Description: The request has succeeded. The information returned with the response is dependent on the method used in the request GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body; POST an entity describing or containing the result of the action; TRACE an entity containing the request message as received by the end server.
Possible Tips: Have a look into SAP Note: 871959

Error Consuming Web Service:Unsupported xstream found:("HTTP Code 200:OK")

I am trying to consume a web service from an Outbound Proxy. I am getting the following error message:-
Unsupported xstream found: ("HTTP Code 200 : OK")
This is a System Exception generated while I call the Outbound Proxy.
Kindly let me know what could be the issue.
An early reply will be highly appreciated as I am getting this issue in my Production Server.

This doesn't appear to be a Web Dynpro related question. Please only post Web Dynpro ABAP related questions in this forum.

SOAP:1,007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")

Dear expert,
When i run sap call .net web service ,it occurs error:
SOAP:1,008 SRT: Couldn't create Object: ("ICF Error when creating object for HTTP DESTINATION "tempuri.org": DESTINATION NOT FOUND")
Exception of class CX_AI_SYSTEM_FAULT
Could you please tell me how to do?
Looking forward to your reply.
Best Regards,
Merry

Hi Merry,
Did you create a logical port (using transaction code SOAMANAGER) for your client proxy & add the necessary configuration pointing to the .NET web service?
Also, if the logical port is configured, make sure that the URL ( for WSDL with endpoint) that you've specified for the logical port is correct. Error 404 generally means that you have made contact with the service provider but it can't find what you're looking for.
As a quick sanity test, you can run a test request to the service provider using a free tool SoapUI just to make sure that everything on the provider side is ok (i.e. they have provided correct WSDL with binding)
In future, please post this type of question in the SOA forum, see URL below, that's the correct forum for it. Thanks:
Service-Oriented Architecture (SOA) and SAP
Regards, Trevor

"Error while parsing SOAP XML payload: no element found" received when invoking Web Service

Running PB 12.1 Build 7000. Using Easysoap. Error ""Error while parsing SOAP XML payload: no element found" received when invoking Web Service". This error does not appear to be coming from the application code. Noticed that there were some erroneous characters showing up within the header portion of the XML ("&Quot;"). Not sure where these are coming from. When I do a find within the PB code for """" it gets located within two objects, whereas they both reference a "temp_xml_letter". Not sure where or what temp_xml_letter resides???   The developer of this is no longer with us and my exposure to WSDL and Web Services is rather limited. Need to get this resolved...please.
This is the result of the search. Notice the extraneous characters ("""):
dar1main.pbl(d_as400_mq_xml)
darlettr.pbl(d_email_xml)
---------- Search: Searching Target darwin for 'temp_xml'    (9:52:41 AM)
---------- 2 Matches Found On "temp_xml":
dar1main.pbl(d_as400_mq_xml).d_as400_mq_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> number </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
darlettr.pbl(d_email_xml).d_email_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> imcnumber </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
---------- Done 2 Matches Found On "temp_xml":
---------- Finished Searching Target darwin for 'temp_xml'    (9:52:41 AM)

Maybe "extraneous" is an incorrect term. Apparantly, based upon the writeup within Wiki, the parser I am using does not interpret the """? How do I find which parser is being utilized and how to control it?
<<<
If the document is read by an XML parser that does not or cannot read external entities, then only the five built-in XML character entities (see above) can safely be used, although other entities may be used if they are declared in the internal DTD subset.
If the document is read by an XML parser that does read external entities, then the five built-in XML character entities can safely be used. The other 248 HTML character entities can be used as long as the XHTML DTD is accessible to the parser at the time the document is read. Other entities may also be used if they are declared in the internal DTD subset.
>>>

Load/Metadata (Manifest): LoadTechnical: Unsupported childNode found in Technical Metadata...

Load/Metadata (Manifest): LoadTechnical: Unsupported childNode found in Technical Metadata:ScormEnginePackageProperties
Anyone know what this message means? I have the eLearning Suite 6.01

Hi Ryan,
Make sure that Captivate's complete version should be 6.0.1.240 or 6.1.0.319. (Help > about Adobe Captivate).
On which LMS are you uploading your Scorm Compliant Course?
Have you published as SCORM 1.2 or SCORM 2004?
Thanks.

** SOAP to SOAP call - HTTP 404 not found - invalid content type

Hi friends,
We have one scenario SOAP to SOAP call. It is synchronous interface. We are calling the WSDL.
For some of the messages (not all), we are getting the error in SXMB_MONI
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
In the sender & receiver SOAP communication channel also, same error : SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
Friends, this error is not coming for all messages. For some of the messages it is coming. For example,
10:50 - Message Processed Successfully
10:54 - Message Processed Successfully
10:59 - Error
11:05 - Message Processed Successfully
By looking threads and blogs, I implemented MessagesTransformBean in the receiver CC and added the parameter Transform.ContentType as 'text/xml;charset=utf-8'.
After implementing this also, error is coming for some of the messages.
Can you kindly clarify friends, what could be the problem?
Kind regards,
Jegathees P.

I'm in agreement with Stefan...
If the problem is intermittent then the system is overloaded at certain times. You would probably need to do some JVM analysis to see the resource usage & look at increasing the memory.
Regards, Trevor

SOAP Fault Exception: method not found

Hi,
I've tried to consume a web service (written in Java) in ABAP using a generated client proxy with logical port. I receive return code 500 and a fault exception like "method for requestMethod was not found".
Has anyone a hint?
Thanks in advance,
Daniel

I have not seen that error before, but my first suggestion would be to state the obvious - check your logical port definition and make sure that the settings are correct, i.e., that they match the WSDL document. You'll want to check that the SOAP Action on the Operations tab is correct and that the URL for the web service is correct on the Call Parameters tab.

SOAP client receives HTTP 302 Found

Hi all
I have a message interface for which I generated a wsdl pointing to the SOAP adapter:
http://server:50000/XISOAPAdapter/MessageServlet?channel:=servicename:channelname
If I am using SAP Soap Client to send a request (http, HTTP Basic Auth.) everything is fine, the message is in the SOAP adapter, in IS and I receive a correct SOAP response.
But if am using other clients, e. g. SoapUI, I get an HTTP 302 Found error back before the data even reaches the SOAP adapter (no message there).
Has anybody an idea how to solve this or where to find more information about it?
Thanks in advance

Thanks for your answers,
but I am still lost with this error. The cluster only consists of one server node and the redirect posts to
http*s*://server:5000*1*/XISOAPAdapter/MessageServlet?channel:=servicename:channelname
So it changes to https. Why is this? What is the client (which is a standard application that we cannot change) supposed to do?
Thanks for any info
Hans

Solution Manager Diagnostics - Installation

I have installed SM EHP1 and have also installed SMD. However during the Basic configuration of SM, I'm getting Diagnostics Configuration errors during the Automatic Configuration phase of the Diagnostics configuration. The errors showing up are:
1. Cannot call Diagnostics Setup web service
2. Web Service URL: http://atl-osm-01.oversightsystems.com:8100/DiagSetupServices/Di...
3. SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
4. Error when processing Web service call
5. Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 404 : Not Found")
What am I missing here?
Thanks for the help.

Hello Hans.
Have you solved the problem? We have a similar problem with Solution Manager 7.0 EHP1 SP27.
Errormessage (parts are in German):
Web Service URL: http://solman.company.com:8100/DiagSetupServices/DiagSetupConfig?style=document
Cannot call Diagnostics Setup web service
SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 404 : Not found")
Beim Prozessieren eines Web Service-Aufrufs ist ein Fehler aufgetreten.
Fehler beim Aufruf von Funktionen der SOAP Runtime: SRT: Unsupported xstream found: ("HTTP Code 404 : Not found")
Note: We have changed the http and https-Ports of ICM. Solution Manager is working fine, but Solution Manager Diagnostics Setup does not work.
Thank you for a hint.
Best regards,
Tobias

CODE 400 - Error Consume WebService

Dear,
I'm trying to consume a Webservice in ABAP program.
I create a Client Proxy (via SE80) and a Logical Port Configuration (via LPCONFIG).
But when I test the client proxy in SE80 this error occurs "SOAP: RTS 1007: Unsupported xstream found: (" HTTP Code 400: Bad Request ")
Who knows what can it be?
Regards,
Rogerio

Hi,
It's because of 2 possible things.
1) ur URL Not responding Means (logical port IP or URL)
2) The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. Check Deatils in
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Salil .....

CX_AI_SYSTEM_FAULT : SOAP:1.023 SRT

Hello Experts -We have been facing below issue in Solution manager 7.1 SP08 - Managed system configuration - Extractor setup
CX_AI_SYSTEM_FAULT : SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_TIMEOUT")
Text(2) Text(2)
CX_SOAP_FAILURE : Error when processing Web service call
Text(3) Text(3)
CX_SOAP_CORE : Error when calling SOAP Runtime functions: SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_TIMEOUT")
We have already looked at all the below notes and followed the steps
1822831 - Web Service Soap Errors in solman_setup
1860293 - Extractors Setup Error "CX_AI_SYSTEM_FAULT : SOAP1,023 SRT" and "ICM_HTTP_TIMEOUT" in Solution Manager 7.10
1885130 - "ICM_HTTP_TIMEOUT" during SOLMAN_SETUP.
1837656 - Extractor Setup returns "CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 500 : Timeout")" - Solution Manager 7.10
our LMSERVICE and ISAGENT patches are on the latest version.
I get below error logs in DEV_RFC log file in Work directory -
RFC> Begin of user trace
XRFC> ---------------------------------------------------------------------
XRFC>                                                                     <
XRFC> TRACE SOAP RUNTIME - header                                         <
XRFC>                                                                     <
XRFC> ------------------------------------------------------------------ <
XRFC> REQ_SIZE   : 1724                                                   <
XRFC> PARENT_ID : ROOT_CALL_ID                                           <
XRFC> TRC_KEY    : DF8BA9E3E673F1078793005056B86220                       <
XRFC> REQ_BASED :                                                        <
XRFC> SESSION_ID : 00013255DF8BA9E3E573F1FA8793005056B86220               <
XRFC> TS_CALL    : 20140312021317.7990000                                 <
XRFC> SY_UNAME   : UsrID                                               <
XRFC> HOSTNAME   : IMXW08V714                                             <
XRFC> SY_SID     : ILR                                                    <
XRFC> SY_MANDT   : 100                                                    <
XRFC> SYS_NR     : 00                                                     <
XRFC> APPLSERVER : ServerHostname                                    <
XRFC> ISPRESCHED : X                                                      <er
XRFC> DURATION   : 605850                                                 <
XRFC> NETHDRTIME : 605850                                                 <
XRFC> CALL_STATE : 2                                                      <
XRFC> ERRORTYPE : SYSFAIL                                                <
XRFC> ERRORAREA : COREMSG                                                <
XRFC> CTXDP_TYPE : SOAP_RUNTIME                                           <
XRFC> SYNC_ASYNC : S                                                      <
XRFC> LOCATION   : C                                                      <
XRFC> DIRECTION : O                                                      <
XRFC> REQ_ID     : 005056B862201ED3AAB1A914E2EC4793                       <
XRFC> RESP_ID    : 005056B862201ED3AAB1A914E2EC6793                       <
XRFC> MSG_STATE : 114                                                    <
XRFC> IF_NAME_I : CO_DIAGSTP_WS_DIAG_SETUP                               <
XRFC> IF_NS_E    : urn:DiagSetupServices/DiagSetupServices/document       <
XRFC> IF_NAME_E : DiagSetupServices_Document                             <
XRFC> ISSHORTCUT :                                                        <
XRFC> TRC_PATT   : WSTEST                                                 <
XRFC> TRC_SSID   : ILR_00                                                 <
XRFC> TRC_USER   : UsrID                                               <
XRFC> TRC_TS     : 20140312021317                                         <
XRFC> TRC_COUNT : 99                                                     <
XRFC> TRC_EXT    :                                                        <
XRFC> COMPLETE   : OK                                                     <
XRFC> CALLEDPROG : CO_DIAGSTP_WS_DIAG_SETUP                               <
XRFC> SOAP_APPLI : urn:sap-com:soap:runtime:application:client:710        <
XRFC> CONF_ID    : 005056B862201ED3A895BB5E31E04793                       <
XRFC> BIND_ID    : 005056B862201ED3A895BB5E31E0A793                       <
XRFC> OP_NAME    : managedSetup                                           <
XRFC> COMM_PATRN : Method:managedSetup                                    <
XRFC> OP_NS      : urn:DiagSetupServices/DiagSetupServices/document       <
XRFC> REMADDRESS :                                                        <
XRFC> LP_NAME    : DIAGSTP_WS_LOCAL_PORT                                  <
XRFC> DT_OBJ     : CO_DIAGSTP_WS_DIAG_SETUP                               <
XRFC> MEMCONSUMP : 272                                                    <
XRFC> WSHOST     : solmanHostname                               <
XRFC> WSPORT     : 8000                                                   <
XRFC> WSPROT     : http                                                   <
XRFC> WSCLIENT   :                                                        <
XRFC> WSPATH     : /DiagSetupServices/DiagSetupConf?style=document        <
XRFC> PXYHOST    :                                                        <
XRFC> PXYPORT    :                                                        <
XRFC> USEDRFCDES :                                                        <
XRFC> BONAME     :                                                        <
XRFC> PROCCOMP   :                                                        <
XRFC> DEPLOYUNIT :                                                        <
XRFC> ------------------------------------------------------------------ <
XRFC>                                                                     <
XRFC> TRACE SOAP RUNTIME - trace records                                  <
XRFC>                                                                     <
XRFC> ------------------------------------------------------------------ <
XRFC> E SOAP_RUNTIME 20140312022323.5780000 : CL_SOAP_RUNTIME_CLIENT      <
XRFC> ->EXECUTE_PROCESSING Exception handling for IF "CO_DIAGSTP          <
XRFC> _WS_DIAG_SETUP" OP name "managedSetup" MSG ID "005056B862201ED3AAB <
XRFC> 17BEE7CC1E793" user "UsrID"                                      <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_APPLICATION 20140312022323.5790000 : CL_SOAP_APPLICATION     <
XRFC> _CLIENT ->IF_SOAP_APPLICATION_CS~EXECUTE_PROCESSING Exception       <
XRFC> handling in SOAP runtime                                            <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_RUNTIME 20140312022323.5780000 : CL_SOAP_RUNTIME_CLIENT      <
XRFC> ->EXECUTE_PROCESSING A SOAP Runtime Core Exception occurred in      <
XRFC> method IF_SOAP_TRANSPORT_BINDING~RECEIVE of class CL_SOAP_HTTP      <
XRFC> _TPBND_ROOT at position id 1 with internal error id 1023 and error <
XRFC> text SRT: Processing error in Internet Communication Framework:     <
XRFC> ("ICF Error when receiving the response: ICM_HTTP_TIMEOUT") (fault <
XRFC> location is 1 ).                                                    <
XRFC>                                                                     <
XRFC>                                                                     <
XRFC> E SOAP_APPLICATION 20140312022323.5790000 : CL_SOAP_APPLICATION     <
XRFC> _CLIENT ->IF_SOAP_APPLICATION_CS~EXECUTE_PROCESSING A SOAP Runtime <
XRFC> Core Exception occurred in method IF_SOAP_TRANSPORT_BINDING         <
XRFC> ~RECEIVE of class CL_SOAP_HTTP_TPBND_ROOT at position id 1 with     <
XRFC> internal error id 1023 and error text SRT: Processing error in      <
XRFC> Internet Communication Framework: ("ICF Error when receiving the    <
XRFC> response: ICM_HTTP_TIMEOUT") (fault location is 1 ).                <
XRFC>                                                                     <
Can any please advise ? We already have OSS message created for this issue, no reply from SAP yet.
Awaiting your reply -
Thanks
-Lee

Hi Swarali,
Did you get any response from SAP on OSS?
what was the resolution as we are having the same problem in our landscape.
-ujjwal

SOAP 1,007 unsupported xstream found

Similar Messages

Maybe you are looking for