After upgrade of WCC to 24.1 the WCC services will not start.

Products

• Autosys Workload Automation

Issue/Introduction

We upgraded the WCC from 12.1.1 to 24.1.
There were no errors or warnings in the upgrade logs.
After the upgrade was completed, the WCC services would not start

 We saw the following error in the collector.log
INFO   | jvm 1    | 2025/10/03 08:31:09 |        7 | @collector WrapperSimpleAppMain                                         []  WARN #CPSubsystem                        #(265) []:7004 [MCTVDAwiZA] [4.2.8] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
INFO   | jvm 1    | 2025/10/03 08:31:11 |        8 | @collector WrapperSimpleAppMain                                         [] ERROR #DefaultIntegrationService          #(98) Lookup for Hazelcast instance from "java:comp/env/bean/clusterInstance" failed.
INFO   | jvm 1    | 2025/10/03 08:31:12 |        9 | Oct 03, 2025 8:31:12 AM com.ca.wcc.config.db.utils.JDBCUtils getReportingDBVersion
INFO   | jvm 1    | 2025/10/03 08:31:12 |        9 | INFO: Reporting database version is 12.0.01
INFO   | jvm 1    | 2025/10/03 08:31:12 |        9 | @collector WrapperSimpleAppMain                                         [] ERROR #InitializationUtils                #(211) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO   | jvm 1    | 2025/10/03 08:31:12 |        9 | @collector WrapperSimpleAppMain                                         [] ERROR #InitializationUtils                #(212) ++++++  ERROR ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO   | jvm 1    | 2025/10/03 08:31:12 |        9 | @collector WrapperSimpleAppMain                                         [] ERROR #InitializationUtils                #(213) Local version of REPORTING (24.0.01) is different than version of REPORTING in the db (24.0.01). 
INFO   | jvm 1    | 2025/10/03 08:31:12 |        9 | @collector WrapperSimpleAppMain                                         [] ERROR #InitializationUtils                #(214) REPORTING will be stopped.

In the upgrade log we saw the following:
2025-10-03 07:39:05,655 [Thread-24398] DEBUG com.ca.wla.ae.installer.customaction.initialize.AEDBSetUpgradeList(438) - isCollector ? false
2025-10-03 07:39:05,655 [Thread-24398] DEBUG com.ca.wla.ae.installer.customaction.initialize.AEDBSetUpgradeList(442) - The database is at a lower level
2025-10-03 07:39:05,655 [Thread-24398] DEBUG com.ca.autosys.db.connection.DBOperations(81) - Running query: SELECT PREFVALUE FROM CFG_GLOBAL_PREF WHERE PREFKEY=?
2025-10-03 07:39:05,655 [Thread-24398] DEBUG com.ca.autosys.db.connection.DBOperations(191) - Query params:
2025-10-03 07:39:05,655 [Thread-24398] DEBUG com.ca.autosys.db.connection.DBOperations(195) - [1 : internal.reporting.database.enabled]
2025-10-03 07:39:05,655 [Thread-24398] DEBUG com.ca.autosys.db.validation.DBValidator(379) - DB_SETUP : isReportingDBenabled - null
2025-10-03 07:39:05,655 [Thread-24398] DEBUG com.ca.wla.ae.installer.customaction.initialize.AEDBSetUpgradeList(471) - useReporting=false

Environment

AutoSys 24.X

Cause

The WCC database did not have a record of the Reporting being enabled.

Resolution

Run the installer again, choosing to install the database schema and provide the database information and credentials for the WCC Reporting database