Skip to Content

File adapter is in error state

Hi Experts,

we have File to RFC [Synchronous scenario ].

File adapter will pick the XML files from the FTP server and send it to PI. The communication channel is not picking the files, it is suddenly stopping.

The status is showing error state. but when i ping the channel everything is the connection, port, directory sender agreement etc.

when i stop and start the communication channel, it is picking and processing the files normally.

Like this it is happening daily minimum 10 - 15 times, every time i'm starting and stop the communication channel.

Please let me know how to over come this issue, without any manual interference.

Regards

Bhargava krishna

Untitled.jpg (62.0 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Aug 27, 2013 at 07:39 AM

    Hello,

    What's the error message u r getting? Define timeout parameter in ur sender file channel and then check?

    Thanks

    Amit Srivastava

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Peter,

      Generally i have noticed this kind of erratic behavior when the timeout parameter is not defined in the sender file channel which resulted into blocking of connections and eventually messages are not getting picked up, but in Bhargava's case since he has already defined this parameter in sender channel so eventually this possibility is ruled out...

      @Bhargava,

      Put timeout parameter as 30 or 45 secs and then check?

      http://scn.sap.com/thread/1932990

      Thanks

      Amit Srivastava

  • Aug 27, 2013 at 07:40 AM

    Hello Bhargava krishna,

    I know that phenomenon. What I normally do is do a slight change in the Integration Builder to the Channel, for example add a blank in the Description, save and activate.

    If that does not help either, create a new channel and delete the erroneous one.

    Best regards,

    Peter

    Add comment
    10|10000 characters needed characters exceeded

    • IƱaki Vila Bhargava krishna Talasila

      Hi Bhargava,

      The problem could be in the FTP server that it doesn't accept to use the same connection, you could try with Connect Mode: Per file transfer, and with each file transfer a new connection will be established.

      Regards,

  • avatar image
    Former Member
    Aug 27, 2013 at 09:58 AM

    Hi Bhargava,

    Can you please check if the lock is getting acquired on the channels?

    got to nwa>>resource monitoring>>locks

    Here you can find the locks acquired by system.

    We were facing same issues so we removed locks and the issue was resolved.

    One more point is please check whether you connection is Active or passive. Normally it should be passive.

    Regards,

    Rahul Kulkarni

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      I've checked the locks, everything is fine. currently there are files in the directory but it is not picking.

      when i ping the channel, it is showing like this.

      Really it is weird, when i stop and start the communication channel, the files are processed.

      Regards

      Bhargava krishna

      Untitled.png (10.9 kB)
  • avatar image
    Former Member
    Aug 27, 2013 at 12:58 PM

    Hello Bhargava,

    Please try to make your connection passive. it will work.

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 28, 2013 at 11:06 AM

    Hi All,

    Thanks for the inputs.

    Actually there is some problem in the java engine, apart from this issue, i also noticed the issues like

    --> No SLD registered while opening the component monitoring.

    --> Messages are failed with system error status [ HTTP 503].

    --> connection b/w abap engine and java engine is not working. due to this, messages are successfully processed but in TBDL state in RWB and not visible in abap engine.

    --> Connection between ESR and ID also not working.

    Solution: Restart the PI server.

    Regards

    Bhargava krishna

    Add comment
    10|10000 characters needed characters exceeded