Skip to Content

How PI classify a File as faulty? How to Avoid Archive of Faulty File not intended?

Hi Experts,

In my current project majority of our interfaces involve files for both inbound and outbound. We have enabled the Archive faulty file option for the sender SFTP channels and it was working as intended.

However, our client requested to move our source and target SFTP server to a new one. The problem now is that inbound files even if they processed properly, a copy is also created into the Archive Faulty file directory. There is no indication in the channels or in the message monitoring with regards to the files being Faulty and they delivered successfully to S4.

The creation of copy into Archive faulty file directory causes issue if same test file is uploaded. The Faulty file archive directory does not allow overwrite and so files are stuck.

Any ideas of solution or links to further discussion is highly appreciated.

Thank you.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Jul 16, 2020 at 08:58 AM

    Some day someone will hit me for always throing out this boilerplate answer, but please have a look at XPI Inspector (Example 50 - give your CCs) to narrow this down.

    Add a comment
    10|10000 characters needed characters exceeded

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.