Automic File Transfer (JOBF) Fails with 'Available Space 0' on Windows Java Agents

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

File Transfers (JOBF) fail on target Windows systems running Automic OS Java Agent v24.4.2, erroneously reporting "not enough space on target system" with "available space '0'", even when there is significant free disk space present on the target.

Symptoms

• File Transfer objects (JOBF) configured between Windows agents (or from a Unix agent to a Windows agent) terminate with an error.
• The job report and agent log display the following error message:
  U00011482 FT '<RunID>': Not enough space on target system for file '<file_path>'. File size '<size>' > available space '0'.
• The agent log may also contain:
  U00063074 FT '<RunID>': Unable to check free disk space for path '<path>', reason '<path>'.
• This issue occurs even when the target system (e.g., a network share or UNC path like \\a\b\cd\efg\...) has ample free disk space (e.g., 119 GB free out of 300 GB).

Environment

Product: CA Automic Workload Automation - Automation Engine
Component: Automic OS Java Agents (Windows, Unix), File Transfer (JOBF) Object
Versions Affected: Automic OS Java Agents version 24.4.2 (and potentially earlier 24.x Java Agents where this parameter was ignored).

Cause

Defect ID: DE178215

Resolution

Upgrade the affected Automic OS Java Agents (both Windows and Unix) to Automation.Engine 24.4.2 HF3 or a later hotfix/service pack.

Workaround (Temporary)

As a temporary measure until the upgrade can be performed, customers can try setting ft_check_free_disk_space=no within the receiver attributes of the JOBF object. While the parameter was being ignored in affected versions, applying this setting can sometimes mitigate the issue or be part of the configuration that the fix then fully enables.