AFW Failed

Guys
Doing file to file scenario. The transaction fails and throws an error message in RWB>>msg monitor that "Transmitting the message to end point http://<hostname>:<port>/sap/xi/engine?type=entry using connection failed. due to :Received HTTP response code 404"
When I checked XI Adapter Framework(Adapter engine netweaver) in RWB>> component monitoring, it show unable to establish connection to "http://<hostname>:<port>:8200/rtc"
Please give me a quick solution and expect good reward points
Regards
Govind

Hi,
1) Check pipeline URL in the SLD in the business system of the Integration Server
For this go to SLD->Business System-><Integrtaion Server>->Pipline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry
Where host is the host name of the Integration Server and port is the HTTP(8xxx) port.
2) RWB error - have a look into this SAP Note -768456
3) Check the ICM port also. Go to SMICM->Services here you should have http port
Hope this helps,
Regards,
Moorthy

Similar Messages

Webservice and BPM; connection AFW failed

I have created the following integration process:
1. Asynchronous receive step of a xml file;
2. Synchronous send step to invoke webservice;
3. Asynchronous send step of the response file.
In this process XI will read a xml file from a directory on the server, convert this file to a SOAP request, call the webservice and convert the SOAP response to a xml file. This file is then sent to the same server directory.
When I look in SXMB_MONI the whole process is set to ok. The response of the webservice is in the payload of the XI response message. (This is the message from my integration process to the inbound message interface.).
But the response file never reached its destination.
When I look at the file adapter monitor it reports: "Up and running - no message processing until now".
And when I look at the message monitoring, there are the following messages:
2005-07-29 11:30:55 Success The message was successfully received by the messaging system.
Profile: XI URL: http://nthvsnw4:50000/MessagingSystem/receive/AFW/XI
2005-07-29 11:30:55 Success Using connection AFW. Trying to put the message into the receive queue.
2005-07-29 11:30:55 Success Message successfully put into the queue.
2005-07-29 11:30:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:30:55 Success The message status set to DLNG.
2005-07-29 11:30:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:30:55 Success The asynchronous message was successfully scheduled to be delivered at Fri Jul 29 11:35:55 CEST 2005.
2005-07-29 11:30:55 Success The message status set to WAIT.
2005-07-29 11:35:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:35:55 Success The message status set to DLNG.
2005-07-29 11:35:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:35:55 Success The asynchronous message was successfully scheduled to be delivered at Fri Jul 29 11:40:55 CEST 2005.
2005-07-29 11:35:55 Success The message status set to WAIT.
2005-07-29 11:40:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:40:55 Success The message status set to DLNG.
2005-07-29 11:40:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:40:55 Success The asynchronous message was successfully scheduled to be delivered at Fri Jul 29 11:45:55 CEST 2005.
2005-07-29 11:40:55 Success The message status set to WAIT.
2005-07-29 11:45:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:45:55 Success The message status set to DLNG.
2005-07-29 11:45:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:45:55 Error The message status set to NDLV.
I looked at several postings with the subject "Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException", but I could not find any which seems to meet my problem.
I would highly appreciate any help on this.

Sorry for my late response, but I did not look at this after it was solved and I did not receive any mail. So please let me know if you still need some support.
I could send you a document with some screen shots. If so send me an email ([email protected])

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

AFW: Failed to transmit message due to RecoverableException

