AutoSys Agent Installation Fails with "Unable to allocate bitmaps for parallel garbage collection" or "Could not create the Java Virtual Machine"

Products

• Workload Automation Agent

Issue/Introduction

During a manual or silent installation of the AutoSys Workload Automation System Agent on a Windows server, the installation fails at the post-install phase. The following errors are observed in the agent installation log:

Custom Action: cybermation.iainstaller.library.CybUpdateLaxFilesStatus: FATAL ERRORAdditional Notes: FATAL ERROR - "Post-Install: Generation of additional files failed"...keytool command : cmd /c "...\jre\bin\keytool" Generating serverkeystoreError occurred during initialization of VMUnable to allocate 32768KB bitmaps for parallel garbage collection for the requested 1048576KB heap.Error: Could not create the Java Virtual Machine.Error: A fatal exception has occurred. Program will exit.Unexpected error occurred during file generation:Exception: java.lang.RuntimeException: Error invoking keytool to generate the server keystore: returncode=1

Environment

• Operating System: Windows Server (Commonly observed on Windows 2019 and 2022)
• Product: AutoSys Workload Automation System Agent

Cause

The AutoSys Agent installer includes a post-installation step that utilizes generator.jar and the Java keytool utility to finalize configuration and generate security keystores.

These child processes are launched without an explicit maximum memory (heap size) limit. By default, the Java Virtual Machine (JVM) attempts to reserve 25% of the server's total physical RAM as the maximum heap size. On high-memory servers, the JVM fails to allocate this large contiguous block of memory, resulting in the "Could not create the Java Virtual Machine" error.

Resolution

If the host operating system does not have enough memory (example: it is a 4GB memory server and 90% is already in use), increase the memory on the host and then retry the installer again.

1. Clean Up Partial Installation: Navigate to the UninstallData folder within the partially installed agent directory and run Uninstall WA Agent.exe. Ensure the target installation directory is empty or removed before retrying.

2. Run the Installer: From the same command prompt session where the variable was set, launch the Agent installer

    

3. Verify (Optional): If the error persists with a CreateProcess error=1455, consult your Windows Administrator to increase the size of the Windows Paging File (Virtual Memory), as this indicates the OS is unable to spawn new processes due to commit limit exhaustion.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.