Knowledgebase
Clarity MSP Scheduler Interface Cleanup and Reinstallation Steps
Posted by Ken Kuperberg on 09 June 2014 09:49 AM

see attachment that includes screenshots

CLARITY MSP SCHEDULER INTERFACE CLEANUP AND REINSTALLATION STEPS

Internal working document.

 

We recommend that you avoid running any of the executables mentioned below directly; instead save it in an appropriate location and “Run As Administrator” – particularly for Windows 7 (even if you are logged in as an Administrator).

(You can Right click on an executable from Windows Explorer and select the ‘Run As Administrator’ option)

 

Steps to ensure that correct version of Java is installed and referenced:

  • Ensure that the Clarity compatible Java version is installed. You can download java through Clarity under Account Settings->Software Downloads. Java can be downloaded and installed or updated from Oracle site – but ensure that the java release number is compatible. For example only Java 6 (jre1.6) should be used with Clarity 13.0 and only Java 7 (jre1.7) should be used with Clarity 13.2. It can be any patch/build number within this compatible release.

 

  • Ensure that a JAVA_HOME system variable is defined pointing to compatible & supported java release.
    • Right-click on My Computer
    • Select Properties
    • Click on the Advanced tab
    • Click on the Environment Variables button
    • Look for JAVA_HOME variable in the second section for System variables.
      • If Variable Key JAVA_HOME does not exist, click the ADD button and add it.
      • The Variable Value should point to java path

 

 

 

 

Note: Java is typically installed in the Program Files (x86) folder. There may be multiple versions of it. Please ensure that you are picking up the version compatible for your release. For example, for Clarity 13.0 the compatible java release is 6 (jre1.6). Do not use Java 7 (jre1.7) in this case. For Clarity 13.2, you need to use Java 7.

 

 

 

  • Add Java path (as noted above) to the beginning of the System Path.
    • Navigate to the Path variable under the System Variables section
    • Update the existing string (do not override) to add “%JAVA_HOME%\bin;” (without the quotes) to the beginning of the string value.

 

 

 

  • Check Registry entry to see if
    • Type REGEDIT from command prompt
    • Navigate to hkey_local_machine\Software\JavaSoft\Java Runtime Environment

(If it exists, else ignore)

  • Ensure that it points to the compatible version – For example 1.6 for Clarity 13.0 and 1.7 for Clarity 13.2

 


 

Pre-Requisites

  1. Make sure you have the following installed on your machine – If you have MSP 2007 ignore this section.

Software

Version

Download link

MSProject

Project 2010

 

MSProject2010 patch

Office-kb2075992-fullfile-x86-glb.exe

Office-kb2075992-fullfile-x64-glb.exe

http://support.microsoft.com/kb/2075992

.NetFrameWork

Version 4.0

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7&displaylang=en

Visual Studio Tools for Office runtime

Vstor40_x86.exe (If your Windows is x86)

 

Vstor40_x64.exe (If your Windows is x64)

http://www.microsoft.com/download/en/details.aspx?id=20479

 

