Integration S3 agent fails to move file despite using <path>/<filename>

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Executing a Move_File job using S3 agent, the file does not get moved, only give the message:
"ERROR: Possible Reason: Unable to parse Connection parameters"

The same error happens when using Copy_File.

Exist_File and Delete_File jobs work as expected. 

Moving the file to a different path in the same bucket files, and the agent log shows the following messages:

20250319/091155.075 - U02000005 Job 'JOBS.S3.MOVE_FILE.ARCHIVE' with RunID 'xxxxxxxxx' is to be started.
20250319/091155.079 - U02000003 Job 'JOBS.S3.MOVE_FILE.ARCHIVE' started with RunID 'xxxxxxxxx'.
20250319/091155.085 - U02000009 Job 'JOBS.S3.MOVE_FILE.ARCHIVE' with RunID 'xxxxxxxxx' ended with return code '80'.
20250319/091155.120 - U00029000 Report 'xxxxxxxxx' for file 'D:\Automic\Agents\bin\..\temp\PLOG.TXT' has been started.
20250319/091155.123 - U02001026 Job 'JOBS.S3.MOVE_FILE.ARCHIVE' with RunID 'xxxxxxxxx' has been removed from the job table.

Environment

Integration S3 Agent 21.2.3 

Cause

Defect

Resolution

This will be fixed in a future release of the Integration S3 Agent.

Additional Information

DE168746