After saving a project back from Microsoft Project (MSP) to Clarity, 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 Clarity
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:
Expected Results: Project is unlocked in Clarity 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 Clarity. Screen shot of error below:
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:
Expected Results: Project is unlocked in Clarity.
Actual Results: The project remains locked in Clarity.
This can happen if MSP or the project in MSP is closed out quickly after a project is saved back to Clarity. The unlock process may still be running.
Component: Clarity Microsoft Project Integration
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 Clarity, just unlock the project in Clarity by clicking the Unlock button.