Project Remains Locked in Clarity after Upgrading the MSP Driver

Products

• Clarity PPM On Premise

Issue/Introduction

• After upgrading PPM and switching to the new xml driver, projects now remain locked in Clarity when they are saved back from MSP.
• The project remains locked regardless of how much time elapses between saving the project back to Clarity and closing MSP. 
• This did not occur prior to the upgrade when the Legacy driver was being used. 

Environment

Release: All Supported Releases
Component: PPMMSP

Cause

• This will happen if the registry did not get cleared out when uninstalling the legacy driver.
• The following registry may contain old values from when the legacy driver was being used:
  HKey_Current_User\Software\Niku\Schedulers|MPPLookup
   

Resolution

Option 1: Delete mpp files from workstation registry

1. Create a backup of the registry (Select File -> Export, enter a File Name and Save).
2. Go to: HKey_Current_User\Software\Niku\Schedulers|MPPLookup
3. Delete the values under the MPP lookup registry key (with the exception of the (Default) value)
   1. These can be deleted by selecting the values in the Name column, right clicking and selecting the Delete option.

Option 2: The MSP interface can be cleanly uninstalled and reinstalled.

• See KB000045862 for steps on how to do a Clean Uninstall of the MSP Interface.

Workaround: Unlock the project in Clarity

1. Navigate to the project in Clarity
2. Click the Unlock button on the project

 

Additional Information

• See KB000045862 for steps on how to do a Clean Uninstall of the MSP Interface.
• See KB000045303 - After Saving a Project from MSP to PPM, Project Remains Locked

• Clarity PPM and MSP integration known defects - Support Technical Document Index (KB: 15956)

• Clarity PPM and MSP integration - List of knowledge documents (KB: 71385)

• List of Clarity PPM KB articles related to issues opening projects in MSP  (KB: 138671)

• See KB: 141061 for tips on how to optimize use of Self Service for Clarity PPM