CLIENT_RECEIVE_FAILED error

Hi Friends,
Please help me to resolve this issue which I am getting in production server:
<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="" />
As I checked the message size, it showing 25716041. And as per the log also we are getting out of memory error.
Please provide help.
Regards,
Nutan

HI Nutan,
By default processed message size PI is 100MB.
First you check the size of the mesages in the parameter (icm/HTTP/max_request_size_KB) in Tcode RZ11, you will get the message size details 100 MB, So you have to increase the parameter from Tcode RZ10 icm/HTTP/max_request_size_KB = 3072 MB.After that Save the instance and restart your server message will processed succfully.
Regards,
Ramesh

Similar Messages

CLIENT_RECEIVE_FAILED Error in Client Java Proxy

Hi. All..
Do you experience CLIENT_RECEIVE_FAILED Error ?
This pattern is java proxy -> xi -> abap proxy.
It's occurring in xi server ( QAS ) . ( I guess that is internal error. )
I did refresh CPACache. but I don't solve.
This interface is very good execution in DEV.
but has occured CLIENT_RECEIVE_FAILED Error in QAS.
What's wrong?
Error message following....
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler beim Empfangen per HTTP (Fehlercode: 110, Fehlertext: )</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>

U may do the following
1. Check in SMICM if your HTTP service is running.
2. Upgrade the ICM kernel patch.
3. For SP15 there is a list of corrections -have a look into this SAP note-897583
Regards,
Prateek

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

Error CLIENT_RECEIVE_FAILED Error while receiving by HTTP

Hi,
I am working on a XML to flat file scenario where I am using MULTI Mapping to get multiple outputfiles.but in SXMb_MONI I am getting this below error. and mesages are stuck in SMQ2.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<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>
what might be the cause for the error and do i need to enable any TUNING parameteres in IE specific config ?
I have gone through different que blogs,but cant find the right one.
thank you,
babu

Babu,
the error has occured in the last pipeline step - Call adapter... Looks like the message size is too large (happens sometimes with multimapping)...Try increasing the max request size parameter.
Please go through Micheal's Post - >
Re: Error-Code: 108 - CLIENT_RECEIVE_FAILED
Also go through the tuning guide...
regards,
Arvind R

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

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

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

Error ID:CLIENT_RECEIVE_FAILED in ABAP PROXI

Hi All,
I am working on File to ABAP Proxy scenario.
I am getting following error in SXMB_MONI when i tried to post some message.
Error ID:CLIENT_RECEIVE_FAILED
Error Category: INTERNAL
error trace as follows:
<SAP:Category>XIServer</SAP:Category>
<SAP:Codearea="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code><SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
Error    : -20
Version : 6040
Component: ICM
Date/Time: Mon Dec 12 18:25:55 2005
Module   : icxxconn.c
Line     : 2118
Server   : XIDSVR_XID_35
Detail   : Connection request from (19/3994/0) to host: http://xidsvr, service: 8035 failed (NIEHOST_UNKNOWN) AP-T19, U3994, 135 XIAFUSER, , 18:25:55, M0, W0, , 1/0
<b>Can any one guide me what is the error & what is solution????</b>
My Receiver communication channel configuration is as follows:-
Address Type   : URL Address
Host ID        : http://xidsvr
Service Number : 8035
Path           : /sap/xi/engine?type=entry
<b>Is my Xi adapter above configuration is not correct?</b>
Please guide my.......

Hi Umesh,
>>- we need to import software component in R/3.
no, you do not need to import SWCs in R/3
>>- register queues in sxmb_adm in R/3.
yes, that is necessary
>>- HTTP destination on R/3(on which proxy is
developed) pointing to XI system.
yes, that is necessary
>>- configure your R/3 to act as IE using SXMB_ADM
transaction
the right entry is LOC - application system and then the URL of your XI system beneath.
>>- values that should be in the R/3 table SPROXSET
IFR_ADDRESS host:8035/rep
IFR_PASSWORD XIPASS
IFR_USER XIAPPLUSER
depend on your sys environment, but yes, necessary
>>- After all above Test
SPROXY -> Go To -> Connection Test
yes...
additionally you have to configure SLD connection from R/3 to the SLD used by your XI system.
Have you checked this config guide https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/52a10ae0-0701-0010-4cb5-d8cd85593731 chapter 8 "Connecting Business Systems with an Integration Engine to the Central Integration Server" this lists in detail the steps to set up an R/3 system to use proxy communication with XI.
best regards
Christine

Error after schudling report for triggring proxy

Hi friends,
In the scnario proxy-jdbc.. i have moved the interface to production and schudled the abap report in background jobs.
now when the report is triggered the proxy is called and here i am getting this error.
INTERNAL.CLIENT_RECEIVE_FAILED Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)
and same report works when i execute manually. and even few days in background also it works..
it seems to be strange.. i need to know the reson is it with network problem.. or any issue..
but report is schuled and sucefuly completing in R/3 side. if we see the status of the job..
Regards
Vijay

Hi Vijay,
I have also Proxy-JDBC syncronous scenario.
Program is running in the Background and it is wroking fine but on few days it is givning the following error.
Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Error (id=INTERNAL.CLIENT_RECEIVE_FAILED): Error while receiving by HTTP (error
    code: 402, error text: ICM_HTTP_TIMEOUT)
