Windows Remote Agent not starting after CAU to version 24.3

[Cristian Suciu]

We upgraded our AE to version 24.3. Now we tried upgrading a Windows and an SAP remote agent via CAU.

The Upgrade deployment for Windows agent finished and it generated JCP certificates but the agent is no longer starting from Service Manager Dialog and it generates no Log.

The only thing we see is in the Service Manager log when we try to start the agent from SMD:

20250318/143455.159 - U00022004 Starting process 'LA0UC401_TEST' ...
20250318/143455.159 - U00022005 ... with command line  'D:\AE_TEST\Agents\windows_1\bin\UCXJWX6.exe'.
20250318/143455.159 - U00022006 ... and start directory  'D:\AE_TEST\Agents\windows_1\bin'.
20250318/143455.185 - U00022007 Process 'LA0UC401_TEST' (ID '12324') successfully started.
20250318/143455.995 - U00022012 Process 'LA0UC401_TEST' (ID '12324') ended.
20250318/143455.995 - U00022022 Process 'LA0UC401_TEST' ended, exit code='1'.

Looks like the ini file did not get modified during the CAU.

Thanks 

Cristian

[Peter Daransky]

Hi Christian, 
if there is no log, think best way how to find out what's wrong is to logon to the machine and try to start it from command line on the same way as the Smgr is doing. Like this:

cdD:\AE_TEST\Agents\windows_1\bin
UCXJWX6.exe

If it still unclear what's wrong, you can try to start it in console mode: UCXJWX6.exe --console (used for dbg purposes), to get more output ... 

BR p

[Markus Embacher]

Hi Cristian,

just a side note: are you using a self signed certificate or a CA signed certificate? Only in case you are using a self signed certificate you would want CAU to distribute the certificate to the agent. In case you are using a CA signed certificate you want the agent to use a CA root certificate that is present on the server. In that case set CAU_INCLUDE_SERVER_CERTIFICATES in UC_SYSTEM_SETTINGS to N in order to prevent CAU from deploying the server certificate to the agent.

From the log snipped you shared it is not possible to find out what was the root cause of the agent not starting up. For analysis please start the agent from the command line using the --console parameter to show diagnostic information.

https://docs.automic.com/documentation/webhelp/english/AA/24.4/DOCU/24.4/Automic%20Automation%20Guides/Content/InstallAgents/InstallAgentWindows_Java.htm

Example:

ucxjwi6.exe --console

Regards, Markus 

[Cristian Suciu]

Hi Markus,

We have CA certificate and I have the pem file from the AE host. I put it in a keystore folder in the Agents folder and added that path in the trustedCertFolder of the ini files. 

For the SAP agent this was successful and the remote agent got upgraded and connected to AE on version 24.3

But for the Windows server it looks like the command isn't even working when trying to start it from SMD. Its working when the agent is on 12.3.3 but not working once the agent gets upgraded by the CAU. 

Looking into running the .exe in console mode I can see the agent is getting the JRE from the Java path but I have Java 11 installed separately and for the SAP agent I added in the SMD file to take the path of the Java 11 instead of Java Home. I do not want to affect other processes hosted on the same server by changing Java Home to 11 instead of 1.8
Is there anyway I can force the Windows agent to use Java 11 instead of Java Home?

Thanks

Cristian

[Peter Daransky]

Hey, 

in this case you can copy the wanted JRE into Agent\bin folder and call the directory jre, like this: 

xcopy /E "c:\Program Files\Eclipse Adoptium\jdk-21.0.4.7-hotspot" D:\AE_TEST\Agents\windows_1\bin\jre

or, create a link 

mklink /D D:\AE_TEST\Agents\windows_1\bin\jre "c:\Program Files\Eclipse Adoptium\jdk-21.0.4.7-hotspot"

Is the same as if you would install the Agent from CAU Package with provided JRE ... 

br p 

[Cristian Suciu]

I wanna thank you for the valuable inputs provided. This was extremely helpful and I managed to upgrade both SAP and Windows agents with this. 

For the SAP agent I added the java 11 path directly in the uc.smd file.

For the Windows agent I created jre folder in the bin folder of the agent and the exe found it and considered that as the JAVA Path instead of what we have in environment variables. 

This is valuable information that I learned today that will certainly help us when upgrading the production agents. 

Cristian

[Carlos Cardano]

Hello Christian,

Is the CAU successful for your set up where you have 1 Service Manager hosting 3 Agents?

------------------------------
Regards,
Carlos
------------------------------

[Cristian Suciu]

I was successful, but after triggering the CAU I had to modify the uc4.smd file manually to get the proper java version.