MSP New Driver: Project hangs opening even though XML appears to fully load

Document ID : KB000103986
Last Modified Date : 21/02/2019
Show Technical Document Details
Some projects will not open in Microsoft Project (MSP) when exporting from Clarity PPM with the MSP New Driver. They hang on opening, and there are no errors or warnings generated in the MSP Logs folder in Libraries/Documents. 

If you review the XML related to the problem project, the XML appears to fully load as there is a </Project> tag at the end of the file. (For steps on how to enable XML if it is not being generated automatically in the workstation's documents folder, see KB000099202.)
This issue appears to apply to certain Microsoft Project updates including using MSP 2013 SP1 with the March / April 2018 updates and MSP 2016 with February / March 2018 updates. 
This issue is due to using an unsupported method of copying and pasting tasks in MSP (highlighting of an entire row and pasting it). This copies the Text3 data that contains task unique information into the second task.

Avoidance: Use the supported method of copying and pasting of tasks in MSP when working with CA PPM documented at: KB000010395


Option 1: Run the below query to temporarily remove the project from the prdocument table. (For On Demand/SaaS customers, please open a case to have this done):


  • MSP Legacy Driver: All custom views for the project will be deleted
    • ​When the project is opened from PPM after the update, the project will only open with the default columns set for the view.
    • Users will have to recreate their views for the project, unless they have them saved in MSP. (This doesn't apply in the new driver, as views are no longer saved. Users should always save the views on their MSP and switch to that view after the project opens).
  • Any custom field data not mapped to PPM will be deleted from the project. This only impacts data entered in a MSP Field (such as a text field) and that data isn't stored in PPM. This impacts both the MSP New Driver and MSP Legacy Driver.
  • MSP New Driver: All Fixed Work tasks will currently change to Fixed Units.  The user will need to manually change all applicable tasks back to Fixed Work the next time the project is opened in MSP.

Run the below query:

update prdocument

set prrecordid = ?? where prrecordid=?

and prtablename= 'PRJ_PROJECTS'


1. Replace the ? with the 5 million number of the project. For ?? change the 5 to a 9. This will create a backup of the record in the database.

2. Run the below query to ensure that there is not already a project with the ?? prrecordid:

        select * from prdocument where prrecordid = ??

3. To find the 5 million number for the project, you can run the below query (or it can be found in the PPM URL when clicking on the link to the project from the project list) 

 select id from inv_investments where name='<project name>' and object_type = 'PROJECT' 

Option 2: Downgrade to the Microsoft Project February 2016 update as this issue is not reproducible there.
  • Notes: 
    • While this update is supported in 14.x and higher, downgrading to this update causes risks of other issues that Microsoft has fixed in updates higher then February 2016, so downgrading should be used with caution and only after testing for any side effects. 
    • For details on supported MSP Updates with CA PPM, see KB000011553
Additional Information:
Other known issues related to opening projects in MSP:
  • In the MSP New Driver, projects will not open if their are enterprise fields linked to the project (TEC1363954)
  • In the MSP New Driver, Unable to open a project in MSP if a Calendar associated with the project has more than 51 characters (TEC1532415)
  • Project opened in MSP2013 throws Schedlink MFC Application has stopped working error (TEC1875866)
  • In the MSP New Driver, Incorrect Rate Dates are being Exported, Preventing Projects from Opening (TEC1308499)
  • MSP New Driver: Project hangs when opening at "writing to XML" step due to a defect fixed in 15.4. (KB000009080
  • MSP Error: 'We're sorry. There seems to be a problem with this file' due to issue with Notes (KB000091838)
For other related MSP CA PPM issues:
  • Reference KB000071385 - CA PPM and MSP integration - List of Knowledge Documents
  • Reference KB000015956 - CA PPM and MSP integration known defects - Support Technical Document Index