Error Transmitting the message to endpoint -Received HTTP response code 401

Hello Experts,
  I am having a SOAP to Proxy scenario. We are using HTTPS without client Authentication.
Everything is running fine and well set on DEV system. After transporting to Test system, i am getting error as :
Error Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.
I get HTTP 200 Ok response in my soap client but the message is not reaching to Integration Engine. It is failing with above error. On CC monitoring for SOAP adapter it shows call completed successfully. But when I use the mesage ID from CC monitoring in Message monitoring i get the error as  shown above in Audit log.
I have checked for Roles attached to my user on DEV and Test systems , I have same roles on both systems.
Any inputs to solve this problem will be very helpful to me. Let me know which service users i need to check for this issue?
Thanks in Advance,
XI Queries.

Hi Pinang,
Thanks for input.
1) Check Role -SAP_XI_APPL_SERV_USER is there in XIAPPLUSER or not.
->Done. Its Ok.
2) check tyour port entry is like J2EE port 5<System no> or not.
->Done. Its Ok.
3) If the error in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
->This note refers in case it happens with high load. I am just sending a small request and no one else is using / testing this interface. So no high load.
4) Check password for user XIISUSER
-> Basis team said they checked for all Xi users and they are not locked.
5) Check password for user XIAFUSER
-> Basis team said they checked for all Xi users and they are not locked.
Any other hints will be helpful.
Kind Regards,
Xi Queries.

