Error 126: Windows Java agent fails to start or produce logs
search cancel

Error 126: Windows Java agent fails to start or produce logs

book

Article ID: 432426

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The Windows Java agent fails to start and does not generate logs in the temp folder or a security folder in the bin directory․​‎​‌​‍​‎​‌​‍​‎​‌​‍​​‎​‌​‍​‌​‎​‌​‍​‌

While attempting to start the agent from the command line with: ucxjwx6․exe --console returns Error 126․

 

 

Error Message:

"126 The specified module could not be found. >libcpprnt/src/System.cpp#sys::System::loadLibrary:220<"

 

Symptoms:

  • Agent refuses to start via Service Manager or command line․

  • No log files are created in the agent's temp directory․

  • The Microsoft Visual C++ Redistributable appears installed but the error persists․

 

Occurs during a fresh installation or startup of the v24 Windows Java agent on a remote server․

 

Environment

OS: Windows

Agent: Windows Java Agent 24․x

Java: Java 17 (Eclipse Adoptium)

 

Cause

We have received confirmation that the solution resolves the issue. The issue is suspected to be caused by a corrupt or compromised Java Runtime Environment (JRE) installation on the host system or security software blocking access to the JRE in the default C:\Program Files location․

 

Resolution

Provide the agent a JRE that it case use. 

  1. Download a clean JRE: Download a fresh version of Eclipse Adoptium Java 17 (JRE zip file)․ Example: https://adoptium․net/temurin/releases?version=17

  2. Extract and Rename: Extract the zip file and rename the resulting directory (e․g․, jdk-17․0․x+x-jre) to exactly "jre"․

  3. Deploy Private JRE: Move the newly created "jre" folder into the agent's bin directory (C:\Automic\Agents\windows\bin)․ The folder structure should look like <AgentInstallDir>/bin/jre/bin/java․exe․

  4. Test Startup: Navigate to the agent's bin directory in a command prompt and run the console command․ Command: ucxjwx6․exe --console

    Expected: The agent starts successfully and the console output shows the correct JRE_HOME path pointing to the local bin/jre folder․

  5. Reinstall Public JRE (optional): If the private JRE works, you may choose to uninstall and clean reinstall the public Java on the system to resolve potential corruption or security blocking in C:\Program Files․

 

Verify Success:

  • Agent status shows as active in the Automation Engine (Client 0)․

  • Log files are successfully generated in the agent's temp folder․

  • Security folder is created in the bin directory upon startup․ This will happen after the Agent successfully connects to JCP. 

 

Powered by Wolken Software