Uninstall MSP Connect/Interface

  1. Go to Control Panel & remove the following items – MSP 2007 users will not have the CAClarityAddIn

 

 

  1. Open MS Project
  • Close the empty project automatically created
  • Go to View / Macros / Visual Basic (2007 Users: Tools -> Macro -> Visual Basic Editor)
  • Expand the ProjectGlobal (Global.MPT) Section (top left)

 

 

 

  • Expand the Modules folder

 

  • Right click on Module with Niku in the name (Niku_Api, Niku_Baseline, Niku_General, Niku_IntegrationMenu, Niku_TSD, Niku_Utility)
  1.                                                                i.      Select Remove
  2.                                                              ii.      Choose No to the export question
  3.                                                             iii.      Repeat for each Niku Module
  • Right click on CA_IntegrationHooks Module & remove
  • Close Visual Basic Window
  • Close MSP
  1.                                                                i.      If a Debug error comes up, choose debug, then delete all text and close out, choosing Yes or OK at the prompts
  • Re-Open MSP
  1.                                                                i.      if a Debug error comes up, choose debug, then delete all text and close out, choosing Yes or OK at the prompts
  • Continue to repeat until you receive no debug error

 

  1. Open Windows Explorer
  • Go to C:\ drive
  • Double click Program Files
  • Delete CA folder & CA Clarity PPM Setups –

 

  1. Go to Start Menu, and in search box type Regedit & hit ENTER

 

  • If prompted with “Do you want the following program to make changes to this computer?” Click yes and the following window comes up

 

 

 

  • Collapse all expanded folders so you are now looking at

 

  • Select/Highlight Computer
  1.                                                                i.      Go to File, Select Export, Enter File Name to store the back up of registry

 

  • Delete the following if they exist
  1.                                                                i.      HKEY_CURRENT_USER\Software\Niku
  2.                                                              ii.      HKEY_LOCAL_MACHINE\Software\Niku

For Windows 7 installation, you may need to drill down to the Wow6432 folder to get to the Niku entry.

 

  • Close/Exit Registry

 

  1. Clear Application Cache – MSP 2010 users only
  • Go to  http://www.microsoft.com/download/en/details.aspx?id=8279  Download the Windows 7 SDK file & run
  • Go to Start Menu and type cmd and click enter
  • Type cd c:\ click enter, this changes the directory back to the C:\ directory
  • Type cd
  • Then type this C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools or copy it then go to the little DOS icon in the top left corner click it, go to Edit & Paste & click enter

 

  • Type

mage.exe /cc

click enter

  • You should see a similar result message:

C:\SoftwareCopies>mage /cc

Application cache cleared.

  1. Reboot machine – not always needed but good idea

Reinstall MSP Interface from Clarity 13.0.1

  1. Open MS Project
  2. Go to File > Options > Trust Center > Trust Center Settings
  3. Make sure “Enable all macros (not recommended; potentially dangerous code can run) is selected
  4. Log into Clarity
  5. Go to Account Settings
  6. Go to Software Download
  7. Click Download link for Microsoft Project Interface
  8. Install the Clarity Add-In last – do no restart machine yet

 

  1. Ensure that the Clarity modules/addins are installed:
  • For MSP2007 installation
    • Execute C:\Program Files (x86)\CA\Clarity\CA Clarity PPM MSPInterface\data\MSPAdd2K.mpp
  • For MSP2010 installation

The Addins should be automatically installed.

If you do not see the Clarity Toolbar in MSP during the next step, then you can explicitly install the Addins as follows:

  • Execute the setup file in C:\Program Files\CA\Clarity\CA Clarity PPM MSPInterface\addIn

Folder. Remember to ‘Run As Administrator’.

Check MS Project for Clarity Interface Option 1

  1. Open MS Project
  2. On toolbar/ribbon click on “CA Clarity PPM Integration”
  3. Click “Open”
  4. Click “Setup”
  5. Check that CA Clarity PPM Host is correct for your app server
  6. Enter Test Environment password & click OK
  • If interface is working you should see messages that say it’s loading information from Clarity, this could take a couple of minutes
  1. Select a Project from the list that you know has tasks & click Open
  2. MSP should now display your tasks list

Check MS Project for Clarity Interface Option 2

  1. Log into Clarity 13.0.1
  2. Open a project with tasks
  3. Click Open in Scheduler
  4. Select Microsoft Project [Read-Write]
  5. MS Project will open and populate with the Clarity Project Task List
  6. Once it’s done loading the task list go to CA Clarity PPM Integration
  7. Click Save to ensure you can save back to Clarity
  8. If no error Success


Attachments 
 
 fixmspinstallationissues_copyc.docx (572.93 KB)
(2 vote(s))
Helpful
Not helpful