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" ?>
- <!--  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>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/">&copy; 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

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

  • File-Proxy (Error while receiving by HTTP )

    Hi All,
    I have a problem in the scenario file to Proxy....which is that after placing a source file successfuly in the source directory.... it is showing an information message in the XML message monitoring(sxmb_moni) like below
    Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)
    Could anybody  explain the problem please????where i need to configure to reslove this.
    Thanks.
    Respond me Imme pls.

    First thing to check is that the adapter_plain service is activated in the transaction SICF. (path: default_host-> sap -> xi -> adapter_plain
    Then check that the http service is running properly (transaction SMICM).
    Also, unless you are connecting to an SAP webAS, you should give a username and password, rather than "Use Logon data fotr SAP System". You could also maintain the URL and authentication data as an sm59 destination and use that in the adapter.
    Please look at these...
    INTEGRATION_DIRECTORY_HMI: Connection fails
    ICM_HTTP_CONNECTION_FAILED
    SAF - ICM_HTTP_CONNECTION_FAILED
    HTTP adapter setup
    Check out this SAP Note- 824554
    Also this links
    ICM_HTTP_CONNECTION_FAILED
    Cache Refresh~
    https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
    ICM_HTTP_CONNECTION_FAILED ERROR
    error code: 400, error text: ICM_HTTP_CONNECTION_FAILED
    Error With ABAP Client proxy
    Message not reaching Integration server
    HTTP content sever - error?
    Error in content server configuration
    HTTP Client : Code 110 reason
    RFC: INTEGRATION_DIRECTORY_HMI
    Content server config - error?
    Thanks
    Swarup

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

  • Error while run OAF, HTTP 500 - Internal server error  Internet Explorer

    I have installed R12 on my laptop having windows 2003 Server, which running successfully.
    In Same machine i have installed Jdeveloper for OAF customization by following 416708.1.
    While running test OAF page from Jdev, following error accruing. I have Run autoconfig as well.
    There is a problem with the page you are trying to reach and it cannot be displayed.
    Please try the following:
    Open the r12.oracle.com:8988 home page, and then look for links to the information you want.
    Click the Refresh button, or try again later.
    Click Search to look for information on the Internet.
    You can also see a list of related sites.
    HTTP 500 - Internal server error
    Internet Explorer

    What is the JDev version?
    Check if the below fixes the issue.
    Go to Tools -> Embedded OC4J Server Preferences-> Global -> Startup. Select the option -> Default Local IP Address.
    Thanks
    Shree

  • 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

  • Received HTTP response code 500 : Error during conversion of XI message

    hi
    Facing the error , "Received HTTP response code 500 : Error during conversion of XI message"
    This is the fist time i am configuring the sender soap ( Axis Framework in the SOAP Adapter) (Quality of service Best effort) communication channel and i am getting the above error did any body face this error.
    01.09.2011 12:02:32     Information     The message status was set to DLNG.
    01.09.2011 12:02:32     Error     SOAPFault received from Integration Server. ErrorCode/Category: XIServer/ATTRIBUTE_INITIAL; Params: Manifest cid:6D90482BF678436D75928FC8B9930519; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Attribute Manifest cid:6D90482BF678436D75928FC8B9930519 is initial
    01.09.2011 12:02:32     Error     Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during conversion of XI message.
    regards
    sandeep
    Edited by: pendyalas on Sep 1, 2011 12:20 PM

    I found a link with respect to similar error , sap note 1522630 has been used to resolve this error.
    i will try and see if it works.
    AXIS Sender Adapter Failure after upgrade to PI 7.11 SP06
    regards
    sandeep

  • Error while creating the HTTP client with destination GB_DPSRetrieve

    Hi All,
    It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
    Please find the error log below and throw some light why the HTTP adapter is getting error -
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
      <SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
      <SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
      <SAP:Service>GGMailbox</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>SAP_DEV_ERP2005</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
      </SAP:Receiver>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</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>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
      <SAP:P1>GB_DPSRetrieve</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
      <SAP:Retry>N</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="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS" />
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <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>20071121</SAP:Date>
      <SAP:Time>155130</SAP:Time>
      <SAP:Host>lbsth-tb1ci</SAP:Host>
      <SAP:SystemId>XIS</SAP:SystemId>
      <SAP:SystemNr>00</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>023</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PISUPER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
      <SAP:QIdInternal />
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID" />
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>0</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>INIT</SAP:InterfaceAction>
      <SAP:RandomNumber>15</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</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">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
      <Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
      <Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
      <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>
    Regards,
    Kishore

    Hi,
    In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
    If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
    Also check if the Target system can be reached from the XI server to validate the configuration parameters.
    Regards,
    S.Santhosh Kumar

  • Error while sending by HTTP

    Bom dia
    Gostaria de saber quais são os motivos que levam uma mensagem síncrona, a retornar o erro: Error while sending by HTTP (error code: 500 , error text: Internal Server Error). Tenho em mente que possa ser por o receiver estar down mas não tenho a certeza, alguém me pode ajudar?
    Obrigado,
    Rúben Catrona

    Bom dia Rúben,
    Por ser uma comunicação síncrona acredito que deva ser externo, porém não dá para afirmar visto que o PI também se comunica internamente por HTTP.
    Dê mais detalhes do que está realizando.
    Você consegue fazer o mesmo teste diretamente no servidor destino (sem PI) através de outra ferramenta?
    Outro teste seria aumentar o log na SMICM para 3, fazer a comunicação síncrona, voltar o nível de trace para 1. E analisar o log da SMICM procurando pela resposta 500.
    Atenciosamente, Fernando Da Ró

  • Error code: 400, error text: ICM_HTTP_CONNECTION_FAILED

    Every now and then we are getting the following error on a synchronous call from XI 3.0.
    Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)
    Usually it is from XI to R/3 (that's where most of our synch calls take place) but occasionally it happen on a synchronous call to a JDBC comm channel.
    It is not just one interface that causes this issue and the same interface will be OK if we re-run it with same data.
    I suspect some system parameter is off, or it's just a bug in XI.  Any one else run into this ?  if so, have you found a fix ?  SAP hasn't been much help for us thus far.
    Thanks in advance for any help.

    Hi Tim,
    Can you check this thread-
    ICM_HTTP_CONNECTION_FAILED
    Also check SAP Note 824554,783515,910649,706563.
    Cache Refresh~
    https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
    Hope this helps,
    Regards,
    Moorthy

  • Apache Error Log mod_security: Access denied with code 400

    Hi
    I am seeing the Access denied with code 400 errors in the apache log's after applying CPU Patch updates below into a Dev/TEST environment
    RDBMS Patches: 9032412 & 9352191 & post steps below:
    @?/rdbms/admin/dbmsaqds.plb
    @?/rdbms/admin/prvtaqds.plb
    @?/rdbms/admin/prvtaqiu.plb
    Java Fix > [ID 1082747.1]
    E-Business Suite Patches & post steps below:
    9323613 & 9506302
    Compiled Forms PLL files using adadmin to solve the known problem below
    ORA-04062: signature of package "APPS.FND_HELP" has been changed
    ORA-04062: KEY-HELP trigger raised unhandled exception ORA-04062.
    the error can be replicated by following the steps below:
    Log in to Oracle Apps E-Business Suite (11.5.10.2) select Report Management Information Responsibility and then transaction reports. (Opens Oracle Discoverer 4i Viewer) > select either Period to date or Year to date and then select any department & and any period (date) and then apply parameters:
    Error message in browser
    This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not be found because of a problem with the address.
    For more information about HTTP errors, see Help.
    Apache log shows:
    error_log shows the following:
    [Fri Jul  8 10:52:08 2011] [error] [client 10.180.225.5] mod_security: Access denied with code 400. Pattern match "!^([[email protected]|#!=A-Za-z0-9/ :.$/(/)]){0,255}([[email protected]|#!=A-Za-z0-9/ :.$]){0,255}$" at ARGS_NAMES. [hostname "loadbalancer.webdomain"] [uri "/discoverer4i/viewer"] [unique_id ThbTSAq0BRQAABrfK7M]
    access_log shows the following:
    IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/shadow_bottom02_leading_ltr.gif HTTP/1.1" 200 861 0
    IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/seperator.gif HTTP/1.1" 200 42 0
    IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/arch_blue_bottom_ltr.gif HTTP/1.1" 200 984 0
    10.180.225.5 - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/white.gif HTTP/1.1" 200 37 0
    IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/bar_blue_leading_edge_middle_ltr.gif HTTP/1.1" 200 111 0
    IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/bar_blue_trailing_edge_middle_ltr.gif HTTP/1.1" 200 129 0
    IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/shadow_bottom_leading_edge_ltr.gif HTTP/1.1" 200 862 0
    IP ADDRESS - - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/btopshadow.gif HTTP/1.1" 200 44 0
    IP ADDRESS- - [08/Jul/2011:10:51:39 +0100] "GET /disco4iv/html/images/bshadow.gif HTTP/1.1" 200 59 0
    IP ADDRESS - - [08/Jul/2011:10:52:08 +0100] "POST /discoverer4i/viewer HTTP/1.1" 400 227 0
    I have tried to follow a number of metalink notes but unable to resolve this issue, metalink notes looked at are:
    976473.1
    389558.1
    1313128.1 Patch 10324904 applied
    394587.1
    389558.1 Patch 5107107 applied
    1143882.1
    376992.1 Patch 3950067 applied
    Any ideas or suggestions most welcome
    Thank you
    Regards
    Arfan
    Edited by: user1717313 on 08-Jul-2011 04:59

    Hi JD
    I have tried the steps i.e stop apps tier, run adconfig on apps tiers and then started services on apps tiers and can replicate the error
    thanks
    Arfan
    Hi Helios
    I checked note 1080465.1 Patch 9506302 has been applied & Recompile all Forms PLL files using adadmin.
    I ran the sql feom the note, output below
    SQL> select text from dba_source where name='FND_HELP' and line <3;
    TEXT
    package Fnd_Help AUTHID CURRENT_USER as
    /* $Header: AFMLHLPS.pls 115.22 2009/10/12 12:56:58 nchiring ship $ */
    package body FND_HELP as
    /* $Header: AFMLHLPB.pls 115.115 2010/03/19 06:45:24 nchiring ship $ */
    Thanks
    Arfan
    Edited by: user1717313 on 08-Jul-2011 05:04

  • Error while receiving Item using MB1C.

    I get the following error message while receiving Item using T-Code MB1C.
    Accounting Data not yet maintained for Material NPPL 2707.
    Not sure which setup is missing. Can somebody please help?

    Dear Nitesh Patil,
    After we do a posting, the changes need to be reflected in FI and since your material master does not contain the accounting 1 and accounting 2 views you are getting this problem.
    To rectify, go to MM01 > give the same material name for which you are getting this problem > select accounting 1 and 2 views and fill up the required data.
    Hope this helps.
    Thanks
    Murtuza

  • Error while creating the HTTP client with destination

    Hi ,
    I am getting this error while connecting to https location on receiver channel . The below error i am getting in SXMB_moni
    Error while creating the HTTP client with destination
    The receiver party is doing some security setting on there end and for that purpose we have provided the external IP address to them , after that we are getting the above error.
    We have already installed the client certificate on our staging server , and have done the correct setting in SM59 and channel.

    Check few things..
    1) I believe you use specify destination for the addressing type field in the comm channel. If so make sure you entered valid target URL address in the SM59 of type http destination.
    2) Check the validitity of the certificate. You can import the certificate both in java and abap stack.
    3) Make sure certificate is installed as expected.
    4) Send the request and talk to the target system and check what error information they get in their log related to ssl.

  • HTTP response code 500 : Error during Sender Agreement Determination

    I am trying a simple file to file scenario and messages are not being received in Integration Server.
    Through communication channel monitoring, i have received the below error message.
    Error Transmitting the message to
    endpoint http://<hostname>:50000/sap/xi/engine?type=entry using
    connection File_http://sap.com/xi/XI/System failed, due
    to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException:
    Received HTTP response code 500 : Error during Sender
    Agreement Determination.
    Can you please help
    Regards
    Harish

    Hi Harish,
    http://<hostname>:50000/sap/xi/engine?type=entry
    it should be http://<hostname>:8000/sap/xi/engine?type=entry not 50000 as port It should be your HTTP port...please .make the changes !!
    In SXMB_ADM transaction under Integration engine configuration please change the settings to http://<hostname>:8000/sap/xi/engine?type=entry
    make sure with your basis team that ur http port is 8000 or 8001 ..as per that make the necessary changes..
    Regards,

Maybe you are looking for