INTERNAL.CLIENT_RECEIVE_FAILED error : code 110

Hi all,
I have configured a synchronous proxy to RFC scenario.
The problem is that the scenario works perfectly fine and I get the reponse back only sometimes. Other times I get the following error
<SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
  <SAP:P1>110</SAP:P1>
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )
I have noted that once I execute the report (in which I call the proxy) and get back the response, I have to wait for a long time before I execute the report again next time and get a response back. I am not able to run the report in quick succession without getting an error. Please help.
Thanks and regards,
Shweta

Hi,
Refer the following thread
XI Error CLIENT_RECEIVE_FAILED.INTERNAL
Regards,
Jayasimha jangam

Similar Messages

  • Error while receiving by HTTP (error code: 110)  ?

    Hi Experts,
    I am working on IDOC to file Scenario.
    I am getting this error in SXMB_MONI. What may be the reason.
    <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">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Best Regards,
    Anil

    Check these threaads:
    Re: XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
    Regards,
    ravi

  • Getting the error: Error while receiving by HTTP error code: 110

    Hi,
    I have developed an interface which actually gets data from SCM system and in BPM to gets additional data from R/3. There are five synchronous call to this R/3 to get different sets of data. I am using only one communciation channle from BPM to R/3. The interface works perfectly OK in the development system. When the interface is migrated to the test system I found that the four calls work perfectly fine while the last call error out as below and the J2ee server goes down:
    <?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="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Any input/help will be appreciated. I have tried increasing timeout/connection alive time but still not get resolved.
    Thanks in advance,
    Sushma

    Hi Prateek,
    Thanks. But this note I have checked before and this seems not related. I actually found out the system logs in SM21 and saw the "Operating system call recv failed (error no. 10054)". What I did then is I seach notes related to this error and found a numebr of SAP notes. And I have informed the Basis guys to look into the notes and the system logs. They are working on this and they are deleting the old messages which have errored out. They are suspecting the system memory or too many old messages would have caused this issue.
    If you have any knowledge of why this error would have occurred please let me know.
    Thanks,
    Sushma

  • Error code: 110, error text

    Hi all,
    While working with Soap Adapter and when the pay load is more 2.7MB i am getting the below error.
      <?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">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    The above error is raised only when the payload is moe ,if I send 1mb payload its working fine.
    Any inputs would be helpful.
    Thanks,
    Srinivasa

    Hi ...
    Check out this part of the following blog : /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
          Hi,
          what about the http response code 110.
          I get lot of errors in SAP Exchange Infrastructure in SXI_MONITOR:
          - <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
          <SAP:P1>110</SAP:P1>
          <SAP:P2 />
          <SAP:P3 />
          <SAP:P4 />
          <SAP:AdditionalText />
          <SAP:ApplicationFaultMessage namespace="" />
          <SAP:Stack>Error when receiving by HTTP (error code: 110, error text: )</SAP:Stack>
          <SAP:Retry>N</SAP:Retry>
          </SAP:Error>
          Any idea?
          With kind regards.
          Martin Steinberg
          SXI_CACHE
          2007-10-11 13:45:49 Marco Salazar SAP Employee Business Card [Reply]
          to solve this try in the INTEGRATION_DIRECTORY_HMI destination put in the path field /dir/hmi_cache_refresh_service/ext
          Query
    Thanks,
    Pooja Pandey

  • INTERNAL.CLIENT_RECEIVE_FAILED Error when receiving by HTTP

    Hello my name is Arkaitz.
    I have this error *"INTERNAL.CLIENT_RECEIVE_FAILED Error when receiving by HTTP (error code: 110, error text: )"*
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Integration Server
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>DD351E48-7EED-DA5D-E100-0000AC1D4E74</SAP:MessageId>
      <SAP:RefToMessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:RefToMessageId>
      <SAP:TimeSent>2008-05-05T15:59:00Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>ECYR</SAP:Service>
      <SAP:Interface namespace="" />
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>BSBWC_35</SAP:Service>
      <SAP:Interface namespace="http://www.ecyr.report.bw.sql">MI_1</SAP:Interface>
      <SAP:Mapping />
      </SAP:Receiver>
      <SAP:Interface namespace="http://www.ecyr.report.bw.sql">MI_2</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error when receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2008-05-05T15:59:00Z" wasRead="false">
      <SAP:Engine type="BS">BSBWC_35</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2008-05-05T16:02:50Z" wasRead="false">
      <SAP:Engine type="IS">is.00.EMSXIL601PRE</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20080505</SAP:Date>
      <SAP:Time>175900</SAP:Time>
      <SAP:Host>emmbwl501pre</SAP:Host>
      <SAP:SystemId>BWC</SAP:SystemId>
      <SAP:SystemNr>22</SAP:SystemNr>
      <SAP:OS>Linux</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>023</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>ES78914719V</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_SENDER</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>SENDER</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>FEC5B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineService>PLSRV_CALL_INTEGRATION_SERVER</SAP:PipelineService>
      <SAP:QIdInternal />
      <SAP:CommitActor>A</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="420">SND_CENTR</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID" />
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>198</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>198</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>INIT</SAP:InterfaceAction>
      <SAP:RandomNumber>52</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="emmbwl501pre">20080505155900.452389</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="emmbwl501pre">20080505155900.454147</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
      <SAP:Timestamp type="begin" host="emmbwl501pre">20080505155900.454636</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
      <SAP:Timestamp type="end" host="emmbwl501pre">20080505155901.884062</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = BWC</Trace>
      <Trace level="1" type="T">client = 420</Trace>
      <Trace level="1" type="T">language = S</Trace>
      <Trace level="1" type="T">user = ES78914719V</Trace>
      <Trace level="1" type="Timestamp">2008-05-05T15:59:00Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 4E111D481C55742CE10000000AD2202B</Trace>
      <Trace level="1" type="T">PLNAME = SENDER</Trace>
      <Trace level="1" type="T">QOS = BE</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline SENDER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="1" type="T">URL for integration server read from global configuration</Trace>
      <Trace level="1" type="T">URL= Dest://SAPISU_XII</Trace>
      <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
      <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
      </SOAP:Body>
      </SOAP:Envelope>
    Can you help me?
    thank

    Hi,
    I think it is the problem with your HTTP connection used by ABAP proxy. so when your PI system tries to connect to ECC using HTTP it fails to connect.
    Regards,
    Indranil
    Award points if applicable

  • Proxy to File - CLIENT_RECEIVE_FAILED - error code: 200, error text:

    I have configured a Proxy to JDBC scenario from a new ECC dev system and it works great.  I recently tried migrating the changes to the new ECC qas environment and I get the following error message.  Can anyone help, I must have missed some configuration somewhere?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Integration Server
      -->
    - <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">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>200</SAP:P1>
      <SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><html> <head> <title>SAP J2EE Engine Start Page</title> </head> <frameset framespacing="0" border="0" rows="90,*" frameborder="0"> <frame name="banner" scrolling="no" noresize target="contents" src="top.html" marginwidth="0" marginheight="0"> <frame name="main" src="main.html" marginwidth="10" marginheight="30" scrolling="auto"> <noframes> <body> <p>This page uses frames, but your browser doesn't support them.</p> </body> </noframes> </frameset> </html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>

    Hi!
    I think what michal told is correct there is a connectivity issue but please make sure regarding mapping also why it is unable to receive the response...
    Actually ERROR 200 code means::
    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..
    I know this is not an exact answet but this ill give u some idea..
    Regards::
    Amar Srinivas Eli

  • Receiver proxy error - CLIENT_RECEIVE_FAILED error code 200

    Hi,
    Scenario: JDBC to Proxy.
    I am getting an error on the receiver side - below is the error.
    <?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">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>200</SAP:P1>
      <SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>--SAP_4732F0E6BA080C67E1000000A859B621_END content-type:text/xml content-length:4118 content-id:<[email protected]> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>asynchronous</SAP:ProcessingMode><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:TimeSent>2007-11-08T10:33:00Z</SAP:TimeSent><SAP:Sender><SAP:Service>BS_ESS</SAP:Service></SAP:Sender><SAP:Receiver><SAP:Party agency="" scheme=""/><SAP:Service>CD103</SAP:Service></SAP:Receiver><SAP:Interface namespace="http://www.Coj.co.za/EssToSapIsu/Ess">MI_EssToSapIsu_EssMiForSapIsu</SAP:Interface></SAP:Main> <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService></SAP:ReliableMessaging> <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2007-11-08T10:33:00Z" wasRead="false"><SAP:Engine type="AE">af.cxd.jssxid0</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2007-11-08T10:33:00Z" wasRead="false"><SAP:Engine type="IS">is.00.jssxid0</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList> <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Information</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic> <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1"><SAP:From><SAP:Name></SAP:Name><SAP:Interface namespace=""></SAP:Interface></SAP:From><SAP:MessageId>00000000-0000-0000-0000-000000000000</SAP:MessageId><SAP:QualityOfService></SAP:QualityOfService><SAP:TimeSent></SAP:TimeSent><SAP:Direction>Request</SAP:Direction><SAP:Document></SAP:Document></SAP:MessageHeader> <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:Context></SAP:Context><SAP:Code p1="" p2="" p3="" p4="">CALLER.MSG_GUID_NOT_QUALIFIED</SAP:Code><SAP:Text language="EN">Attribute message GUID not specified</SAP:Text></SAP:ErrorHeader> <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0"><SAP:Hop SystemName="CD103" Type="SENDER" TimeStamp="2007-11-08T11:00:57Z" WasRead="0"><SAP:MessageInbound><SAP:Type>AENGINE</SAP:Type></SAP:MessageInbound><SAP:MessageOutbound><SAP:Type></SAP:Type></SAP:MessageOutbound></SAP:Hop></SAP:HopList> <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound></SAP:InternalAttributesHeader> </SOAP:Header> <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:[email protected]"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest> <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0"> <SAP:Payload xlink:href="cid:[email protected]"> <SAP:Document>TraceDocument</SAP:Document> </SAP:Payload> </SAP:Manifest> </SOAP:Body> </SOAP:Envelope> --SAP_4732F0E6BA080C67E1000000A859B621_END content-type:application/xml content-length:417 content-id:[email protected] <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_EssToSapIsu_EssMtForSapIsu xmlns:ns0="http://www.Coj.co.za/EssToSapIsu/Ess"><TABLE1><BSTKD>A0707120330</BSTKD><BSTDK>12-07-2007 </BSTDK><ZE01>15:33</ZE01><ZE04>JANICE</ZE04><ZE05>DS3</ZE05><ZE06>RIVERLEA</ZE06><ZE02>,957 A KOMANI,RIVERLEA</ZE02><MATNR>A</MATNR><ZE03></ZE03><AUGRU>Medical - General</AUGRU></TABLE1></ns0:MT_EssToSapIsu_EssMtForSapIsu> --SAP_4732F0E6BA080C67E1000000A859B621_END content-type:text/plain content-length:1717 content-id:[email protected] <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace> <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace> <Trace level="1" type="T">**************************************************** </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">XMB entry processing </Trace> <Trace level="1" type="T">system-ID = CD1</Trace> <Trace level="1" type="T">client = 103</Trace> <Trace level="1" type="T">language = E</Trace> <Trace level="1" type="T">user = MOLAIM</Trace> <Trace level="1" type="Timestamp">2007-11-08T11:00:57Z </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">**************************************************** </Trace> <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="T">Message-GUID = 00000000000000000000000000000000</Trace> <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="System_Error">Exit XMB because of system error!</Trace> <Trace level="1" type="System_Error">System-Error: CALLER.MSG_GUID_NOT_QUALIFIED</Trace> <Trace level="1" type="System_Error">Attribute message GUID not specified </Trace> <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace> <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace> </SAP:TraceHeader> SAP_4732F0E6BA080C67E1000000A859B621_END</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Thanks,
    Leanne

    Are u trying a synch scenario? Ur server proxy must be receiving the data properly. If it is a sync scenario then u should check the response mapping again in sxmb_moni.
    Regards,
    Prateek

  • HT201372 used this to make a bootable copy for a new hard drive installation. copied the install find but gave error code 110 when making the disk bootable.. Any help in what this code is

    Used createinstallmedis to make a copy of the Mavericks app for use in a new hard drive install.. Copied find but gave error code 110 and failed to make the flash drive bootable.. Any help in what errror code means?

    Did you partition and format the flash drive first? See the following:
    Make Your Own Mavericks, Mountain/Lion Installer
    After downloading the installer you must first save the Install Mac OS X application. After the installer downloads DO NOT click on the Install button. Go to your Applications folder and make a copy of the installer. Move the copy into your Downloads folder. Now you can click on the Install button. You must do this because the installer deletes itself automatically when it finishes installing.
       2. Get a USB flash drive that is at least 8 GBs. Prep this flash drive as follows:
    Open Disk Utility in your Utilities folder.
    After DU loads select your flash drive (this is the entry with the mfgr.'s ID and size) from the leftside list. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
    Select the volume you just created (this is the sub-entry under the drive entry) from the left side list.
    Click on the Erase tab in the DU main window.
    Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    Click on the Erase button. The format process can take up to an hour depending upon the flash drive size.
    Make your own Mavericks flash drive installer using the Mavericks tool:
    Mavericks has its own built-in installer maker you use via the Terminal:
    You will need a freshly partitioned and formatted USB flash drive with at least 8GBs. Leave the name of the flash drive at the system default, "Untitled." Do not change this name. Open the Terminal in the Utilities folder. Copy this command line after the prompt in the Terminal's window:
    sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction
    Press RETURN. Enter your admin password when prompted. It will not be echoed to the screen so be careful to enter it correctly. Press RETURN, again.
    Wait for the process to complete which will take quite some time.

  • Heart beat could not open connection, error code 110

    Hi, where can I find error codes for NFR and NSM?
    I have problems with some agents connecting to the engine:
    2/17/2010 16:02:55 EngineInterface: Heart beat could not open connection, error code 110
    Both engine and agent runs on the same server (10.236.19.147):
    AgentNCP Service Config
    Host Address: 10.236.19.147
    Service Ports: HTTPS: 3037 HTTP: 0
    Data Path: /var/opt/novell/filereporter/agentncp
    Debug Logging: Enabled
    Heartbeat: 60 seconds
    Engine Address: 10.239.19.147:3035
    Use SSL: Yes
    Alternate Hostname: huanovellfs1
    Engine Service Config
    Host Address: 10.236.19.147
    Service Ports
    Client HTTPS: 3033 HTTP: 0
    Agent HTTPS: 3035 HTTP: 0
    Data Path: /var/opt/novell/filereporter/engine
    Debug Logging: Enabled
    Heartbeat: 60 seconds
    DSI Address: 10.236.19.89:8009
    Use SSL: Yes
    Scans per Volume: 2
    Another OES2 server connects fine to the engine, butI have a Netware agent, which also fails to connect:
    Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open connection.
    NFR is 1.0.0
    Thanks for any input.
    Istvan

    Hi Istvan! Sorry for the delay in our response! we are in the process
    of building a list of error codes for everyone! in the meantime the 110
    means the following:
    // Couldn't create a new network interface
    #define CC_STATUS_CCS_CANT_CREATE 110
    Is this an NSM integration installation?
    Also, remove the alternate hostname.
    If you don't mind, let's move this support issue to
    filereporter"@"novell.com!
    Thank you!
    icseke wrote:
    > Hi, where can I find error codes for NFR and NSM?
    >
    > I have problems with some agents connecting to the engine:
    >
    > 2/17/2010 16:02:55 EngineInterface: Heart beat could not open
    > connection, error code 110
    >
    > Both engine and agent runs on the same server (10.236.19.147):
    >
    >
    > AgentNCP Service Config
    > ------------------------------------------------------------------------------
    > Host Address: 10.236.19.147
    > Service Ports: HTTPS: 3037 HTTP: 0
    >
    > Data Path: /var/opt/novell/filereporter/agentncp
    > Debug Logging: Enabled
    > Heartbeat: 60 seconds
    > Engine Address: 10.239.19.147:3035
    > Use SSL: Yes
    > Alternate Hostname: huanovellfs1
    >
    > Engine Service Config
    > ------------------------------------------------------------------------------
    > Host Address: 10.236.19.147
    > Service Ports
    > Client HTTPS: 3033 HTTP: 0
    > Agent HTTPS: 3035 HTTP: 0
    >
    > Data Path: /var/opt/novell/filereporter/engine
    > Debug Logging: Enabled
    > Heartbeat: 60 seconds
    > DSI Address: 10.236.19.89:8009
    > Use SSL: Yes
    > Scans per Volume: 2
    >
    > Another OES2 server connects fine to the engine, butI have a Netware
    > agent, which also fails to connect:
    >
    > Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open
    > connection.
    >
    > NFR is 1.0.0
    >
    > Thanks for any input.
    >
    > Istvan
    >
    >

  • HTTP error code: 110

    Hi ALL
    Can any body give me details regarding  what doest this error code indiacte?
    " Error while receiving by HTTP error code: 110"
    any related document or SAP note will be helpfull?
    Thanks in advance
    Sandeep

    Hi Sudhir
    Thanks for the reply. I have already gone through this thread.
    I am not using any HTTP adapter. i am using IDOC adsapter only.
    and this error occured on my production server. So we cant say like the thread you mentioned that this time it need any HTTPS connection configured coz it was working fine already.
    Although this problem was solved by restarting the server.But its not advisable to refresh server on production frequently..also i want to know the complete description of this error ?
    what this error stands for? what is the permannet solution of this?
    Also if there is any supporting document or SAP Note to clarify this , will be highly appreciated/
    any input experts?
    Regards
    Sandeep

  • Internal errorcode Error code 9050 "disk_not_accessible"

    Dear Support,
    When iam starting MaxDB database getting the Internal errorcode, Error code 9050 "disk_not_accessible"
    Same iam copying last few lines of knldiag.err message here
    2011-05-11 15:19:47     0x12EC ERR 20017 Admin     +   RestartFilesystem failed with 'I/O error'
    2011-05-11 15:19:47      0x27C ERR     7 Messages Begin of dump of registered messages
    2011-05-11 15:19:47      0x27C ERR    10 Messages abort dump of registered messages
    2011-05-11 15:19:47      0x27C ERR     8 Messages End of the message list registry dump
    2011-05-11 15:19:48                               ___ Stopping GMT 2011-05-11 09:49:48       
       7.6.06   Build 010-123-229-880
    2011-05-11 15:20:05                               --- Starting GMT 2011-05-11 09:50:05       
       7.6.06   Build 010-123-229-880
    2011-05-11 15:20:09      0xE34 ERR 20066 IOMan    The inplace migration is not possible,
    because the migrate command was not executed in 7.2/7.3
    2011-05-11 15:20:09      0xE34 ERR 20004 Kernel   Bad page - page check algorithm is invalid
    2011-05-11 15:20:09      0xE34 ERR 20026 IOMan    Bad page on data volume 1 blockno 0
    2011-05-11 15:20:11      0xE34 ERR 20004 Kernel   Bad page - page check algorithm is invalid
    2011-05-11 15:20:11      0xE34 ERR 20026 IOMan    Bad page on data volume 1 blockno 0
    2011-05-11 15:20:13      0xE34 ERR 20004 Kernel   Bad page - page check algorithm is invalid
    2011-05-11 15:20:13      0xE34 ERR 20026 IOMan    Bad page on data volume 1 blockno 0
    2011-05-11 15:20:15      0xE34 ERR 20040 IOMan    Cannot read info page from data volume 1
    2011-05-11 15:20:15      0xE34 ERR     3 Admin    Database state: OFFLINE
    2011-05-11 15:20:15      0xE34 ERR     6 KernelCo  +   Internal errorcode, Error code 9050
    "disk_not_accessible"
    2011-05-11 15:20:15      0xE34 ERR 20017 Admin     +   RestartFilesystem failed with 'I/O
    error'
    2011-05-11 15:20:15     0x1390 ERR     7 Messages Begin of dump of registered messages
    2011-05-11 15:20:15     0x1390 ERR    10 Messages abort dump of registered messages
    2011-05-11 15:20:15     0x1390 ERR     8 Messages End of the message list registry dump
    2011-05-11 15:20:16                               ___ Stopping GMT 2011-05-11 09:50:16       
       7.6.06   Build 010-123-229-880
    2011-05-11 15:22:55                               --- Starting GMT 2011-05-11 09:52:55       
       7.6.06   Build 010-123-229-880
    2011-05-11 15:22:58     0x1520 ERR 20066 IOMan    The inplace migration is not possible,
    because the migrate command was not executed in 7.2/7.3
    2011-05-11 15:22:58     0x1520 ERR 20004 Kernel   Bad page - page check algorithm is invalid
    2011-05-11 15:22:58     0x1520 ERR 20026 IOMan    Bad page on data volume 1 blockno 0
    2011-05-11 15:23:01     0x1520 ERR 20004 Kernel   Bad page - page check algorithm is invalid
    2011-05-11 15:23:01     0x1520 ERR 20026 IOMan    Bad page on data volume 1 blockno 0
    2011-05-11 15:23:03     0x1520 ERR 20004 Kernel   Bad page - page check algorithm is invalid
    2011-05-11 15:23:03     0x1520 ERR 20026 IOMan    Bad page on data volume 1 blockno 0
    2011-05-11 15:23:05     0x1520 ERR 20040 IOMan    Cannot read info page from data volume 1
    2011-05-11 15:23:05     0x1520 ERR     3 Admin    Database state: OFFLINE
    2011-05-11 15:23:05     0x1520 ERR     6 KernelCo  +   Internal errorcode, Error code 9050
    "disk_not_accessible"
    2011-05-11 15:23:05     0x1520 ERR 20017 Admin     +   RestartFilesystem failed with 'I/O
    error'
    2011-05-11 15:23:05      0x570 ERR     7 Messages Begin of dump of registered messages
    2011-05-11 15:23:05      0x570 ERR    10 Messages abort dump of registered messages
    2011-05-11 15:23:05      0x570 ERR     8 Messages End of the message list registry dump
    2011-05-11 15:23:06                               ___ Stopping GMT 2011-05-11 09:53:06

    Dear Markus,
    I dont have the old backup, i used application "maxdb-all-win-32bit-i386-7_6_06_10.exe" for upgrade,  So what is the alternate way to resolve this issue.
    This Database is using for DMS Content Server
    Here some logfiles is copying
    Date       Time       TID(hex) Typ MsgID Label    Message-Text
    2010-03-08 10:40:03                               --- Starting ---
    2010-03-08 10:40:07                               --- Starting ---
    2010-03-08 10:55:33                               --- Starting ---
    2010-03-08 19:17:56      0x980 ERR 18431 MESSAGES Could not write to event log, rc = 31
    2010-03-08 19:20:29                               --- Starting ---
    2010-12-12 06:05:41      0xA00 ERR 18431 MESSAGES Could not write to event log, rc = 31
    2010-12-12 14:41:08                               --- Starting ---
    2011-04-01 20:57:36      0x9BC ERR 18431 MESSAGES Could not write to event log, rc = 31
    2011-04-01 20:57:39      0x9C4 ERR 52485 LOG      56move: error occured; 1900
    2011-04-01 20:57:39      0x9C4 ERR 18196 DBCRASH  vabort:Emergency Shutdown, vgg01.c: 2374
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   module file name              |.text start |.text end
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   kernel.exe                    | 0x00400000 | 0x00844000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   liboms.dll                    | 0x10000000 | 0x10048000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   dbghelp.dll                   | 0x6d580000 | 0x6d628000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   WS2HELP.dll                   | 0x71bf0000 | 0x71bf8000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   WS2_32.dll                    | 0x71c00000 | 0x71c17000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   sqltcp.dll                    | 0x76000000 | 0x7600d000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   imagehlp.dll                  | 0x76c10000 | 0x76c38000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   DNSAPI.dll                    | 0x76ed0000 | 0x76efa000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   Secur32.dll                   | 0x76f50000 | 0x76f63000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   rasadhlp.dll                  | 0x76f80000 | 0x76f85000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   USER32.dll                    | 0x77380000 | 0x77411000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   comctl32.dll                  | 0x77420000 | 0x77523000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   ole32.dll                     | 0x77670000 | 0x777a9000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   VERSION.dll                   | 0x77b90000 | 0x77b98000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   msvcrt.dll                    | 0x77ba0000 | 0x77bfa000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   GDI32.dll                     | 0x77c00000 | 0x77c49000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   RPCRT4.dll                    | 0x77c50000 | 0x77cef000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   kernel32.dll                  | 0x77e40000 | 0x77f42000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   ntdll.dll                     | 0x7c800000 | 0x7c8c2000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   SHELL32.dll                   | 0x7c8d0000 | 0x7d0cf000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   SHLWAPI.dll                   | 0x7d180000 | 0x7d1d2000
    2011-04-01 20:57:39      0x9C4 ERR 19999 BTRACE   ADVAPI32.dll                  | 0x7d1e0000 | 0x7d27c000
    Reagards
    Chandra
    Edited by: Chandra B. on May 11, 2011 6:57 PM
    Edited by: Chandra B. on May 11, 2011 6:59 PM

  • HTTP Receiver interface returns with error code 110

    Hi All,
    We are posting the document from XI to a external server as HTTPS request.
    We are able to sucessfully post the request to external server using HTTP destination as address type but not able to post sucessfully with URL as address type.
    Here goes the details -
    We are able to post the HTTPS request successfully on the external server using the HTTP destination as address type in HTTP receiver adapter setup.
    When we setup address type as HTTP destination , we need to provide the following details -
    IN SM59 , Connection type G
    Target Host : host name (  with out "https://"  as prefix)
    Service No : 443
    Path prefix : query string
    SSL : Active
    Certificate : Select the certifacte from the client certificate list.
    We can post the request to external server using URL as address type in HTTP receiver adapter setup.
    When we setup address type as URL , we need to provide the following details -
    Address type : URL Address
    Target Host : host name (  with out "https://"  as prefix)
    Service Number : 443 ( HTTPS port setup on XI)
    Path : query string.
    When we post the same request as we did with HTTP destination as Address type , we are getting a HTTP response code as failure HTTP response code 110
    Please find the details about the return code -
    If a cache returns a stale response, either because of a max-stale directive on a request, or because the cache is configured to override the expiration time of a response, the cache MUST attach a Warning header to the stale response, using Warning 110 (Response is stale).
    110 Response is stale
    MUST be included whenever the returned response is stale.
    Please find the error message from SXMB_MONI
    <?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>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP client code 110 reason</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Please let me know if some one has faced this issue.
    Regards,
    Reddy
    Edited by: Nanda kishore Reddy Narapu Reddy on Mar 11, 2008 12:35 PM

    Hi All,
    Is some one can confirm that - We can use HTTPS with Address type as URL address in HTTP receiver adapter setup.
    I can confirm that using HTTP destination as Address type in HTTP receiver adapter setup we can attain HTTPS communication with external server.
    If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can guide me what are the steps need to be done.
    Address type is a parameter in HTTP adapter setup .
    Regards,
    Reddy

  • Internal kernel error (code 7267)

    Hi,
    while trying to synchronise my Notes Calendar I get the message
    Lotus Notes connector returned a Notes kernel error (code 7267)
    I´m using
    Blackberry Desktop Software6.1.0.36
    Lotus Notes 8.0.2 FP1
    Synchronising details are:
    One way to device
    Transfer only future items is selected.
    Update 1:
    I tried it with 2 days in the past and 2 in the future. It worked. Seems to be there is a calender item in the future he cannot deal with.
    Update 2:
    5 days past and 10 future --> same kernel error
    Update 3:
    Seems to be it was an invitation in the past which I had not declined nor accepted. I accepted the invitation and the next synch the software freezed.
    Update 4:
    Killed the software process and restarted BB Desktop Software. On startup and connection it freezed again while reading notes calendar????

    Hi,
    it could be the sso issue. please ensure
    login/accept_sso2_ticket = 1
    login/create_sso2_ticket = 2
    Restart server after changed and retry.
    Is problem persist, kindly ensure
    1) post upgrade steps are performed
    2) no issue with secstore and strustsso2
    3) update kernel to latest level
    Hope it helps,
    Nicholas Chang

  • Timeout error in ECC "INTERNAL.CLIENT_RECEIVE_FAILED Error while receiving by HTTP (error code: 402 , error text: ICM_HTTP_TIMEOUT)"

    Dear Experts,
    I am very critical situation due to this timeout error in ECC, please help me as much as you can. Go-live date is very near, but I am not getting any clue why this error is occurring. our ECC system is EHP 4, and PI is dual stack 7.4
    My scenario is synchronous ABAP proxy to HTTP_AAE. request is triggering from ECC via proxy and reaching to third party (bank) through PI, I am reviving the response back in PI from bank. But from PI to ECC the response is not reaching. So in ECC after the defined Timeout limit its getting timed out.
    I have tried everything by increasing the timeout in ECC more than 15 minutes in HTTP_TIMEOUT under SXMB_adm in ECC, but nothing worked, even if I am increasing for half an hour then also its getting timeout after half an hour.
    response from bank to PI is coming within 30 to 40 seconds, but PI is not sending the response back to ECC.
    This is classical scenario, and I have checked the trace via SXMB_Moni in PI as well as in ECC, in ECC its showing the timeout error, but in PI i did not see any trace for this error.
    I have read many thread on SCN for the same error, and everywhere it has been suggested to increase the timeout, and I have tired that, it didn't help me.
    All ABAP proxy configuration has been done as follows.
    RFC destinations in ECC
    LCRSAPRFC(TCP/IP)
    SAPSLDAPI ((TCP/IP))
    G type destination to path "/sap/xi/engine?type=entry"
    G type destination SAP_PROXY_ESR to path "/rep"
    All the destination connection test is working fine.
    but i have a doubt on G type destination(AAE_XDJ) to path  "/sap/xi/engine?type=entry" which is returns the status code 500 with message "Empty HTTP request received", is it ok with 500 ?
    Configuration in ECC Integration Engine configuration is as follows
    Questions
    How the message gets pushed to ECC from PI, once the message received in PI, I believe by G type RFC destination on path  "/sap/xi/engine?type=entry" , please clarify.
    How to trace this, if message is not getting pushed to ECC, I mean I have checked the trace in PI XSMB_MONI, but didn't get anything for this error. In ECC SXMB_moni only I am able to the timeout error.
    Please expert help me as soon as you can, this error really effecting me badly in front of management
    Thanks,
    Farhan

    Hi Hareesh,
    I configured the scenario based on ICO, and again I received the same timeout error in ECC.
    I am really sick with this error, and I have raised the OSS message to SAP. Meanwhile I just want to double check my entire configuration with you. Please see the below configuration (for classical) for ABAP proxy to HTTP_AAE, and let me know if anything is wrong.
    Request structure (ECC->PI->Bank)
    <?xml version='1.0' ?>
    <PaymentInfoMessage>
    <PaymentInfoRequest>
    <CompanyCode>Partner01</CompanyCode>
    <BankCode>BSFRSARI</BankCode>
    <StartDate>2006-07-09T00:00:00</StartDate>
    <EndDate>2006-07-09T00:00:00</EndDate>
    <TransactionType>940</TransactionType>
    </PaymentInfoRequest>
    </PaymentInfoMessage>
    Response Structure (Bank->PI->ECC)
    <?xml version="1.0"?>
    <PaymentInfoMessageResponse>
    <PaymentInfoResponse>
        <TransactionType>940</TransactionType>
        <SequenceNum>1</SequenceNum>
        <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
        <ProcessStatus>1</ProcessStatus>
        <Comment>No Comment</Comment>
        <TransactionData>:20:MT940-1007200601
    :25:3210000079901
    :28C:190/0001
    </TransactionData>
        <CompanyCode>PARTNER01</CompanyCode>
    </PaymentInfoResponse>
    <StatusCode>OK</StatusCode>
    <StatusDetail>OK</StatusDetail>
    <ResponseItemCount>2</ResponseItemCount>
    </PaymentInfoMessageResponse>
    ESR Configuration
    Please see the below screenshot for ESR config. I have created 4 data types, 4 message types, 2 Service interface (synchronous), 2 mapping and one operation mapping.
    I just want to clarify about selecting the Request and response message type in inbound and outbound service interface.
    <?xml version='1.0' ?>
    <PaymentInfoMessage>
    <PaymentInfoRequest>
    <CompanyCode>Partner01</CompanyCode>
    <BankCode>BSFRSARI</BankCode>
    <StartDate>2006-07-09T00:00:00</StartDate>
    <EndDate>2006-07-09T00:00:00</EndDate>
    <TransactionType>940</TransactionType>
    </PaymentInfoRequest>
    </PaymentInfoMessage>
    Response Structure (Bank->PI->ECC)
    <?xml version="1.0"?>
    <PaymentInfoMessageResponse>
    <PaymentInfoResponse>
        <TransactionType>940</TransactionType>
        <SequenceNum>1</SequenceNum>
        <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
        <ProcessStatus>1</ProcessStatus>
        <Comment>No Comment</Comment>
        <TransactionData>:20:MT940-1007200601
    :25:3210000079901
    :28C:190/0001
    </TransactionData>
        <CompanyCode>PARTNER01</CompanyCode>
    </PaymentInfoResponse>
    <StatusCode>OK</StatusCode>
    <StatusDetail>OK</StatusDetail>
    <ResponseItemCount>2</ResponseItemCount>
    </PaymentInfoMessageResponse>
    ESR Configuration
    I have simply created 2 data types for requests(ECC->PI->Bank) and did one to one mapping. Similarly for response(Bank->PI->ECC) 2 data types, one to one mapping for this as well.
    But I just want to clarify about selecting the Request and response message type in inbound and outbound service interface. please explain me this for synchronous interface.
    Please see the below structure from ESR and inbound and Outbound service and let me know if the selection of Request and response message types is correct or not.
    OutBound service interface
    Inbound service interface
    Thanks,
    Farhan

  • New intern. drive - error code post/0/2048/s0dimm0/j25lower

    I replaced my broken harddive and loaded the startup disks successfully. Then my lovely wife asked me why I didn't load her new Macbook pro(Leopard) startup disks instead...didn't know it was illegal...however here I am re-loading the G4 disk but get the error above, the extended tests pass, is there anything I can do besides buying another laptop?

    Hi again, mcquitty. You shouldn't even consider spending $500-1000 to repair your Powerbook. Its market value in good working order is well under $1000 and possibly under $500 now, depending on exactly which model you have. So you might be able to replace it with an equivalent used Powerbook in working condition for less than repairing it would cost, and whatever you invest to fix it isn't going to be recoverable on resale if you do repair it. If you want it repaired, have Wegener repair the RAM slot on your existing logic board for $250.
    Test each RAM module in the upper slot, with the lower slot empty, by trying to start up from your Mac OS X 10.3 installer CD or DVD. If you are able to do so, open Disk Utility from the Installer menu and format your hard drive according to Kappy's instructions. Then install Panther. You are now out of the woods with respect to the hard drive problem.
    If you can't start the machine with either RAM module in the upper slot, then retiring the PB may be the best option. For $999 you can buy a brand-new MacBook that will run rings around the PB.

Maybe you are looking for

  • How to print a something in oracle sql developer

    Hello all Do you know How to print a something in oracle sql developer? i mean for example in the query we write something, (offcourse i dont mean comments) thank u in advance. best

  • Wrong aspect ratio on DVD???? Why??

    Hi there friends, ok, I have just spent over an hour waiting for my dvd to encode and burn. I have since found that everything apart from my vision is in 16:9. Why is this?? It is 16:9 vision edited with FCE. I have checked all pref and "switch to 4:

  • IOExecption in palm

    Hi, i have some problems with my application. My program is running in a palm tx with j9 Vm, and it send some information with http post to a php server. All work fine when i have an active wifi connection, but when the palm dont find any wifi connec

  • Error trying to use TreeSet

    I get an odd error when trying to use TreeSet on my computer... even in code that I know compiles on other computers... C:\Program Files\JavaCompiler\Programs\Exam2\Prob03>javac Prob03.java .\Prob03MyClass.java:1: cannot resolve symbol symbol : class

  • HT1226 how to add security key to airport extreme that was set up without? a key?

    How can I add a security to my airport extreme that was set up without one?