Error U02000186 and U02001007: Windows Jobs hang in background unable to interact with desktop prompts

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Windows jobs that require user interaction with desktop prompts hang indefinitely in the background without displaying the application interface․​​​​​‌​‍ This occurs because the Windows Agent running as a service operates in Session 0, which isolates it from the interactive desktop user session ․

 

Environment

OS: Windows Server
Product: Automic Automation Engine 24․4․1
Component: Windows Agent (Java) 24․4․3

 

Cause

Windows OS Session 0 isolation prevents services from interacting with user desktops․ When the Automic Windows Agent runs as a Windows Service, it executes in Session 0, forcing all launched applications into the background where users cannot see or interact with them․

Resolution

Prerequisites: 

• Access to Client 0

• Administrator access to the Windows server hosting the agent

   

   

STEPS:

1․ CONFIGURE THE AGENT INI FILE

Path: [Agent-Directory]\bin\ucxjwx6․ini

Update the logon parameter to 0: logon=0

EXPECTED: The agent configuration updates successfully․

 

2․ UPDATE THE HOST CHARACTERISTICS

Navigate to Client 0․ Open the UC_HOSTCHAR_DEFAULT VARA object․ Change the value of ANONYMOUS_JOB from N to Y․

EXPECTED: The system saves the variable update․

 

3․ RECONNECT THE WINDOWS AGENT

Disconnect the Windows agent from the Automation Engine․ Allow the agent to reconnect so it registers the updated UC_HOSTCHAR_DEFAULT settings․

EXPECTED: The agent reconnects and applies the anonymous job configuration․

 

4․ CREATE A LOGIN OBJECT WITH BLANK PASSWORD

Create a new Login object for the job execution․ Leave the password field completely blank․

EXPECTED: The system saves the Login object without a password․

 

5․ START THE AGENT INTERACTIVELY

Log into the Windows server via a Remote Desktop (RDP) session using the account intended for job execution ․ Open a command prompt․

Execute the agent directly from the console: ucxjwx6․exe --console

EXPECTED: The agent starts in the active user session rather than Session 0․ NOTE: You can disconnect the RDP session, but do not sign out, to keep the session active ․

 

6․ EXECUTE THE JOB

Run the interactive Windows job using the newly created Login object․ Ensure the Job is configured with the following attributes:

• Interpreter Type: Command (cmd.exe)
• Command: The command that will launch the interactive process you want to run (ex: notepad.exe)
• View Job on Desktop: Normal

EXPECTED: The application launches in the foreground of the active desktop session, allowing user interaction․ 

 

VERIFY SUCCESS:

• The application GUI or prompt appears on the Windows desktop for interaction․ On Windows Server 2019, Task Manager has groups of processes (Apps, Background Processes and Windows Processes). In order for that application to be interactive - it needs to be seen as running under the Apps section. If it's shown in/under Background Processes - it will not be something you can interact with.

 

 

Additional Information

Microsoft implemented Session 0 isolation specifically to resolve security vulnerabilities․ Applications that still require interactive desktop access while running from a service are considered legacy applications by Microsoft and should be updated by their developers to run without interactive prompts.