Clean uninstall of the MSP interface
search cancel

Clean uninstall of the MSP interface


Article ID: 45862


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


How do you do a clean uninstall of the Clarity Microsoft Project (MSP) Interface / Integration? 


Releases: All Supported Releases


Sometimes, due to permission restrictions or other issues on the machine, some of the MSP components do not get uninstalled on their own. If that is the case, a manual uninstall is needed to remove the remaining components. Doing a clean uninstall / install is especially recommended if running into issues during an upgrade of the MSP Interface. 


Step 1: Uninstall the MSP Interface components

Uninstall the following MSP Interface components from Control Panel. If there are any duplicates of any of the components delete those as well:

  1. CA PPM Microsoft Project Interface 
  2. CA PPM Schedule Connect
  3. CAClarityAddin
  4. Open Workbench (if installed) - Note, prior to uninstalling OWB, if you have any custom views for OWB, make sure to save these in a separate folder prior to the uninstall.

Step 2: Clean out the Registry

Note: Some of the keys may not exist; also, deleting each key will correctly delete all of their subkeys.

  1. On the workstation, go to Start and type 'regedit' in the search field.
  2. Select regedit.exe
  3. Select File -> Export and enter a File Name to store the back-up of the registry
  4. Once finished creating a backup, delete the following keys if they exist:  
    • HKEY_CURRENT_USER\Software\Niku

      1. Expand the HKEY_CURRENT_USER folder

      2. Expand the Software folder

      3. Then scroll down and check if Niku exists. 

      4. If yes, right-click the Niku folder and delete it

    • HKEY_LOCAL_MACHINE\Software\Niku
      Note: You may need to drill down to the Wow6432 folder to get to the Niku folder depending on your bit level: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Niku

      1. Expand the HKEY_CURRENT_USER folder

      2. Expand the Software folder

      3. Scroll down and check if Niku exists.

      4. If not, also expand the Wow6432Node folder and see if Niku exists there.

      5. If yes, right-click the Niku folder and delete it

        The file path in the registry for 32 bit: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Niku

Step 3: Clear out folders

Delete the following folders if they are still listed: 

  • C:\CA\CA PPM MSPInterface

  • C:\CA\PPM Setups

  • C:\CA\PPM\CA PPM Schedule Connect

Note: The folder location is dependent on where the MSP Interface was installed:

  • If you installed the 32-bit Interface, the folders may be instead found in C:\Program Files (x86)

  • If you installed the 64-bit Interface, the folders may be instead found in C:\Program Files

Step 4: Clean out Visual Basic

  1. In MSP, go to View > Macros > Visual Basic 
  2. Expand ProjectGlobal
  3. Expand Modules
  4. Delete the modules that start with either CA_ and Niku_ (Right-click the module and select 'Remove ...' )
  5. Click ‘No’ to the message that pops up ‘Do you want to export <Module Name> before removing it?’ (The message is asking if you want to export the files, which is not needed)
  6. Expand Microsoft Project Objects
  7. Double-click on Thisproject
  8. Select everything in the right panel and delete it
  9. Save and exit Visual Basic

Step 5: Verify the Trust Center Setting

Verify the correct Trust Center Setting is set:

  1. Go to File > Options> Trust Center > Trust Center Settings

  2. Make sure "Enable all macros" is selected

Step 6: Reinstall the MSP Interface

  1. Ensure the bit level of the MSP Interface being installed matches that of MSP. See KB MSP bit level installed - steps to determine for more details.
  2. Make sure the MSP Interface version being installed is the same version and patch level as that of Clarity. The correct downloads can be found in Clarity by going to Home->Account Settings->Software Downloads.
  3. If using a proxy, reenter the Proxy Host and Proxy Port in the setup window in MSP. See the steps to renter proxy details found in KB: Opening MSP stops at 'Connecting to PPM' step

Additional Information

Reference also: MSP Integration - Master KB of Known Issues