Simple Windows job runs indefinitely - cancel throws return code '102'.

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

A simple windows job that runs:

echo

in the process tab and that is all runs indefinitely.  When cancelled, it throws the following:

20230120/144747.531 - U02000005 Job 'AGENT_TEST' with RunID '5643328' started.
...
20230120/144837.671 - U02001020 Cancel job 'AGENT_TEST' with RunID '5643328'.
20230120/144837.671 - U02001023 Cancel of job 'AGENT_TEST' with RunID '5643328' was successfully initiated.
20230120/144837.780 - U02000009 Job 'AGENT_TEST' with RunID '5643328' ended with return code '102'.
20230120/144837.812 - U02001026 Job 'AGENT_TEST' with RunID '5643328' has been removed from the job table.
20230120/144837.827 - U00029000 Report '5641863' for file 'D:\Automic\12.3\Agents\windows\temp\OAAMJCDC.TXT' has been started.
20230120/144837.827 - U00029001 Report '5641863' ended normally.

A TCP/IP =9 trace on the agent might show something like:

00000850 20230127/111938.492 - U02000009 Job 'AGENT_TEST' with RunID '5650317' ended with return code '102'.
...
00000850 20230127/111938.539 -           Could not remove file 'D:\Automic\12.3\Agents\Windows\temp\OAAMJMLX.TXT', reason '32 - The process cannot access the file because it is being used by another process. (D:\Automic\12.3\Agents\Windows\temp\OAAMJMLX.TXT) >Path.cpp#sys::Path::remove:462<'.

Environment

Release : 12.3.8

Resolution

Usually these messages are resolved by being sure that the user who starts the windows agent has all the local security policies assigned explicitly to them:
12.3 requirements
21.0 requirements

UAC should also be turned off

One user saw that after doing the above, changing the port for the agent resolved the issue.