Outbound RFC to file: Received HTTP response code 500

hello:
i am doing outbound rfc from ecc to other system using PI and I get the below error in the PI.
I am on PI 7.0 and looked at the RFC destiantions in ECC and all look good.
The registered program in TCP/IP RFC destination was tested and looks fine .
I checked the SMICM in PI running at port 8000 and it looks file and also i checked the SXMB_ADM Interation configuration in PI which looks good too .
Even the PI integration engine is restarted . i am sure its in PI and I am hoping its related to user in PI -adapter frame work user XIAFUSER?
can you please let me know how to fix the below issue ..
"Transmitting the message to endpoint http://HGSGXI50: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 : Internal Server Error"
thanks,

HI
for the error com.sap.aii.af.ra.ms.api.RecoverableException Received HTTP response code 500 Internal Server Error"
HTTP 500 can be any problem at receiver side. Are you sure, that the payload fits to the receiver requirements
Please refer this thread answered by Stefan Grube
Plain HTTP adapter error
check the similar thread HTTP server code 500 reason Internal Server Error

Similar Messages

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

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..

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

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

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

Received HTTP response code 500 : Timeout

Hi All,
I have done the File to JDBC to File(Sync) with module concept. Every thing is working fine in Dev system, yes'day it was moved to Quality System while i am trying to test i am getting the error in Sender File communication chennal.
Error: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
I have chaged the SQL statment to fetch only 50 records at that time its working fine with out any error.
While i am trying to collect 40,000 records its failing generally in Dev it use to take 4 to 6 min to gereate file.
Pls let me know do i need to chage any paramaters in Visual admin.
I have observed cm/keep_alive_timeout =60 (sec) but in dev the time is more? is this causing the problem?
I DEV system i don't have any issues the scenario is working fine.
Thanks,
Venkat.

Hi,
Yes..you should increase the icm/keep_alive_timeout.If you increase the time then until the connection will wait for the response. For more details..
[http://help.sap.com/saphelp_nw70/helpdata/EN/0b/1c7e7abbc311d5993a00508b6b8b11/content.htm]
Regards,
Prakasu.M
Edited by: prakasu on May 13, 2009 6:31 PM

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 with acknowledgment

Hello,
This is my process : R/3 (Idoc) -> XI -> 3rdParty(CSV).
I use R/3 4.6C and XI 3.0 SP10
This work fine but there is a problem with the acknowledgment :
Transmitting the message to endpoint http://<server>:8000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: Received HTTP response code 500..
I use this Weblog : /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
and all I can find in this forum.
What can I do ?
Thanks
Regards
Message was edited by: Christophe DUMONT

HTTP 500 is an error caused at the Web Server side. Any http connection happens in 4 steps:
1) Obtain the IP address from the URL - provied by DNS
2) Open Ip Socket for that IP
3) Use this socket to write data
4) Receive data stream back from the server.
This data stream which is passed by the server has status codes. If there is a status code 500, this is trapped only at the last level and client is not able to resolve the status.
You would want to look at the 4 points of faliure mentioned above. And it would help if u get someone on the Web Server side to look at the server logs. These logs are more descriptive and will provide a clue to set things right.
let us know if u are able to resolve the issue.

HTTP Response code 500 : Delivery Exception

Hello ,
i have following scenario WS(Client) <--> RFC. I am getting the following error :
Response code 500: File couldnot be posted.
Here are RWB data entries :
2006-03-13 09:45:52      Success      SOAP: request message leaving the adapter (call)
2006-03-13 09:45:52      Success      Application attempting to send an XI message synchronously using connection AFW.
2006-03-13 09:45:52      Success      Trying to put the message into the call queue.
2006-03-13 09:45:52      Success      Message successfully put into the queue.
2006-03-13 09:45:52      Success      The message was successfully retrieved from the call queue.
2006-03-13 09:45:52      Success      The message status set to DLNG.
2006-03-13 09:46:11      Error      Returning synchronous error notification to calling application: Received HTTP response code 500..
2006-03-13 09:46:11      Error      Transmitting the message using connection http://<XiServer>:8000/sap/xi/engine?type=entry failed, due to: Received HTTP response code 500..
//i changed here server name for internal reasons//
2006-03-13 09:46:11      Error      The message status set to FAIL.
2006-03-13 09:46:11      Error      Returning to application. Exception: Received HTTP response code 500.
2006-03-13 09:46:11      Error      SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500.
I did all the things i could do , tested soap service working fine, changed settings in sxmb_adm as well
Please suggest,
Vara

thanks sam,
Well i have the following error message in soap envelope:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Body>
          <SOAP:Fault>
               <faultcode>SOAP:Server</faultcode>
               <faultstring>failed to call the adapter engine</faultstring>
               <detail>
                    <s:SystemError
xmlns:s="http://sap.com/xi/WebService/xi2.0">
                         <context>XIAdapter</context>
                         <code>DeliveryException</code>
                         <text><![CDATA[
Please suggest :

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,

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

Received HTTP response code 404 : Not Found

I am attempting to pass a file through XI into an IDoc to ECC. I have tested the mapping, and that works fine. I have also tested the configuration in the integration builder and it seems to be fine. However, when the file is picked up by XI from the directory, processed by XI, and then sent to ECC, an error occurs in the runtime workbench:
Transmitting the message to endpoint http://server:port/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
The error leads me to believe that the system cannot be found, or there is a privelage issue with the service user attempting to log onto ECC. However I believe I have set up the RFC connection correctly, and the service user should be fine.
Does anyone know what may be causing this? I am using the IDoc adapter for the reciever communication channel. I have set the RFC destination (and tested it in SM59, works fine) and the port (I assume this is the port in WE21?). Not sure where to look...

Being that the error says:
Transmitting the message to endpoint http://server:port/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
I am trying to understand what this means. Can anyone explain to me why the message is getting sent to this address? I assume that the AFW is coming into play because I am using the IDoc adapter, hence the adapter framework. Is this true? Should the AFW be showing up, or do you think there is another issue?
Mainly I want to know if this is more of a basis issue, or a configuration problem with the interface in XI?

Outbound RFC to file: Received HTTP response code 500

Similar Messages

Maybe you are looking for