search cancel

R12 Full Client Upgrade only upgraded client but not system Agent

book

Article ID: 203214

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE

Issue/Introduction

Customer tried to upgrade their 11.3.6 SP8 client+agent install to r12.0.  Only client seems to be getting upgraded but not the Agent.

Environment

Release : 12.0

Component : CA Workload Automation AE (AutoSys)

Cause

Agent installation customer performed was using the Agent Only install, while the Client was using the Client/Autosys ISO image.

In 11.3.6 release, the client is 32bit.   Agent install performed via the client/server ISO image would also be 32bit.  Such 32bit Agent boxes would contain a registry entry like this:

 HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ComputerAssociates\Unicenter AutoSys JM\11.3_base\Agent

 

However if you install the Agent using Agent Only module,  one could install the 64bit version of the agent.  In such a case, the above registry entry is not present. When r12.0 Upgrade is performed, it tries to look for the above 32bit registry entries. If it cannot find it, it cannot upgrade that agent module.

 

Resolution

If the Agent install performed was using the Agent Only software,  that agent cannot be upgraded by the same r12 Client/Server ISO.

 

It has to be installed using the 12.0 Agent Only ISO.

 

On a machine that contains 11.3.6 (32bit) client +  11.x Agent (64bit using Agent Only ISO),  you would have to upgrade the modules separately using 2 different r12 ISOs.

1) r12.0 Client/Server ISO (which will upgrade the client)

2) r12.0 Agent Only ISO  (which will upgrade the agent)