ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Windows agent won't start/write log; trustedCertFolder= has a colon


Article ID: 239092


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic One Automation


When attempting to start a version 21.0 windows agent, the agent won't start.  No log is written.

Steps to reproduce:

  1. In a 21.0.x system, identify a windows agent that starts correctly
  2. Stop the agent
  3. Update the trustedCertFolder setting to have an extra colon somewhere, for example - C:\automi:c\certs
  4. Attempt to start the agent (I attempted this from smgr, executable and command line)

    Expected behavior:
    Agent won't start, but creates a log stating why - for example, putting in an exclamation point instead of a colon throws:
         U02000327 Unexpected error on connection '*SERVER' (socket handle = '804'), reason '"category: 'asio.ssl', (337047686) certificate verify failed"'.

    Actual behavior:
    No log is created - when turning on a tcp/ip trace, no trace is created either; only the windows event viewer has a hint of why the agent won't start

Windows Event Viewer shows:
     The description for Event ID 1000 from source UC4 Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

     If the event originated on another computer, the display information had to be saved with the event.

     The following information was included with the event: 

     Reason: Unable to create 'C:\tools\ce:rts\key', reason: 267 - The directory name is invalid. >libcpprnt/src/Path.cpp#sys::Path::createDirectory:283<

Note: Java agents created logs, traces, and throw an error


This is caused by a bug with the windows agent.


Release : 21.0.2



This has been determined to be a bug and will be fixed in a future service pack