Project Remains Locked in PPM after Upgrading the MSP Driver

Document ID : KB000112587
Last Modified Date : 30/08/2018
Show Technical Document Details
Issue:
After upgrading PPM and switching to the new xml driver, projects now remain locked in PPM when they are saved back from MSP. The project remains locked regardless of how much time elapses between saving the project back to PPM and closing MSP.  

This did not occur prior to the upgrade when the Legacy driver was being used. 
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:
Create a backup of the registry (Select File -> Export, enter a File Name and Save). Then the values, with the exception of the (Default) value, under the MPP lookup registry key will need to be deleted. They can be deleted by selecting the values in the Name column, right clicking and selecting the Delete option. 

Alternatively, the MSP interface can be cleanly uninstalled and reinstalled. 
Additional Information:
Reference KB000045862 for steps on how to do a Clean Uninstall of the MSP Interface.
Reference KB000045303 - After Saving a Project from MSP to PPM, Project Remains Locked