Hi all,
I use a XI 3.0 SP 14.
I've created a BPM with 3 steps:
1) receive step
2) send synchronous step
3) send asynchronous step
XI exposes a Asynchronous Message Interface as a Web Service. Than the BPM uses this information to send a synchronous call to a Web Service (this WS is created from an EJB and deployed on a SAP Web AS 6.40). Than the BPM uses the WS response to send an asynchronous mail.
In the SXI_MONITOR everything works fine, but in the message monitor (Messages from the Adapter Framework) I get this error when I try to send an e-mail (step 3):
2005-11-08 15:22:25 Success The message was successfully received by the messaging system. Profile: XI URL: http://sapadx01:51600/MessagingSystem/receive/AFW/XI
2005-11-08 15:22:25 Success Using connection AFW. Trying to put the message into the receive queue.
2005-11-08 15:22:25 Success Message successfully put into the queue.
2005-11-08 15:22:25 Success The message was successfully retrieved from the receive queue.
2005-11-08 15:22:25 Success The message status set to DLNG.
2005-11-08 15:22:25 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-11-08 15:22:25 Success The asynchronous message was successfully scheduled to be delivered at Tue Nov 08 15:27:25 CET 2005.
2005-11-08 15:22:25 Success The message status set to WAIT.
2005-11-08 15:27:25 Success Retrying to deliver message to the application. Retry: 1
In the default trace I can see:
Failed to transmit message 436f38c9-0617-022e-0200-00000ab44471(INBOUND) due to com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
java.lang.NullPointerException
 at com.sap.aii.af.service.alerting.Alert.getInputInterface(Alert.java:330)
 at com.sap.aii.af.service.alerting.Alert.send(Alert.java:103)
 at com.sap.aii.af.service.alerting.Alert.run(Alert.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
 at java.security.AccessController.doPrivileged1(Native Method)
 at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
I don't have this problem if instead of SOAP Synchronous call I do an RFC Synchronous call (on step 2)
I also get a mail (step 3) if I have a System Error Exception in the SOAP synchrounous call (step 2)
I have also noticed that:
when I call the mail adapter (asynchronous step) with the Web Service Response in the HEADER I've got the ACK field:
<SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Status>OK</SAP:Status>
<SAP:Category>permanent</SAP:Category>
</SAP:Ack>
Instead if I call the mail adapter (asynchronous step) with the BAPI Response in the HEADER I haven't got the ACK field.
But in the BPM send Asynchronous step the "acknowledgement" parameter is set to NONE
Could you please help me?
Best Regards,
Paolo

Ops... the note will be released in the near future...
Anyway my problem was that the response message from the SOAP Receiver Adapter included the XI Ack header for any successfull response message. Then, when I tried to send an asynchronous request message to the Mail Receiver Adapter it was not able to manage this ACK.
Best Regards,
Paolo

Connection AFW failed, due to: RecoverableException : SOAP Adapter.

Hi All,
We are using XI3.0 Sp14 . the message flow is
IDOC> XI> SOAP ADPATER (receiver side)--> External system.
Here everything is fine, we are using https URL of the extrnal system to send the cXML file on there side. The external URL is fine and working.
When we send the idoc from R/3 to XI. then it gives very common message. I dont know what is wrong with this message. .
Please check this , what I got in Audit log:
2007-04-16 10:14:03 Error Exception caught by adapter framework: null
2007-04-16 10:14:03 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2007-04-16 10:14:03 Success The asynchronous message was successfully scheduled to be delivered at Mon Apr 16 10:19:03 EDT 2007.
2007-04-16 10:14:03 Success The message status set to WAIT.
I don't know why I am getting this error message. Please help me to resolve this. Thanks
regards
Ram Singhal

Hi,
For SOAP receiver adapter, you have the WSDL file from the provider of the webservice, either from a URL link or physically receiving the file.
The WSDL file contains the attribute "location" from the element "address", and the attribute "soapAction" from the element "operation". These 2 values must be entered exactly as is into the SOAP comm chan config.
Also, insure the proxy information are also entered correctly, include the userid/password if required. The webservice provider may also require authentication, so make sure it is also entered.
If possible, execute the webservice using a generic SOAP client tool to test. Use the exact configuration entries as those you used in XI. There are many free tools from the internet.
Regards,
Bill

Entry using connection AFW failed

Hi,
I am trying to read an external file and push it in to R/3 by calling RFC using XI.
I configured everything.
File and RFC adapters are working fine.
After processing as per settings it is deleting the file but it is not pushing in to R/3.
In the Audit log i am getting the following messsages:
1.Success>Send binary file "tom.xml" from FTP server "entegdt27:XIshared", size 140 bytes with QoS EO
2.Success>Application attempting to send an XI message asynchronously using connection AFW.
3.Success>Trying to put the message into the send queue.
4.Success>Message successfully put into the queue.
5.Success>The application sent the message asynchronously using connection AFW. Returning to application.
6.Success>The message was successfully retrieved from the send queue.
7.Success>File "tom.xml" deleted after processing
8.Success>The message status set to DLNG.
9.Error>Transmitting the message to endpoint http://entegdt27:8000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..
10.Success>The asynchronous message was successfully scheduled to be delivered at Tue Dec 06 09:39:01 IST 2005.
During retry the same error(9) is repeating.
Can Anyone Help.
Thanks in Advance

Hi Chemmam,
       The file adapter is picking up the file and deleting the same.The problem should be in mapping or the receiver adapter configuration.
Check the following things.
        1.In design time(repository) check whether the mapping between the two data types are perfect.Check the same by using test tab and execute option.
        2.Then go to the reciver SAP r/3 business system and go to transaction SM59.Check whether the a connection is established between the receiver system and the Intergration server.
          Create connections by giving the log on parameters of the XI server and the program ID and test the connection.
        3.If the test connection is perfect , then go to receiver R3 system and try executing the RFC as stand alone by giving appropriate inputs.
        4.If that is working fine.Then check for your configuration settings.The Comunication channel between XI and Receiver SAP R/3 should be under the SLD registered business system while the sender communication channel(File adapter) should be under a service.
         5.In receiver communication channel check for the log on parameters of the receiver SAP system.
      Hop this helps you in locating the root cause.
regards,
aravindh.

Connection afw failed

hi gurus,
i getting an error msg " transmitting the message to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFW failed ,due to com.sap.aii.af.ra.ms.runtime:clusterexception: serverinternal locking not avaliable"
With Regards,
Shakthi Raj N.

Hi, I'm experiencing the same problem.. how did you solved it?
Thanks in advance for your help
Sonia

Xi 3.0: Mail adapter fails with "exception in method process"

Hi.
I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
I tried both async and sync case with the same result. In the sync case, the response contains:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea???

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
Anyway, in my server i get a 404 for the link you suggested.
In the async case i don't get any error on the SXMB_MONI but only on the A.F.
I attach the audit log for the async case:
Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
Time Stamp Status Thread ID Sequence No. Description
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
Total: 33 Entries 1020304050 messages displayed per page; this is page 1 of 1 page(s)

Strange problem in AFW custom module (question for gurus)

Hi there SDN'ers,
I have I very strange problem with an additional Adapter Module I developed.
My scenario is: IDOC -> JDBC (Oracle)
Well, to make a long story short, say that before the JDBC Receiver cc can write my data to the db, I have to do (inside the channel) kinda java mapping in order to produce an XML document that is acceptable for it. So in my module I manipulate the payload via DOM. No problem here.
The strange story is: at first attempt, the Adapter fails (see error below), while after 5 minutes, when automatically trying again, it succeeds.
Just because I put some stuff in the message audit log, what I can tell you is this weird thing:
1. at first, no XML document exists in the payload, but in place of it there's this string:
org.apache.crimson.tree.XmlDocument@745501c6
which seems to be a toString() of something I don't (or don't know to) use directly
2. at the second attempt, even in the audit log I can actually see the weel-formed XML document ready for the JDBC adapter, and in fact data are written to the db.
?? WHAT COULD THIS BE CAUSED BY ??
Say also that the the other way around (JDBC->IDOC) with another very similar module works perfectly.
Thanks.
Alex
Delivery of the message to the application using connection AFW failed, due to: ERROR occured parsing request:com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6f, 72, 67(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6f, 72, 67(:main:, row:1, col:3).
P.S. -> 6f, 72, 67 is "org", that is the first three letter of the weird payload I get at first attempt.

Ok guys, I got that workin'.
I don't know why - and don't think I'll have the time to investigate further - but it seems the implementation of DOM Document used by XI is different the first time AFW executes my module, so here my workaround.
if (docOut instanceof org.apache.crimson.tree.XmlDocument) {
 org.apache.crimson.tree.XmlDocument tmpDocOut = (org.apache.crimson.tree.XmlDocument)docOut;
 tmpDocOut.write(out);
} else {
 out.write(docOut.toString().getBytes());
Regards,
Alex

Attempt to process file failed with Exception in XML Parser-format problem

Hi all,
Iam getting an unusual error in the J2EE stack in XI.
And the message is:
006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)' 2006-11-30 17:31:07 Error Exception caught by adapter framework: null 2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
My scenerio iam posting IDOC to a flat file with content conversion in the receiver side,the mapping got executed successfully and in the audit log i found that the error was after the 'Start converting XML document content to plain text'.
This means that error occured during content conversion of XML to the prescribed file format.
Can anyone suggest any better approach using which we may trace the junk data in IDoc. Manual adhoc approach could take time and is error prone.
Thanks in advance...
karun

Hi Bhavesh,
Thanks for the early reply. I checked the mapping and everything is fine and the output is also in valid XML format.
The audit log shows that the mapping got executed successfully and the error is after the step 'Start converting XML document content to plain text '. Is there any constraint in the file adapter regarding the message size for parsing.
2006-11-30 17:30:50 Success Transfer: "BIN" mode, size 2912595 bytes, character encoding -
2006-11-30 17:30:50 Success Start converting XML document content to plain text
2006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)'
2006-11-30 17:31:07 Error Exception caught by adapter framework: null
2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2006-11-30 17:31:07 Success The asynchronous message was successfully scheduled to be delivered at Thu Nov 30 17:36:07 GMT 2006.
2006-11-30 17:31:07 Success The message status set to WAIT.
2006-11-30 17:31:08 Success Acknowledgement creation triggered for type: SystemErrorAck
2006-11-30 17:31:08 Success Acknowledgement sent successfully for type: SystemErrorAck
2006-11-30 17:36:08 Success Retrying to deliver message to the application. Retry: 1

