Access Gateway inplace upgrade fails with duplicate files

Products

• CA Single Sign On Agents (SiteMinder)

Issue/Introduction

After a Failed inplace upgrade, Access Gateway was restored but now the installer does not pick up the install as an Upgrade, rather it continues and causes duplicate files to be created 

What are the files that the Access Gateway depends on when performing an inplace upgrade to check the version and pick up the installer as an upgrade ?

Environment

Release : 12.8.x

 

Resolution

- The zerog file is not used by the Access Gateway, it is used for any other Siteminder components such as Agent , Adminui , policy Server ... but no Access Gateway product is registered in it.

- There are multiple locations that the Access Gateway installer looks for to identify the existing installed version and determine if this is going to be an upgrade

/CA/secure-proxy/install_config_info/ca-sps-version.info

/CA/SiteMinder_Secure_Proxy/default/ca-sps-version.info

in addition to the above,  a file called "ca-install-history.log" which gets created under the user home that the installer is being executed from  which maintains also the versions of the installed Software 

/home/smuser/CA/install-info/ca-install-history.log   

- before any upgrade , it is recommended that you backup all the files mentioned above in case a restore was needed to ensure the installer will pick up the installation as an upgrade when re-executed