Residual registry keys prevent installation of CA Harvest SCM client

Products

• CA Harvest Software Change Manager

Issue/Introduction

When upgrading or reinstalling the CA Harvest SCM client on Windows, the installer may fail or report that a previous version is still present. This occurs even after a standard uninstallation via the Control Panel if residual registry entries remain on the system.

Environment

CA Harvest Software Change Manager (SCM) version 12 or 13 upgrading to 14.5
Windows 10, Windows 11, Windows Server 2016 and higher

Cause

The standard uninstaller may not remove all registry keys, particularly the ComputerAssociates\SourceSafe or ComputerAssociates\Harvest nodes within the WOW6432Node on 64-bit operating systems.

Resolution

To resolve this issue, manually clear the residual registry keys using the following steps:

Open an administrative command prompt. Run the following commands to delete the relevant registry nodes:

@echo off
REM Remove main product keys
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\SourceSafe" /f
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Harvest" /f

REM Remove 32-bit keys on 64-bit systems
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ComputerAssociates\SourceSafe" /f
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ComputerAssociates\Harvest" /f

Then restart the installer for the new version of CA Harvest SCM.

If the issue persists, see Contact Broadcom Support for further assistance.