Archive file does not exist

[Former Member]

We have a requirement to move archive files that were previously stored on the transfer directory /usr/sap/<SID>/archive to an Opentext store. We have setup the connection to Opentext for the A2 repository in OAC0. The connection test returns ok. We get an error "HTTP error: 400 Bad Request 5010: wrong usage: - Wrong Usage!" if we click on CSAdmin but this error does not seem to be an issue as we have the same error on other systems where this functionality is working. We can see the repository with a green light in the Overview tab.

I go to SARA and choose to store file for previously completed archive job. The Archive File is accessible (Green Light):

File Name RFI09020

Logical Path ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK

Physical File Name /usr/sap/TST/archive/RFI09020

However, the store job errors with the following information in the job log:

12.09.2011 12:25:09 Job started 00 516 S

12.09.2011 12:25:09 Step 001 started (program RSARCH_STORE_FILE, variant , user ID SMITHADC) 00 550 S

12.09.2011 12:25:09 Archive file 000739-001FI_DOCUMNT is being processed BA 165 S

12.09.2011 12:25:15 Archive file 000739-001FI_DOCUMNT does not exist BA 111 S

12.09.2011 12:25:15 Error occured when checking the stored archive file 000739-001FI_DOCUMNT BA 194 E

12.09.2011 12:25:15 Job cancelled after system exception ERROR_MESSAGE 00 564 A

File is present on the file system, owner is <SID>adm and have tried with 777 permissions. File can be seen when going through AL11 too.

The customizing settings for FI_DOCUMNT are setup to use logical file name ARCHIVE_DATA_FILE_WITH_ARCHIVE_LINK with Physical File R<PARAM_1><MONTH><DAY><PARAM_2> and Logical Path ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK. Logical file path ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK is set with Physical Path /usr/sap/TST/archive/<FILENAME> for UNIX.

Any ideas? I can see numerous other similar topics raised but they have always been solved by file permissions which I can see no problems with.

Adrian

[Former Member]

Issue was certificate and security settings on the Opentext side. Error message was a red herring.