cancel
Showing results for 
Search instead for 
Did you mean: 

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

former_member273752
Participant
0 Kudos

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

Accepted Solutions (0)

Answers (1)

Answers (1)

Shabarish_Nair
Active Contributor
0 Kudos

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

former_member273752
Participant
0 Kudos

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