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.
This behavior is observed in AE Windows Agent 24.4.5 due to changes in the default job-launch path. When the agent operates under a specific account without explicit configuration for Job Objects, the process environment provided to executed jobs is significantly reduced.
Resolution:
We are investigating via DE209645. At this time, we anticipate a fix for this issue in version 24.4.6 and 26.1.0.
Workaround:
Option 1: Per-job configuration (Recommended for individual jobs)
Option 2: Agent-wide configuration (Recommended for all jobs on an agent)
.ini file.[GLOBAL] section.useJobObject=1