("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

Similar Messages

  • 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

  • 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

  • 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

  • SAP consume external web service - HTTP Code 200 : OK

    Hi
    We are integrating UPS Shipping Ground Web service with SAP system and we have the settings in place on our side and did a blank request test today and we are getting a " HTTP Code 200 : OK " error instead of a response.
    The SAP SOAManager shows the below detail for the error:
    A SOAP Runtime Core Exception occurred in method get_http_headers of class CL_SOAP_HTTP_TPBND_ROOT at position id 3 with internal error id 1007 and error text SRT: Unsupported xstream found: ("HTTP Code 200 : OK") (fault location is 1 ).
    One thing we noted but not sure about it is that the response content type is showing text/plain while the request shows content type accept text/xml in SOAManager trace functionality. (screen shot )
    I see several discussion on this but could not figure out what needs to be changed in SE80 consumer proxy or the SOAManager port level. Please advice.
    Regards,
    Prabaharan G

    hi Prabaharan! thanx for answer!
    i do integration with document scanning/recognitioning system (ABBYY FlexiCapture). It interact as SOAP services over MS IIS server in local network.
    what i`ve done:
    - drop everething at first.
    - create proxy in se80 using wsdl file. created ok.
    - create logical port in soamanager using "Create WSDL based configuration". created ok.
    - go to sm59. there are some connections but nothing like my connection. i have check all sections, not only type G(HTTP).
    AND HERE HAPPEN GREAT THING!
    Test "ping" fail but my test code start to work!
    All I have change is "url access path". So i think that was my problem. (I was confused by ping fail early and have trying to change all settings)
    you bring me luck - thank you very much!

  • Error in Web Service SOAP Calling HTTP Code 200

    Hi Gurus,
    I'm new of this forums, I hope you can help me in my realy strange problem.
    I' ve create a Web Service ( SAP ) and my job it's to create a Adobe Interactive Forms with LiveCycle,
    that connect to WS and recive some Binding values.
    When I import the WSDL in my LiveCycle and create the form, all works fine.
    When I preview the pdf generated, I have this kind of error in the xml returned:
    soap-env:Server sap SRT: Unsupported xstream found: ("HTTP Code 200 : OK")
    When I change button type from Submit to Execute, the preview pdf generated don't works...
    I press the button more times and don't works too.
    Reguards
    Nicola Bisinella

    Hi to all,
    I have resolved my problem installing Adobe Acrobat Pro and creating the pdf with it...
    Thanks
    Nicola Bisinella

  • "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 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

  • The test encountered an error while signing in to Outlook Web App. HTTP code: 200

    Infrastructure: Exchange 2010 SP3 RU2 environment on 17 servers worldwide with CAS, MB, HUB and UM roles. Server 2008 R2 VM's on Hyper-V 2008 R2.
    Trying to run the following command to test OWA connectivity on a server in the same Active Directory domain but in a different AD site:
    Get-ClientAccessServer -Identity Server1 | test-owaconnectivity -AllowUnsecureAccess -TrustAnySSLCertificate
    I get the reponse:
    WARNING: [11:04:51.276] : An Outlook Web App page wasn't received.
    WARNING: [11:04:51.276] : The test encountered an error while signing in to Outlook Web App.
    HTTP code: 200
    WARNING: [11:04:51.276] : Test failed for URL 'https://server1.domain.com/owa/'.
    ClientAccessServer        MailboxServer            URL                                               
    Scenario       Result       Latency          Error
    Server1.domain.com      Server2.domain.com  https://server1.domain.com/owa  Logon           Failure                           
    The test encountered an error while signing in to Outlook Web App. HTTP code: 200
    This is the same error message received from SCOM on its tests also.
    I have created a test account on all 17 servers using ./new-TestCasConnectivityUser and ensured their mailboxes reside on the correct server in the correct database.
    All internal servers are set for OWA and ECP for Windows Authentication. Only public facing CAS servers are set to Forms based. That said, have checked the 'Microsoft Exchange Forms-Based Authentication service' is running on both Server1 and Server2 as
    are all Exchange services except 'Microsoft Exchange IMAP4' (not used) or 'Microsoft Exchange POP3' (not used).
    However, if I run this command:
    test-owaconnectivity -AllowUnsecureAccess -TrustAnySSLCertificate -URL
    https://server1.domain.com/owa
    I get the following success after I have entered my correct credentials:
    Windows PowerShell Credential Request : cmdlet Test-OwaConnectivity at command pipeline position 1
    Warning: This credential is being requested by a script or application on the Server2.domain.com remote computer.
    Enter your credentials only if you trust the remote computer and the application or script requesting it.
    Supply values for the following parameters:
    MailboxCredential
    ClientAccessServer  MailboxServer  URL                                                
    Scenario              Result      Latency    Error
    (ms)
                                                            https://server1.domain.com/owa  
    Logon                 Success    6282.13
    So if I login with my domain username, it works and logs in. If the script runs using the 'extest....' user account created by the above ./new-TestCasConnectivityUser.ps1 , it does not work.
    Has anyone got any ideas please? I know its not the network as it works under my username, I know all fo the services required are running as it works under my username. There are no entries at all in the receiving server's error logs for Application, System,
    Exchange or Powershell at all.
    Any help greatly appreciated.
    Danny

    Did you read this?  http://support.microsoft.com/kb/2277649/en-us
    Did you run Test-MapiConnectivity? If not, can you run and post results? 
    HossFly, Exchange Administrator

  • Flash remoting returns HTTP code 200, classified as error

    Hi,
    Our problem is with an older application, originally created with Flash MX2004.  It is an application which schools use and communicates with our Java services.  We've always had some issues with remoting errors but it seems this past school year has been much worse.
    The issue does not happen all the time and the schools have reported it as  being sporadic.  We have been working with the schools to see if we can track  down the issue and what we’ve found is that the data is coming back to the  application correctly but it is somehow interpreted as an error within the  Macromedia classes.  Currently, the schools are reporting that their labs which have IE8 seem to be getting the issue while it is OK in the labs which still run IE7.
    Has anyone heard of a similar issue in that they can point us in the right direction to get this resolved?

    to add to the above details, when i look at the headers of the response object i see the following:
    HTTP/1.1 200 OK
    Server: Apache-Coyote/1.1
    X-Powered-By: Servlet 2.4; JBoss-4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)/Tomcat-5.5
    Content-Type: application/x-amf
    Content-Length: 18893
    Date: Wed, 07 Oct 2009 15:52:24 GMT
    Cache-Control: no-cache
    but when i look at the properties of the Connection object i see:
    contentType: application/x-fcs
    Is it normal for it to be different like this?

  • 'HTTP Code 404  : Not Found' in SE80

    Hi,
    I have consumed WSDL using consumer proxy in SAP system. Now I am trying to test this proxy.
    But, getting error
    Error when calling SOAP Runtime functions: SRT: Unsupported xstream found:
    ("HTTP Code 404  : Not Found")
    I have maintained correct URL and port, computer name in SOAMANAGER, still I am getting this error.
    Please advice.
    Regards,
    Sneha Nikam

    Hi Sneha,
    Please check if you created logical port in SOAMANAGER and same logical port is used in the proxy class.
    please also check below discussion
    Re: Error when Consuming Service in ABAP
    regards,
    Harish

  • BC 4.8 sending a HTTP Code or an own XML Response

    Hi Guys,
    I receive an ORDRSP (ORDERS05) about http and the supplier needs a status code, that the request was successfully. HTTP Code 200 or an own XML Response are great.
    Is it possible to do this with the BC 4.8?
    Any Ideas?
    Greetings,
    Michael
    Edited by: Michael Nett on Jul 30, 2010 12:04 PM

    Hi ,
    Refer these links,
    http://w3.miraclesoft.com/msws/msoft/products/oracle/pdf/SAP-IDOC_Article.pdf
    http://www.sap.com/korea/partners/icc/scenarios/pdf/ICC_INTEGRATION_GUIDE_22.pdf
    http://www.soberit.hut.fi/T-86/T-86.161/2004/Final%20report%20SAP_RN%20.pdf
    regards,
    Suryanarayana.M

  • Receiver XI adapter error :HTTP Status Code 200 during Reponse Parsing

    Hi Exeprts,
    My Scenario is mail to ABAP proxy , I have got the bellow error in moni  while testing my secnario .
    Please help me reslove this .
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    Regards
    Upendra

    Hi Mark ,
    No error message in attachement . only it daisplay the following information
    SAP Library
    SAP Library contains the complete documentation for SAP NetWeaver Application Server Java. You can access it by choosing SAP NetWeaver.
          SAP NetWeaver Administrator
    A powerful administration, configuration and monitoring tool, which bundles key administrative tasks to keep your SAP NetWeaver system landscape running. SAP NetWeaver Administrator can be used in a central or local scenario. Here you access the local NetWeaver Administrator.
        System Information
    System information provides administrators with an overview of the system configuration and its state. It shows all of the system's instances and processes, their current state and important parameters (such as ports) that may be required for support cases, as well as the versions of the components installed.
          Services Registry
    The Services Registry is a UDDI based registry that contains definitions of enterprise services and references to their metadata.
       User Management
    The user management administration console provides administrators with the functions they need to manage users, groups, roles, and user-related data in the User Management Engine (UME). Users without administrator permissions can use it to change their user profile.
          UDDI Client
    The UDDI client provides query and publishing functions for UDDI entities to any UDDI compliant registry.
       Web Services Navigator
    Web Services Navigator is a tool that gives you a short overview of a specific Web service based on its WSDL, and enables you to test your Web service by creating and sending a client request to the real end point.
          Web Dynpro
    Web Dynpro is a User Interface technology available within the SAP NetWeaver Developer Studio.
    Various Web Dynpro tools provide administrators and application developers with performance measurement and application administration capabilities. The Web Dynpro runtime is already deployed.  
    Regards
    Upendra

  • HTTP Status Code 200 Received But Error During Response Parsing

    Hi Experts,
    We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Adapter  -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    We searched other threads but could not get any solution. Please provide suggestions.
    Thank You.
    Regards,
    Anandan

    the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically  and as a result  , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
    We have done the following activities in order to solve this problem....
    increase the value of  icm/HTTP/max_request_size_KB to 512MB
                                        icm/wp_roll_timeout   to maximum
                                        HTTP TIMEOUT to 1800 sec
                                       icm/wp_roll_timeout   to maximum
                                         mpi/total_size_MB  to maximum
                                       mpi/buffer_size  to maximum
    and then increased the maxthreadcount ,maxcontentlength using config tool...
    and also increased the java heap size to maximum....
    After doing everything ,the file has been successfully processed....
    the problem has been resolved...

Maybe you are looking for