Windows Agent fails to start with exit code 0 when UAC is enabled and a specific user is defined

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Windows Agent fails to start with exit code 0 when UAC is enabled and a specific user is defined

1. UAC is enabled
2. A windows user (with required permission) is defined in the service manager dialog properties
3. Service manager itself is started with a local user

 

Some version of the agent will start but is unable to run any jobs. You will see an error like this below:
U02000186 Report file 'C:\automic\Agents\WIN01\temp\OAADOTNF.TXT' for Job 'JOBS.WIN.TEST (1630179)' cannot be opened. Error: 'java.nio.file.FileSystemException C:\automic\Agents\WIN01\temp\OAADOTNF.TXT: Either a required impersonation level was not provided, or the provided impersonation level is invalid'.

 

Environment

Windows

Cause

This behavior is due to a defect. When UAC's "Admin Approval Mode" is active, the Service Manager—running under the Local System account—cannot correctly impersonate the defined user to launch the agent process with the required security token.

Resolution

The issue is resolved in the following versions:
*   **Automation Engine 24.4.4 HF2** (and later)
*   **Automation Engine 26.1.0** (and later)

**Important:** Both the **Windows Agent** and the **Service Manager** must be upgraded to the fixed version. Upgrading the Agent alone will not resolve the impersonation failure.

**Workaround**
If an immediate upgrade is not possible, use the following steps to bypass the impersonation issue:
1.  Open the **Service Manager Dialog**.
2.  Right-click the Windows Agent and select **Properties**.
3.  **Remove the user credentials** (User and Password) from the dialog properties.
4.  Open the Windows Services manager (`services.msc`).
5.  Locate the **Automic Service Manager** service.
6.  Change the "Log On" property from "Local System account" to **"This account"** and provide the credentials for the specific user intended to run the Agent.
7.  Restart the Service Manager service and then start the Agent.