Skip to Content

File to RFC Synchronous Scenario: Error "Channel is not a Receiver Type"

Dear All,

We are using a File-to-RFC Synchronous scenario, where PI reads a file from a FTP server, and posts some business transaction synchronously into SAP. After posting the data, the SAP system gives back a status response corresponding to the data, which is captured by PI and a status file is written. The source file is moved to an archive folder. We are not using a BPM to achieve this; instead using RequestResponseBean and ResponseOneWayBean to achieve this. The interface was running without a hitch; suddenly we are experiencing a problem while processing the file. In the MDT, the error details are given as : Attempt to process file failed with com.sap.aii.af.ra.ms.api.RecoverableException: Error: invalid receiver channel '45aartsfse92347g1g816deb10235b963b'. When we look through the defaultTrace.trc, we come accross an error which states:Channel 45aartsfse92347g1g816deb10235b963b is not receiver type. We tried CPACache refresh, anticipating that it is a Cache issue, but no luck whatsoever. Has anybody encountered such a problem? Is there a known solution to it?

Awaiting answers.

Thanks and Regards,

Sid

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Sep 10, 2010 at 08:55 AM

    It is actually a cache issue.

    Did you CPA cache refresh complete without any errors?

    try a full cache refresh. Else another option would be to try and restart the RFC adapter service from VA or NWA.

    And a final step might be to try to restart the java stack itself

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Shabarish,

      Thanks for the prompt reply. We have solved the problem, although the reason was really trivial: The user who was monitoring RWB had accidentally stopped the File receiver channel. So, while processing the source file, the module processor found the stopped channel and identified it as a channel which is not of type receiver. That's why the error was triggered. Closing the thread.

      Thanks and Regards,

      Sid

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.