Skip to Content
author's profile photo
Former Member

No receiver found


as Tom XU, sometimes i have problem with interfaces (send RFM into idoc via XI )

here is the error in the monitoring


<SAP:Text language="EN">Unable to determine a receiver (processing type: QoS = EO or EOIO)</SAP:Text>


Generaly the result is fine with this inferface but sometimes the status is "no receiver found"

i tried to restart the message without result

thanks to help me if possible


Add comment
10|10000 characters needed characters exceeded

2 Answers

  • Posted on Jun 16, 2004 at 04:03 PM


    The most common reason for this error is:

    1. an error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.

    2. an error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!

    But if I understood you well, your scenario works fine, but only sometimes something goes wrong, right?

    So in this case, it rather can't be typo in configuration. Are you sure that the adapter on the receiver side is up and running?


    Andrzej Filusz

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      Thanks for your informations

      However, this interface is ok 99 times and it bugs one time, so i'm not sure there is a mistake in configuration or design .

      but i will check tomorrow ...

      if you have other ideas...

  • author's profile photo
    Former Member
    Posted on Jun 17, 2004 at 03:20 AM

    Hi rousseau cedric :

    Could it be possible that your R/3 System is down ?


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Praveen

      No, the R/3 system is not down

      could it be possible that when there is a lot of messages (more than 2500) the system is overload and so, few messages are in error