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". Is this due to corruption during saving?
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)
Expected Results: The project is unlocked in Clarity and there is no error message upon closing MSP.
Actual Results: A target error that starts with "Target: System.Object InvokeDispMethod (System.String, System.Reflection.BindingFlags, System.Object",... referencing: "Error: Thread was being aborted" and the project remains locked in Clarity. Screenshot of error below:
This happens if you close the project quickly after the save
Expected Results: The 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. This error can be ignored and will have no impact to the data being saved back to Clarity.
Component: Clarity Microsoft Project Integration / Connector
MSP New Driver
Wait a few seconds before closing MSP (or the project in MSP) after saving. A few seconds is typically enough time to wait even with larger projects (with large xml sizes).
If you see this issue after waiting a few seconds before closing MSP or the project, see MSP interface performance slowness with Clarity. If that doesn't help, please open a case with Broadcom support.