Overview:

Occasions arise when an existing Enterprise Vault (EV) Compliance Accelerator (CA) installation needs to be changed to a Discovery Accelerator (DA) installation, or an existing DA installation needs to be changed to a CA installation.  These occasions typically occur in test lab environments, but can occur in any environment.  As CA and DA are not supported on the same server, the installed Accelerator product (CA or DA) must be uninstalled completely before the other Accelerator product can be installed.

Normally, just running the 'Add or Remove Programs' application to uninstall the Accelerator product will provide a clean uninstall.  There are instances where some as yet undetermined environment variable or variables exist that prevent a clean uninstall.  Such an uninstall can leave the Enterprise Vault Accelerator Manager Service (EVAMS) present in the Services MMC snap-in.  Manually removing the EVAMS does not allow the installation of the other Accelerator product to succeed.

Solutions:

Currently, there are two possible solutions.

Solution 1:
1) Re-install the Accelerator product that was previously installed on the server
2) Restart the server to clear any cache or buffers
3) Ensure the re-installed Accelerator product functions properly
4) Stop the EVAMS
5) Stop any other Enterprise Vault services that may be running
6) Use the 'Add or Remove Programs' application to uninstall the Accelerator product
7) Delete the installation folder (default location is C:\Program Files\Enterprise Vault Business Accelerator)
8) Check the registry to ensure the Accelerator product's registry entry has been deleted
-- for CA, the registry key that should be removed is HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Compliance Accelerator
--- if the CA Journal Connector (JC) is also installed on the machine, ensure the JC's entry in HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\External Filtering\Journaling registry key is also removed
-- for DA, the registry key that should be removed is HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Discovery Accelerator
9) Restart the server to ensure all entries are cleared from cache or buffers
10) Upon server restart, ensure the EVAMS is not listed in the Services MMC snap-in.

Solution 2:
Install the other Accelerator product on a separate server, installing all prerequisite software before installing CA or DA.