Here situation is same as you have mentioned in your case. (getting error sometimes)
So please tell me the how did u solve it??
Thanks & Regards,
Jagesh

ICM_HTTP_INTERNAL_ERROR

Hello,
i send idoc with the jdbc adapter in one Database.
when i send only one or 5 of them to the same time everthing is fine.
But when i send maybe more than 5 at the same time i got following error at a few of the messages:
Error when receiving by HTTP (error code: 405, error text: ICM_HTTP_INTERNAL_ERROR
CLIENT_RECEIVE_FAILED
Error: -1
Version: 6040
Component: ICM
Date/Time: Thu Oct 27 15:08:34 2005
Module: icxxthrio_mt.c
Line: 1716
Server: *********
Detail: IcmHandleNetWrite(id=10/1998): No data from server received (rc = -1)
is there any parameter to set?
we have WAS 6.40 SP 13.
Regards,
Robin

Robin,
I do not think there are any parameters to set. I guess you need to apply SP14, usually that is the SAP answer. If you do not want to upgrade it to SP14, the only way is to open an OSS Note.
Regards
Shravan

J2ee not restarted.

Hello Guys,
I tried to restart the J2ee engine using
smicm---Administration--Java instance-Softshutdown --- with restart.
I received an error notification to our mailbox as this :
SAPOPC: IEngine_XIP_100 Integration Server: Error code: CLIENT_RECEIVE_FAILED error text: Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED). SAP System:XIP, Instance:32, host:sapxipu, client:100, date:2008/03/08, time:09.41.05.
The J2ee machine is still down. It is not restarted. can you please help.

There must be some error in std_server0.out file in the <j2ee instance>\work directory. Could you please paste the error/exception here.
Thanks,
Snehal

Error"XI Error CLIENT_RECEIVE_FAILED.INTERNAL: Queue sto" in SMQ2

Hi,
When i am trying to test my JDBC to ABAP Server proxy i am getting the error(XI Error CLIENT_RECEIVE_FAILED.INTERNAL: Queue sto) in SMQ2 please advice me what could be the problem?
Regards,
Bhoj

Hello better you apply LUW on each and every message in SMQ, queues. Else activate and inactivate the messages in the queue by sxmb_adm -> managequeues -> deregisterqueues -> registerqueues -> activate queue.
And also do if any messages are failed follow the blog to resend the failed messages,
XI : How to Re-Process failed XI Messages Automatically

Error 110 : INTERNAL" CLIENT_RECEIVE_FAILED

Dear All,
I am working on Java server proxy, In my scenario i am picking a file from sender File Adapter and in Receiver side i am using java proxy (Inbound). But in SXMB_MONI , it give me the Error and Error no is :110
See the Detailed Error in Call Adapter.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<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>
Please help me how to resolve this Issue.
Regards
Lateef

Dear Michelle,
In Receiver Channel we are Assiging the XI user Id and Password.
Check your XI User ID in XI system with T_Code "SU01" Go to Display Button and it will open the screen there you will find one Tab "Role" and Assign this role "SAP_XI_APPL_SERV_USER" to that user id whatever you are using in receiver channel.
If you are not able to assign tell basis person he can assign it tell him it should be "XIAPPLUSER" with the above role which i have mentioned.Hope you problem will be resolved, i did the same .
If useful give points.
Regards
Lateef

Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED

Hi experts,
I have a big issue in production server,
the Queues are stuking in smq2 " command to tRFC/qRFC: execute LUW again"
if i am reprocess or press F6 it is going manually.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://xidist:8000/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP NetWeaver Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://xidist:8000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://xidist:8000/sap/public/icman/img/graybar_tile.jpg" height="31"> </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2><b>404 Resource not found</b></H2><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed May 14 15:50:24 2014 </td></tr> <tr><td>Module:</td><td>icxxconn.c</td></tr> <tr><td>Line:</td><td>2341</td></tr> <tr><td>Server:</td><td>xidist_GXI_00</td></tr> <tr><td>Error Tag:</td><td>{004654a1}</td></tr> <tr><td>Detail:</td><td>Connection request from (110/28816/0) to host: xidist, service: 50000 failed (NIESERV_USED) EX-T110, U28816, 001 PIAFUSER, 10.1.57.50, 15:50:24, M0, W1, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Regards,
Kiran polani

Dear Sriram Ramani,
in ths case some scenarios are working good. proxy to soap, idoc to soap and jdbc to proxy, proxy to jdbc all are working with out error.
but my problem is in Soap to RFC case..
for all RFC communication channels are working but some time it is throwing RFC_COMMUNICATION_ERROR and messages are stucks in smq2 with retry.
when i check with retry error with in sxmb_moni log showing ICM_HTTP_CONNECTION_FAILED with error code 400.
not for all signals for few signals for some time..
Why it is happening i can't understand.
in repository it is saying Repsitory object hmi failed and address already in use.
is there any problem with loading IR objects.
Please suggest me good suggestion for this type of issue what can do for this to resolve.
Regards,
Kiran Polani

CLIENT_RECEIVE_FAILED error

Similar Messages

Maybe you are looking for