Empty or Truncated PATH Variable on Windows Agent After Upgrade
search cancel

Empty or Truncated PATH Variable on Windows Agent After Upgrade

book

Article ID: 450876

calendar_today

Updated On:

Products

Automic Automation

Issue/Introduction

When running the Automic Automation (AE) Windows Agent version 24.4.5 while it is configured to run jobs anonymously (logon=0 + UC_HOSTCHAR_DEFAULT -> ANONYMOUS_*=Y), jobs may execute with a severely truncated process environment. Variables such as PATH and other standard user environment variables are missing, which can cause job steps dependent on these variables to fail (e.g., failure to locate executables). This article describes the cause and workarounds for this behavior.

Environment

Automic Automation (AE) Windows Agent
Versions affected: All versions built on or after Dec. 9, 2025 (e.g., 24.4.3+hf.1, 24.4.4+hf.3, 24.4.5)
OS: Windows Server (all supported versions)
Agent Configuration: logon=0 and ANONYMOUS_JOB=y

Cause

This behavior is a known regression (Defect DE209645) introduced by a performance optimization. When the agent operates in anonymous mode, the job-launch process fails to correctly inherit the system environment, causing it to fall back to a null or minimal environment block.

Resolution

The issue is targeted to be fixed in upcoming releases. See Download Broadcom products and software for steps to download the latest available release once the fix is confirmed.

Workaround: Option 1: Per-job configuration (Recommended for individual jobs)

  1. Navigate to the Windows Job object in the Automic Web Interface.
  2. Open the Process page.
  3. Locate the Use Windows OS Job Object attribute.
  4. Set the value to Yes.
  5. Save the job.

Option 2: Agent-wide configuration (Recommended for all jobs on an agent)

  1. Access the Agent installation directory.
  2. Edit the agent's .ini file.
  3. Locate the [GLOBAL] section.
  4. Add or modify the following parameter: useJobObject=1.
  5. Restart the Agent service for the changes to take effect.