Getting error -1073741502 when trying to run batch file on windows server

[BEN BAEZ]

I have a Windows server that we recently upgraded the agent from 21.0.11 to 24.4.0. Everything appeared to go smoothly in the upgrade. However any batch job running on the upgraded windows agent shows it completed successfully in the Jobs Executions list; but the REP log is empty and, in the agent log we see the message "ended with return code '-1073741502'."

I came across another thread from Feb with the same issue that doesn't have a resolution; but my permissions don't let me reply to it for some reason.  Getting error -1073741502 when trying to run batch file on windows server | Automic Workload Automation

We also have upgraded 24.4 SAP & SQL agents on this windows server that are executing and logging jobs successfully. The issue so far just appears to be with the windows agent. I redeployed a 21.0.11 windows agent and it is behaving as expected. Has anyone (especially the poster of the thread from Feb) determined the cause of this issue with 24.* windows agent? Thanks

[BEN BAEZ]

We were able to determine the cause which seems to be a combination of things. This issue seems to stem from the newer windows agent ignoring the credentials in the login object.

 

 

When the agent starts up we see that it is not using the defined account, but instead is using the BUILTIN\Administrators account

 

 

The agent starts and appears to be running but no jobs actually get executed and in the logs we see the original message I started the post with.

 

U02000009 Job 'JOBS.VERIFY_WINDOW' with RunID '1126014' ended with return code '-1073741502'.

 

We determined this code related to code trying to interact with the desktop. So this led to the CAU settings.

 

 

Our security requirements don't allow us to change this setting so In order to get the new windows agent to function I needed to change the login account for the service manager to use the desired service account which seems to defeat the purpose of the login object.

 

Before:

 

After:

 

 

This hasn't impacted the functioning of any of the other agents and I could find any reference to the change in login behavior. Hopefully this information helps someone else