Similar Messages

  • 403 Error Transmitting the message to endpoint for XML file to XML file

    Friends,
    This is my 4th day learning XI and getting below issue.
    I'm trying to follow the steps to transfer XML file to XML file scenario and when I drop the sender XML file, it seems the file has been picked-up but it does not generate the output file.
    I checked in RWB for the message and found below error:
    2008-01-04 13:09:48 Error Transmitting the message to endpoint http://sappc:8000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 403
    I tried to access http://sappc:8000/sap/xi/engine?type=entry from new browser window and I get the same error "403".
    I'm able to access http://sappc:8000 fine.
    I would appreciate help on this.
    Thanks in advance.
    Hetal

    Sorry! you were correct I was looking at wrong file adapter. The message is error: (It gives 401 error during XICACHE update)
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Identification
      -->
    - <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="XICACHE">UPDATE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>HTTP status code401 Unauthorized</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>An error occurred when refreshing the XI runtime cache</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • Received HTTP response code 401

    Hi,
    I have scenarion JDBC - XI - RFC. Everything seems to be working till yesterday and suddenly i see an error in the communication channel. In the message monitoring the status is set to waiting and I see nothing in the sxmb_moni. Please see the error below
    Transmitting the message to endpoint http://sapxd1.egd.enbridge.com:8019/sap/xi/engine?type=entry using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.
    Thanks
    Unni

    Immo,
    Go to SLD:
    http://server:port/sld/ListServlet?bsview=true
    Business systems and check if your XI business system has correct "Pipeline URL" parameter defined:
    http://server:httpport/sap/xi/engine?type=entry
    also check TCODE -> SLDCHECK - if you don't have any errors over there
    Gaurav Jain
    Reward Points if answer is helpful

  • Help needed to resolve Received HTTP response code 401 : Unauthorized

    2011-04-08 11:37:48 Error Transmitting the message to endpoint http:---/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized
    while i was executing file to file scenario. the error occoured.
    Edited by: subbuk76 on Apr 8, 2011 8:12 AM

    As the error indicates, the username/PWD you are using in file adapter to write the file (FTP) at target location is incorrect and hence the error. Please check and let us know.
    3) Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
    Description: The request requires user authentication
    Possible Tips:
    u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
    u2022 If the error is in Adapter Engine
    u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
    u2022 May be wrong password for user XIISUSER
    u2022 May be wrong password for user XIAFUSER
    u2013 for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
    Also, for HTTP errors in future do refer this blog:
    /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
    It will help you

  • Received HTTP response code 401 : Unauthorized

    Hi Experts!
    I know there are lots of posts regarding Received HTTP response code 401 : Unauthorized, and I read a lot of them.
    Unfortunately I got not the solution to my problem.
    I have following scenario: async; oneway; xml via DataPower (SOAP) to SAP PI to Service Consumer
    When sending a message it is led over the DataPower to the PI, but it is not processed through.
    It enters the MP and it is successfully put into the queue. You can see the details below.
    15.02.2012 15:12:34.611     Information     MP: entering1
    15.02.2012 15:12:34.614     Information     MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    15.02.2012 15:12:34.616     Information     SOAP: request message entering the adapter with user PI**
    15.02.2012 15:12:34.620     Information     SOAP: request message leaving the adapter (send)
    15.02.2012 15:12:34.620     Information     The application tries to send an XI message asynchronously using connection SOAP_http://sap.com/xi/XI/System.
    15.02.2012 15:12:34.624     Information     Trying to put the message into the send queue.
    15.02.2012 15:12:34.676     Information     SOAP: call completed
    15.02.2012 15:12:34.676     Information     SOAP: completed the processing
    15.02.2012 15:12:34.676     Information     Message successfully put into the queue.
    15.02.2012 15:12:34.676     Information     The application sent the message asynchronously using connection SOAP_http://sap.com/xi/XI/System. Returning to application.
    15.02.2012 15:12:34.678     Information     MP: leaving
    15.02.2012 15:12:34.682     Information     The message was successfully retrieved from the send queue.
    15.02.2012 15:12:34.700     Information     The message status was set to DLNG.
    15.02.2012 15:12:34.922     Error     Transmitting the message to endpoint https://<sid>.XXX:port/sap/xi/engine?type=entry using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 401 : Unauthorized.
    15.02.2012 15:12:34.940     Information     The message status was set to WAIT.
    15.02.2012 15:12:34.941     Information     The asynchronous message was successfully scheduled to be delivered at Wed Feb 15 15:17:34 CET 2012.
    I can't say, why I get the 401-response.
    From PI Message Monitoring: Monitor Messages I get following informations:
    Message-ID     MSG-ID
    Richtung     OUTBOUND
    Message-Headers     content-length=14391
    http=POST
    content-type=multipart/related; boundary=SAP_MSG-ID_END; type="text/xml"; start="<soap-MSG-ID[at]sap.com>"
    Message-Typ     Send
    Verbindungsname     SOAP_http://sap.com/xi/XI/System
    Credential     SAPPasswordCredential(PIAFUSER):password=********:sapclient=009:saplang=en:sapsysid=<SID>
    Fehlerkategorie     XI_J2EE_ADAPTER_XI_HANDLER
    Fehlercode     SEND_CONSUMER_ERROR
    Statusdetails     Messaging: allgemeiner Fehler
    Quality-of-Service     EO
    Empfängerkomponente     
    Referenz-ID     
    Senderkomponente     SENDER_COMP
    Sequenz-ID     
    Serialisierungskontext     
    Status     systemError
    Einplanungszeit     2012-02-15 13:49:38.579
    Start Time     Wed Feb 15 13:34:37 CET 2012
    Transport     HTTPS
    Gültig bis     
    Protokoll     XI
    Persistenz bis     2012-02-16 13:34:37.373
    Endzeitpunkt     Wed Feb 15 13:49:39 CET 2012
    Anwendungskomponente     
    Softwarekomponente     
    Service-Definition     
    Wurde bearbeitet     false
    Any clues?
    Many thanks in advance
    Holger

    Hi Ravi,
    it's the Java stack's port.
    Hi Venkata,
    1. Check whether service user maintained in the SM59 destination is with Roles of std. user PIAPPLUSER, PIISUSER
             The Problem is, that the message is not processed in the PI. I don't see them at SXMB_MONI.
             Today I see them on the RWB at the message-monitoring, but only because they are set after the 3rd try to send them to NDLV.
             I can see the messages, after they are triggered, in the comm-channel-monitoring by selecting the appropriate channel.
    2. Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
             Checked the PIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
    3.May be wrong password for user PIISUSER.
             There was a pwd-change in january, but the passwords are all correctly replaced.
    Thank you for your help!
    Holger

  • RNIF adapter error - Transmitting the message to endpoint failed

    Hi
    I have developed one interface SAPR/3 - PI - RNIF (Vendor system). the communication happens from PI to Vendor  via HTTPS protocol, the SSL certificates has been installed on PI J2EE engine, and configured in RNIF receiver communication channel.
    But when i perofrm end-end test and tryting to send messages from PI to Vendor system getting below error.
    "Transmitting the message to endpoint https://**.*.*.:***/SeeburgerDT/HTTPController?HTTPInterface=rosettanet using connection RNIFAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connect timed out."
    The URL "https://**.*.*.:***/SeeburgerDT/HTTPController?HTTPInterface=rosettanet" provided by Vendor team. i have checkd with the Vendor team and they said the URL works fine from their side and able to receive XML messages from our PI server (we are working on PI7.1.).
    Pls suggest why im getting Transmission error in PI RNIF adapter log.
    Is it the problem with SSL certificates installed on PI or URL used in RNIF communication channel ?
    Please help how to resolve this issue.. i would appreciate your help.
    Regards,
    Rajesh

    Hi,
    we are getting same message.
    "Transmitting the message to endpoint https://**.*.*.:**/*********************** using connection RNIFAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connect timed out."
    SSL_get_state() returned 0x00001180 "SSLv3 read client certificate A"
    [Thr 1085831488] *** ERROR during SecudeSSL_SessionStart() from SSL_accept()==SSL_ERROR_SSL
    [Thr 1085831488] SecudeSSL_SessionStart: SSL_accept() failed --
    [Thr 1085831488]   secude_error 536875074 (0x20001042) = "received a fatal SSLv3 bad certificate alert message from the peer"
    [Thr 1085831488] >> -
    Begin of Secude-SSL Errorstack -
    >>
    [Thr 1085831488] WARNING in ssl3_read_bytes: (536875074/0x20001042) received a fatal SSLv3 bad certificate alert message from the pe
    [Thr 1085831488] << -
    End of Secude-SSL Errorstack -
    [Thr 1085831488]   SSL NI-sock: local=10.1.1.11:51101  peer=210.71.237.26:41004
    [Thr 1085831488] <<- ERROR: SapSSLSessionStart(sssl_hdl=102b270)==SSSLERR_SSL_ACCEPT
    [Thr 1085831488] *** ERROR => IcmConnInitServerSSL: SapSSLSessionStart returned (-56): SSSLERR_SSL_ACCEPT [icxxconn_mt. 1676]
    [Thr 1088473408] Thu Oct 15 07:31:46 2009
    [Thr 1088473408]   SSL_get_state() returned 0x00001180 "SSLv3 read client certificate A"
    [Thr 1088473408] *** ERROR during SecudeSSL_SessionStart() from SSL_accept()==SSL_ERROR_SSL
    [Thr 1088473408] SecudeSSL_SessionStart: SSL_accept() failed --
    [Thr 1088473408]   secude_error 536875074 (0x20001042) = "received a fatal SSLv3 bad certificate alert message from the peer"
    [Thr 1088473408] >> -
    Begin of Secude-SSL Errorstack -
    >>
    [Thr 1088473408] WARNING in ssl3_read_bytes: (536875074/0x20001042) received a fatal SSLv3 bad certificate alert message from the pe
    [Thr 1088473408] << -
    End o
    Could you please let us know how did you resolve the issue?
    Thanks inadvance
    Regards
    Lshriva

  • Connection AFW failed, due to: Received HTTP response code 500

    Hi,
    I have tried to develop a file to file scenario in XI 3.0. The Sendor File adapter is reading the file but the message is not getting transfered to Integration engine.
    The audit log for the message is as follows:
    2005-05-07 04:10:24 Success Channel FileSendor: Send binary file "/tmp/xi_input.dat". Size 324 with QoS EO
    2005-05-07 04:10:24 Success Application attempting to send an XI message asynchronously using connection AFW.
    2005-05-07 04:10:24 Success Trying to put the message into the send queue.
    2005-05-07 04:10:24 Success Message successfully put into the queue.
    2005-05-07 04:10:24 Success The application sent the message asynchronously using connection AFW. Returning to application.
    2005-05-07 04:10:24 Success Confirmation mode test found. File will be resent next time
    2005-05-07 04:10:24 Success The message was successfully retrieved from the send queue.
    2005-05-07 04:10:24 Success The message status set to DLNG.
    2005-05-07 04:10:24 Error Transmitting the message to endpoint http://nadcp517:8020/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..
    Any suggestion...

    hi
    This problem comes due to the post installation steps might be at the time of post installation some wrong might be done.
    step1 : In sxmb_adm configure the integration server by giving the path as http://<host>:<abapport>/sap/xi/engine?type=entry
    step 2 : Check ur business system created at the time of post installation there u need to main the path as it as above.
    Reward points if useful,
    Regards,
    Srinivas.D

  • Transmitting the message to endpoint error

    Hi all,
    I am getting following error while doing the File to RFC Scenario:
    Error is;
    SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/URL_PIPELINE_NOT_FOUND; Params: /sap/xi/engine?type=entry., ENTRY.; AdditionalText:  ; ApplicationFaultMessage:  ; ErrorStack: Pipeline ID ENTRY., which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?type=entry.)
    Transmitting the message to endpoint http://sapxidev.tatatel.co.in:8000/sap/xi/engine?type=entry. using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Pipeline specified in URL attribute (type) not existing.
    Please, provide the solution for this
    Thanks In Advance
    Mahesh

    Hi Ganesh,
    It is opening properly.
    the result is like this:
    SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Header />
    - <SOAP:Body>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <faultcode>SOAP:Client</faultcode>
      <faultstring>Empty HTTP request received</faultstring>
      <faultactor>http://sap.com/xi/XI/Message/30</faultactor>
    - <detail>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
      </SAP:Error>
      </detail>
      </SOAP:Fault>
      </SOAP:Body>
      </SOAP:Envelope>

  • 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

  • Received HTTP response code 500 : Internal Server Error

    Hi All,
    In my scenario EANCOM to IDOC, I am getting an error in the sender communication channel (FILE Adapter). It is being picked up from the ‘sender’ directory successfully but not reaching the XI box (no messages seen in SXMB_MONI).
    The error in the runtime Workbench says the following:
    “Transmitting the message to endpoint http://gdrsap.nestle.com:50000/XIAxisAdapter/MessageServlet? using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Internal Server Error.”
    Regards,
    Manohar

    Hi Murli
    error code 500 stands for Internal Server Error
    This code is the default for an error condition when none of the other 5xx codes apply.
    for more details on error code follow the link
    http://www.web-cache.com/Writings/http-status-codes.html
    you have to restart J2EE engine
    steps to restart J2EE engine
    1) run transaction SMICM
    2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart
    by this java engine will restart and will be up in 5-10 minutes and your problem will be solved
    Thanks
    sandeep sharma
    PS ; if helpful kindly reward points

  • Received HTTP response code 500 : Internal Server Error using connection Fi

    Hi everybody,
    I have configured a file-webservice-file without BPM scenario...as explained by Bhavesh in the following thread:
    File - RFC - File without a BPM - Possible from SP 19.
    I have used a soap adapter (for webservice) instead of rfc .My input file sends the date as request message and gets the sales order details from the webservice and then creates a file at my sender side.
    I monitored the channels in the Runtime work bench and the error is in the sender ftp channel.The other 2 channel status is "not used" in RWB.
    1 sender ftp channel
    1 receiver soap channel
    1 receiver ftp channel.
    2009-12-16 15:02:00 Information Send binary file "b.xml" from ftp server "10.58.201.122:/", size 194 bytes with QoS EO
    2009-12-16 15:02:00 Information MP: entering1
    2009-12-16 15:02:00 Information MP: processing local module localejbs/AF_Modules/RequestResponseBean
    2009-12-16 15:02:00 Information RRB: entering RequestResponseBean
    2009-12-16 15:02:00 Information RRB: suspending the transaction
    2009-12-16 15:02:00 Information RRB: passing through ...
    2009-12-16 15:02:00 Information RRB: leaving RequestResponseBean
    2009-12-16 15:02:00 Information MP: processing local module localejbs/CallSapAdapter
    2009-12-16 15:02:00 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
    2009-12-16 15:02:00 Information Trying to put the message into the call queue.
    2009-12-16 15:02:00 Information Message successfully put into the queue.
    2009-12-16 15:02:00 Information The message was successfully retrieved from the call queue.
    2009-12-16 15:02:00 Information The message status was set to DLNG.
    2009-12-16 15:02:02 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Internal Server Error using connection File_http://sap.com/xi/XI/System.
    2009-12-16 15:02:02 Error The message status was set to FAIL.
    Please help.
    thanks a lot
    Ramya

    Hi Suraj,
    You are right.The webservice is not invoked.I see the same error in the sender channel and the receiver soap channel status is "never used".
    2009-12-16 15:52:25 Information Send binary file  "b.xml" from ftp server "10.58.201.122:/", size 194 bytes with QoS BE
    2009-12-16 15:52:25 Information MP: entering1
    2009-12-16 15:52:25 Information MP: processing local module localejbs/CallSapAdapter
    2009-12-16 15:52:25 Information The application tries to send an XI message synchronously using connection File_http://sap.com/xi/XI/System.
    2009-12-16 15:52:25 Information Trying to put the message into the call queue.
    2009-12-16 15:52:25 Information Message successfully put into the queue.
    2009-12-16 15:52:25 Information The message was successfully retrieved from the call queue.
    2009-12-16 15:52:25 Information The message status was set to DLNG.
    2009-12-16 15:52:27 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Internal Server Error using connection File_http://sap.com/xi/XI/System.
    2009-12-16 15:52:27 Error The message status was set to FAIL.
    what can I do about this?
    thanks,
    Ramya

  • File- XI- RFC (Error: Received HTTP response code 500..)

    Hi,
    I am working on File->XI->RFC  scenario, getting Processed Successfully status in "SXI_MONITOR".
    But Data is not posted in SAP R/3. I check   <b>Runtime Workbench  </b> Getting following Error in one step.
    Can any one help me in analyzing the error.....??????
    2006-06-09 14:36:32 Success output 1149888992513 Channel WEBMETHOD_SENDER_SOAPFMTEST: Send binary file "/usr/sap/transx42/data/xi_input.xml". Size 175 with QoS EO
    2006-06-09 14:36:38 Success output 1149888998592 Application attempting to send an XI message asynchronously using connection AFW.
    2006-06-09 14:36:39 Success output 1149888999757 Trying to put the message into the send queue.
    2006-06-09 14:36:40 Success output 1149889000823 Message successfully put into the queue.
    2006-06-09 14:36:40 Success output 1149889000824 The application sent the message asynchronously using connection AFW. Returning to application.
    2006-06-09 14:36:41 Success SAPEngine_System_Thread[impl:5]_12 1149889001577 The message was successfully retrieved from the send queue.
    2006-06-09 14:36:41 Success output 1149889001591 File "/usr/sap/transx42/data/xi_input.xml" deleted after processing
    2006-06-09 14:36:41 Success SAPEngine_System_Thread[impl:5]_12 1149889001745 The message status set to DLNG.
    <b>2006-06-09 14:37:47 Error SAPEngine_System_Thread[impl:5]_12 1149889067522 Transmitting the message to endpoint http://SAPR3001.bently.com:8042/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..</b>
    2006-06-09 14:37:47 Success SAPEngine_System_Thread[impl:5]_12 1149889067585 The asynchronous message was successfully scheduled to be delivered at Fri Jun 09 14:42:47 PDT 2006.
    2006-06-09 14:37:47 Success SAPEngine_System_Thread[impl:5]_12 1149889067695 The message status set to WAIT.
    2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367587 Retrying to send message. Retry: 1
    2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367587 The message was successfully retrieved from the send queue.
    2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367643 The message status set to DLNG.
    2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368435 The message was successfully transmitted to endpoint http://SAPR3001.bently.com:8042/sap/xi/engine?type=entry using connection AFW.
    2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368471 The message status set to DLVD.
    2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368472 The message was successfully delivered.
    Thanks & Regards

    Hi Umesh,
    I think, the reason is because of huge number messages ..
    Also just go to RFC adapter, activate the adapter,refresh the cache and try it..
    following guide will help you to solve problem~
    https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
    Just refresh the cache-The following guide will help you on that~
    https://websmp101.sap-ag.de/~sapidb/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
    Refer these SAP notes- 807000,803145
    (some hints)
    Regards,
    Moorthy

  • RFC  Received HTTP response code 500 : Timeout error

    Hi All.
    I am getting the following error for the RFC sender:
    Transmitting the message to endpoint http://pocitmsprdxi.crisp.com:8000/sap/xi/engine?type=entry using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout.
    The RFC sends the data to XI through RFC and at times the data is not entering XI and the error shown above occurs.
    How do i solve this?

    Hi Lavanya,
    For these kind of problem, you need to set proctimeout smicm as per SAP note - 824554 .
    Application threads in the J2EE engine might have got consumed in high load situations. Increase the count of application threads in config tool at location Config Tool -> cluster-data -> <configuration template> -> <instance-ID> -> managers -> ApplicationThreadManager -> MaxThreadCount.
    And also Increase the parameter ServletInputStreamTimeout.
    Hope this helps to you.
    Regards,
    P.Rajesh

  • Received HTTP response code 500 : Internal Server Error in XI

    Hi,
    I have configured a scenario SOAP to RFC in XI. when I am sending a message from web service, I got following error
    <SOAP:Fault>
                   <faultcode>SOAP:Server</faultcode>
                   <faultstring>Server Error</faultstring>
                   <detail>
                        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context>XIAdapter</context>
                             <code>DeliveryException</code>
                             <text><![CDATA[
    com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Internal Server Error
         at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:831)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
              ]]></text>
                        </s:SystemError>
                   </detail>
              </SOAP:Fault>
    Please suggest.
    Thanks,
    Ashish

    Read blog for all HTTP response code:Http* Errors in XI
    and read sap note  804124, 807000

  • Received HTTP response code 500..

    Hi All
    Whenever i try a scenario with file adapter as the sender, i get the following error in the runtime workbench (message monitoring).
    "Transmitting the message to endpoint http://USSAPVM7:8000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: Received HTTP response code 500.."
    Can anyone let me know as to what could be the cause of the problem. Please remember the response code is 500 and not 503.
    regards
    Sameer

    Hi Sudhir/Siva
    My pipeline url has the following entry,
    http://<hostname>:8000/sap/xi/engine/entry?action=execute
    so u recommend that i should change it to,
    http://<hostname>:8000/sap/xi/engine/entry?action=entry
    (or)
    http://<hostname>:8000/sap/xi/engine/entry?type=entry
    (or)
    http://<hostname>:8000/sap/xi/engine?type=entry
    which one of the above three should i change to. But whenever i try other scenarios such as idoc to file, it works fine. So by changing the pipeline url, will there be any problem while executing the the other scenarios.
    cheers
    Sameer
    Message was edited by: Sammy

Maybe you are looking for