After Saving a Project from MSP to PPM, Project Remains Locked

Document ID : KB000045303
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue

After saving a project back from Microsoft Project (MSP) to PPM, the project remains locked. Sometimes a Target error is generated in MSP with the error "Thread was being aborted".

 

Symptom 1: Target Error: Thread was being aborted. Project also remains locked in PPM

This happens if the project is still saving when MSP is closed. The size of the project may impact whether this error occurs or not. (IE # of baselines, assignments, and tasks) 

Steps to reproduce using MSP Interface New Driver: 

1. Export a project from PPM to MSP 
2. Save the project back to PPM
3. Once you get the 'Project Successfully Saved' message, click OK right away, and then immediately click the top x in the right hand corner to close completely out of MSP

Expected Results: Project is unlocked in PPM and there is no error message upon closing MSP.
Actual Results: A target error is generated referencing: "Thread was being aborted" and the project remains locked in PPM. 

Capture.PNG

Symptom 2: Project remains locked after save, but there is no Target error in MSP
If your project remains locked after saving and closing MSP, but there is no target error, this is usually caused by closing the project itself in MSP quickly. 

Steps to Reproduce using MSP Interface New Driver:

1. Export a project from PPM to MSP 
2. Save the project back to PPM
3. Once you get the 'Project Successfully Saved' message, click OK right away, and then immediately click the second x in the right hand corner to close the project, but not close out of MSP entirely
 
Expected Results: Project is unlocked in PPM.
Actual Results: The project remains locked in PPM. 

Environment: 

Applies to all supported PAS environments for specified releases.

Cause:

This can happen if MSP or the project in MSP is closed out quickly after a project is saved back to PPM. The unlock process may still be running. 

Resolution/Workaround:

Wait a few seconds before closing MSP (or the project in MSP) after saving. If you do run into the issue, the data will have saved back to PPM, just unlock the project in PPM by clicking the Unlock button.