Transmitting message to entry pipeline failed !!

Hi all,
We have configured a file adapter to poll a specific directory. Now the adapter polls the file , deletes it after reading it , however it fails to deliver the message to entry pipeline.
We are getting an error msg that reads:
Transmitting the message to endpoint http://itcxi1:53000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404..
We have already gone through the link:
Transmitting message to entry pipeline failed !!
Accordingly we have checked but we have not used any business system.
There are two business service(one sender and the other reciever).
We have checked sxmb_adm and httpport in the exchange profile but all of them are filled with the respective values:
com.sap.aii.connect.integrationserver.r3.httpport = 8030.
com.sap.aii.connect.integrationserver.httpport = 53000.
in sxmb_adm we have given url as http://10.119.4.33:8030/sap/xi/engine?type=entry
But still in the error msg the url reads as:
http://itcxi1:53000/sap/xi/engine?type=entry
The entire audit log shown is:
2006-05-24 12:59:10 Success
Channel SenderChannel: Send binary file "D:\usr\sap\trans\tmp\sender\xi_input.xml". Size 363 with QoS EO
2006-05-24 12:59:10 Success
Application attempting to send an XI message asynchronously using connection AFW.
2006-05-24 12:59:10 Success
Trying to put the message into the send queue.
2006-05-24 12:59:10 Success
Message successfully put into the queue.
2006-05-24 12:59:10 Success
The application sent the message asynchronously using connection AFW. Returning to application.
2006-05-24 12:59:11 Success
The message was successfully retrieved from the send queue.
2006-05-24 12:59:11 Success File "D:\usr\sap\trans\tmp\sender\xi_input.xml" deleted after processing
2006-05-24 12:59:11 Success
The message status set to DLNG.
2006-05-24 12:59:11 Error
Transmitting the message to endpoint http://itcxi1:53000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404..
2006-05-24 12:59:11 Success
The asynchronous message was successfully scheduled to be delivered at Wed May 24 13:04:11 GMT+05:30 2006.
2006-05-24 12:59:11 Success
The message status set to WAIT.
2006-05-24 13:04:11
Success Retrying to send message. Retry: 1
This same process is repeated 4 times.
Pls suggest what else do i need to check.
Regards
Neetu

