Identity Manager won't install after a successful uninstallation

Products

• DIRECTORY
• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Risk Analytics
• CA Secure Cloud SaaS - Arcot A-OK (WebFort)
• CLOUDMINDER ADVANCED AUTHENTICATION
• CA Secure Cloud SaaS - Advanced Authentication
• CA Secure Cloud SaaS - Identity Management
• CA Secure Cloud SaaS - Single Sign On
• SINGLE SIGN ON - LEGACY
• CA Data Protection (DataMinder)
• CA User Activity Reporting

Issue/Introduction

"Earlier version of CA Identity Manager has been detected" error will keep you from installing the product. This will happen if you didn't manually remove Identity Manager's registration in the .com.zerog.registry.xml file.

 

Environment

Release:
Component: IDMGR

Resolution

"Earlier version of CA Identity Manager has been detected" error will keep you from installing the product. Some customers run into this message after manually uninstalling Identity Manager. You might have used the Add/Remove Programs and successfully ran the Identity Manager un-installers. You might have even deleted all remaining files under Program Files\CA\CA Identity Manager. You remove all registry entries and yet can't install the product and are getting this error.

This is because the information that indicates the product is installed is actually located in: "C:\Program Files\Zero G Registry\.com.zerog.registry.xml". It's a hidden file so you might need to turn on the 'Show Hidden Files' option to see it. This file is holding the information about some of CA's products that have been installed. This file would be up to date with the most current version of each of the products that are regsitered.

To find the information about CA Identity Manager you should look for

<product name="CA Identity Manager" ..... ..... ..... ....

This section ends with the next closing tag:

</product>

In this section you will find information about the vendor, version and features installed in Identity Manager. So, this tells the installer that CA Identity Manager has not yet been uninstalled.

What you will need to do is the following:

• If Identity Manager is the only CA product listed in this file then you should feel safe to delete the file. You might prefer to move the file to another location until you finish up the installation before you delete it entirely.
  
  
• If Identity Manager is not the only CA product listed in this file then you should not delete the file. You will then need to edit it and simply erase the fragment that relates to Identity Manager which , as explained above, is in between <product name="CA Identity Manager" ... ... >... ... ... .. </product> . You will be best off making a backup of this file (which you should delete after successfully installing the product), then delete this fragment and save the file.

After that you should be able to run the CA Identity Manager installer.

Additional Information

If have Siteminder integrated. If run as root, the installer creates /var/.com.zerog.registry.xml. If run as the service account, it creates the file in the user’s home directory. Both files on the systems. The Siteminder web agent install must be running as root, but the IDM installs are running under the service account. Thus the 2 files with different values. ( Note - The zerog registry file in /var on the prod servers is from 2016. The correct file is in the home directory).

The com.zerog.registry.xml in the csaiags home directory contains the correct values. However the file In /var has 777 perms and that appears to be causing the installer to want to use that file.