A File Transfer (JOBF) object fails on a Windows agent fails with java.nio.file.AccessDeniedException.

Products

• CA Automic Workload Automation - Automation Engine
• Automic Automation
• Automic SaaS

Issue/Introduction

A File Transfer (JOBF) object fails on a Windows Agent version 24.4.4 when the source directory contains a subfolder that is inaccessible to the login user. This occurs even when the "Include Sub-Directories" option is set to "No". This behavior is a regression from version 21.0.x.

The JOBF ends abnormally with the following errors in the agent logs:

• U00063030 FT '####': The file '####' does not exist.
• U00063042 FT '####': Access is denied.
• Java Exception: java.nio.file.AccessDeniedException: C:\Source\InaccessibleSubfolder

Environment

• Automic Automation 24.x
• Windows Agent 24.4.x

Cause

A defect in the agent-os-java component (DE209049) causes the agent to attempt to open a directory stream for all subfolders to build a status map, regardless of the maxDepth or subdir settings. Additionally, the file visitor sets a failure state unconditionally when encountering an access error, ignoring the abortOnError=N configuration.

Resolution

A code correction is required to ensure the agent respects the directory depth settings and error handling configurations.

Targeted to be fixed in release:

• Automation Engine 24.4.6 - TBA
• Automation Engine 26.1.0 - TBA

Public Title:
File transfer and inaccessible folders

Public Description:
A problem has been fixed that let file transfers fail on inaccessible folders.

Workaround:

1. Grant the File Transfer login user "Read" permissions to the inaccessible subfolder.
2. Move the inaccessible subfolder out of the source directory path.

Subscribe to this article to be updated on the fix status (reference: https://knowledge.broadcom.com/external/article/275360).

Additional Information

For similar behavior on Unix-based Java agents, see KB 414363.