Hi Michal,
Thanks for ur prompt response.
Actually in this scenario i am not using any business system.
As mentioned before i have two business services one of which acts as the sender service and the other one acts as the receiver service.
Each one of them have their corresponding communication channels.
So where do i change the url.
My sld has a business system for xi in which i changed the url, putting the port as 8XXX.
Next i imported this system to my scenario and tried sending a message again but got the same error.
What should i do next?
Regards
Neetu

AFW to IS Communication Error?

I am having trouble setting up a file adapter on the central adapter engine for XI 3.0
The adapter engine is able to pick up the files, but has a communication failure sending the message to the integration server.
No xml message arrives in SAP_MONI, however there is the following error message in the Adapter Framework log:
Transmitting the message to endpoint http://xyz.com:8090/sap/xi/engine/entry?action=execute using connection AFW failed, due to: Received HTTP response code 500..
Unfortunatly HTTP Error 500 is very generic, definition below from the web:
Internal Server Error: The Web server is incapable of performing the request.
The message is being sent with the following configuration:
Direction: OUTBOUND
Message Type: Send
Profile: XI
Connection: AFW
Transport: HTTP
End Point: http://xyz.com:8090/sap/xi/engine/entry?action=execute
Authorization: SAPPasswordCredential(S_SB_XIAF):password=********:sapclient=100:saplang= 
This looks like an internal communication issue...
Any advise on how to track down the root cause?

