WA Agent 24.1 Installation Hangs at 5% on Windows Server 2022
search cancel

WA Agent 24.1 Installation Hangs at 5% on Windows Server 2022

book

Article ID: 437552

calendar_today

Updated On:

Products

Workload Automation Agent Autosys Workload Automation

Issue/Introduction

When attempting to install Workload Automation (WA) Agent 24.1.00 on a Windows Server 2022 environment, the installation process consistently freezes or hangs at 5% during the "Installing" stage. The process may remain in this state for hours without timing out or producing an error message.

Environment

 

  • Operating System: Windows Server 2022.

  • Product Version: Workload Automation System Agent 24.1, Autosys Workload Automation

  • Security Software: Often observed in environments running CrowdStrike, Dynatrace, or Trend Micro Deep Security.

 

Cause

The issue is typically classified as an environment problem. It is often related to the default Java Runtime Environment (JRE) memory allocation being too large for the installer to initialize properly in certain restricted or monitored server environments.

 

Resolution

To resolve the hang, the installer should be executed via the command line with restricted Java memory options and, preferably, using a silent installation method.

Recommended Workaround: Silent Installation:

  1. Extract the Agent 24.1 ISO image to a local directory.

  2. Locate the sample silent property file: WA_System_Agent_24_1_00\win_installer.properties.

  3. Update the property file with your specific environment values (paths, port numbers, etc.).

  4. Open a Command Prompt as a local Administrator.

  5. Set the Java memory options by running the following command:

    set _JAVA_OPTIONS=-Xms16m -Xmx96m

  6. Execute the installer silently by pointing to your modified properties file:

    setup.exe -i silent -f "C:\fullpath\win_installer.properties" (Note: Replace "C:\fullpath" with the actual path to your file).

Additional Information

This is specific to customer environments, not really related to AutoSys but workaround is available to resolve.