Following an upgrade of the Integration FTP Agent to version 24.1.x, jobs may fail without a clear connection-related error message. Instead of failing correctly during the authentication phase, the Agent proceeds to execute commands (such as `ls`) against the local filesystem where the agent is installed.
The Job Report typically shows local directory contents instead of the remote FTP server contents.
Copying from Local File System to CONN.FTP.NAME
copy C:\path\to\file\file_name.TXT to /../path/to/file/file_name.TXT
com.automic.agent.ftp.commands.impl.FtpFacadeCommandImpl@1234 start: getInputStream(): file: copy C:\path\to\file\file_name.TXT, skip:-1
com.automic.agent.ftp.commands.impl.FtpFacadeCommandImpl@1234 StackTrace: com.automic.agent.ftp.exceptions.DataTransferException: File copy C:\path\to\file\file_name.TXT not found.However, the Agent's log file (`ra_log_00.txt`) will contain the following specific error messages:
U00052009 UCUCM: invalid or defect encrypted value found
U02003012 An unknown message from partner 'SYSTEM#CP001' could not be processed.
U00009907 Memory view 'Received 319 bytes from SYSTEM#CP001' (Address='n/a', Length='000319')
00000000 01085543 45585F52 2020FF30 01000051 >..UCEX_R .0...Q<
00000010 55495454 20202030 31640043 420F004E >UITT 01d.CB..N<
00000020 4B000052 45535F47 45542000 00000000 >K..RES_GET .....<
00000030 00000029 CB000020 20202020 20202020 >...)... <
00000040= 20202020 20202020 20202020 20202020 > <
00000130 20202020 20202000 00000000 000000 > ........<
U00029001 Report '2862024' ended normally.
This behavior is a known defect (tracked under DE184875). The Agent does not correctly trap decryption failures when accessing the password stored in a connection object.
Instead of reporting a connection error and halting, it enters a state where it defaults to local file system operations, which can lead to confusing job reports or incorrect file processing.
Update to a fixed version listed below or a newer version if available.
Integration FTP agent 24.2.0 - TBA
Public Title:
The FTP job report displays a misleading exception if the connection object contains an invalid or corrupt entry.
Public Description:
A bug has been fixed where a wrong encrypted password in a CONN object did not cause the FTP job to fail. The Job was executed in the same way as if the CONN object was not set in the job definition.
Workaround:
To resolve the immediate job failure, recreate the affected Connection Object:
1. Locate the FTP Connection Object referenced in the failing job.
2. Open the object and re-enter the username and password.
3. Save the object.
4. Alternatively, create a new Connection Object and update the job to use it.
Article title: How to register to Broadcom Software Product updates and Critical Alerts
https://knowledge.broadcom.com/external/article?articleId=133819