Thanks Xin.
I have already looked in MDT, that is where I got the original error text.
I will try the visual administrator - hopefully that will have some more detailed logs with more of an explanation of the error. Does the visual administrator cover only J2EE stack logs, or also the ABAP stack?
Unfortunatly the URL was for the reverse scenario of mine - the error I have is going from Adapter Engine to IS, and there is a chance the error occurs in the IS, but the IS is not able to give back a proper response to the Adapter Engine (hence the HTTP 500: Internal Server Error)

Files fail to reach IS after being processed by File adapter

Hi,
Till a few minutes back, our XI server was working fine. But all of a sudden the messages could not be sent to IS for processing. I found the following message in RWB--> Message monitoring.
8000 is the ABAP port that we have mentioned in SMICM.
Transmitting the message to endpoint http://intersrv:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.ProtocolException: Server redirected too many times (20).
In adapter monitor i found that the message has been successfully been picked up(processed).
Also 1 strange thing that i observed is, when i tried posting the same payload using HTTP adapter(i mean the sample HTML page used to post HTTP requests to IS) is failing. I could not see any messages in sxmb_moni when i tried in an EO or EOIO processing mode.
Kindly help me on this.
Regards,
Siva Maranani

siva,
can you check the url in SLD for the related business system. It should be 8000 also and not 50000(i had a similar error and it was resolved by changing the URL in SLD.
is your DB up?
thanks
tony

Adapter framework failing to send message

Hi,
I am facing an issue in XI, where the adapter framework is getting failed to send the message. The message is also not getting reflected in SXMB_MONI,
"Transmitting the message to endpoint http://server:8080/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not found."
No service using the ICM port 8080 is working though active. No XI service, even the ping service in sap/bc/ping is not working.
I have checked the following:
1) SLDCHECK (browser opening properly). In ABAP part i am getting error
Use transaction SLDAPICUST if you wish to maintain
Launching the SLD GUI in a separate browser window.
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Summary: Connection to SLD does not work
=> Check SLD function and configurations
for troubleshooting the above error i have gone through the link
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm
Still the problem persists while calling function LCR_LIST_BUSINESS_SYSTEM
2) Then i checked the ping (path - http://server:8080/sap/xi/engine?type=entry ) -- its also not running and showing error :
Service cannot be reached with error code 404 not found.
3) The RFC XIINTEGRATION_SERVER is showing also showing error 404.
4) Checked ICM port - its 8080
Inspite of working hard over this issue, still unable to resolve this issue.
Please help me. Awaiting for your helping suggestions
Thanks in advance..

> Still the problem persists while calling function LCR_LIST_BUSINESS_SYSTEM
> 2) Then i checked the ping (path - http://server:8080/sap/xi/engine?type=entry ) -- its also not running and showing error :
> Service cannot be reached with error code 404 not found.
>
> 3) The RFC XIINTEGRATION_SERVER is showing also showing error 404.
> 4) Checked ICM port - its 8080
>
have a look for LCR_LIST_BUSINESS_SYSTEM in the below link
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm
Regards,
Sarvesh

JMS Adapter Fail - Receiver channel. Details: Receive timed out

Its an IDOC to JMS scenario. IDOC gets processed through the pipeline in XI successfully, can see the checkered flag.
However in Adapter monitoring, JMS adapter is in red.
The error text against the Communication Channel is "Receiver channel. Details: Receive timed out".
I am trying to connect to the JMS queue provided by a third party on port 1100 ( as configured in JMS adapter).My initial analysis is to check if the port is open on the third party's firewall( Need to get the response back from them yet).
However i would like to know, if there is something else that i should look into?

Following are the error messages in RWB audit log for the message sent.
Exception caught by adapter framework: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out
Error Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out.
what might be the problem?

AFW Failed

Similar Messages

Maybe you are looking for