Client Automation - Content Download job shows ERROR

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

Default Software Contents Download job shows ERROR after every execution, few validations are made and everything seems correct:

- Connectivity with content server is OK.

- Connectivity against the MDB is also OK.

- Latest patches are visible on Patch Management.

- Latest signatures can be seen updated on Domain Manager.

- Unlinking and Linking the task again still keeps showing error after every execution.

- Changing the job to another Engine result in same error.

Environment

Client Automation - All Versions

Cause

Reviewing Engine logs after the task is executed shows the task is being executed correctly:

2020-11-24 09:43:21 Engine Started
2020-11-24 09:44:26 Performing Job:Default Software Contents Download Job
2020-11-24 09:44:26 MDB,1433
2020-11-24 09:44:26 DM.server.name mdb MDB.server.name 1433 MDB
2020-11-24 09:44:26 Engine running on manager.

Checking CIC logs shows the execution is made correctly:

[CCMain] INFO [com.ca.sccc.CCMain] - ****** CIC cycle: 8 started ********* [CIC version: 14.0.2000.0199 (I201703151749D)]
[CCMain] INFO [com.ca.sccc.CCAcmeClient] - Entered into method : checkstatus()
[pool-9-thread-1] INFO [com.ca.sccc.CCAcmeClient] - Connecting to Content Server from: <ServerName> Applications: DSM UPM Application Ids: B1B13849-08D1-4DA6-91EA-2D278E5F00CC 682DCD15-5C94-4321-842D-E3944D3CA000
[pool-9-thread-1] INFO [com.ca.sccc.CCAcmeClient] - Server - URL: contentupdate.broadcom.com/192.19.232.217 Port: 443 Https: true

[CCMain] INFO [com.ca.sccc.CCMain] - ** Processing messages for domain 'MDB.server.name' (Connection 'jdbc:sqlserver://MDB.server.name:1433') **

[CCMain] INFO [com.ca.sccc.dbm.CCDBManager] - Starting uninitialization of MDB connection pool for domain 'MDB.server.name'

[CCMain] INFO [com.ca.sccc.CCMain] - Cycle 8 completed with status: OK. Elapsed time 1 minutes.

But when running the job manually, the following message can be seen:

Which is also seen on Wrapper log:

STATUS | wrapper | 2020/11/24 09:44:28 | Launching a JVM...
INFO | jvm 1 | 2020/11/24 09:44:29 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2020/11/24 09:44:29 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
INFO | jvm 1 | 2020/11/24 09:44:29 |
INFO | jvm 1 | 2020/11/24 09:44:29 | [com.ca.sccc.CCMain] - Another CIC is already running, aborting
STATUS | wrapper | 2020/11/24 09:44:31 | <-- Wrapper Stopped

Resolution

That message means that CIC is already running by a previous execution but it never ended successfully.

CIC is a Java application, so when it's manually started, a new Java instance starts on Task Manager, triggered by the logged in user:

And when it ends successfully, this instances stops by itself:

If this doesn't happening, the following procedure can be followed:

1.- Unlink Content Download job from Engine.

2.- Kill any Java.exe that is currently running on DM server (where CIC is installed), verifying first that none of them correspond to a critical system running on the server.

3.- Link the task Again to the Engine.

4.- Start the job from the Engine or manually from CMD.