OK_BUT_NO_XI_MESSAGE

All,
i am working on the interface File to Proxy(SRM),
when executing the scenario, i am getting the below error in call adapter.
<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>
can any one help me out to solve this issue.
Thank You,
Madhav

i got same issue with you
i solved.
T_code(SMICM) -> Administrator -> ICM ->  Maintance Mode -> Deactive

Similar Messages

  • 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