Skip to Content

Erroneous duplicate file error in PI 7.1

We have a file transfer process in PI which picks up files from a shared drive, and passes the contents to an RFC in the ECC system, then archives the files in a separate folder.

We have recently activated the relevant communication channels in PI DEV in order to test interfaces into a recently patched ECC DEV system.

Currently all files are erroring as follows: "Could not archive file <filename> after processing"

The message log contains the following:

"Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 1a5c01d9-c2d7-11e6-851c-00001998b6ba(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: Violation of PRIMARY KEY constraint 'PK__BC_MSG_D__99C1915D3336943B'. Cannot insert duplicate key in object 'SAPPD4DB.BC_MSG_DUP_CHECK'. The duplicate key value is (1a5c01d9-c2d7-11e6-851c-00001998b6ba, OUTBOUND)."

Any thoughts on why this is happening? The interfaces have worked in the past, and the equivalent interfaces in QAS and PRD are working ok. The files in question are unique and have not been processed before by the system.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 21, 2016 at 11:21 AM

    This has now been resolved, the issue was incorrect permissions on the archive folder, meaning the Pi DEV service was unable to access it. So PI fails to archive the message the first time, then on subsequent retries reports a duplicate error message as the file has already been processed, even though it failed to archive.

    Add comment
    10|10000 characters needed characters exceeded