Running 15.2, MSP2016, XML Interface.
First, the interface works! Cool! On simple, single projects, milestones only, project opens in MSP in about 5 seconds. Sweet! I can create tasks, assign resources, save changes back to CA PPM, the assigned hours in MSP and CA PPM match....all good.
Our projects are rarely simple, and we have a lot of bad Gantt history, where our projects were only used for milestone tracking and booking to one or a couple tasks - dozens of resources, for a year or more. And, we also have parent projects with multiple child projects.
The legacy MSP Interface always had a problem with this scenario...so, waited eagerly for the XML based solution.
Current testing shows, using scenario described above:
Any one else seeing this? Any advice (besides "Quit using MSP!)?
This is happening after trying to open a specific project but others do work, right?
If this is the case, this might need additional troubleshooting, please open a Support case.
Yes. Appears that ‘clean’ projects open well. What’s a ‘messy’ project? One with dozens of resources assigned to a single task (fast plan), booking time form a couple years or more, with a couple years or more ETC remaining.
Will contact support.
Do you have one of the supported Microsoft Project updates installed? If not, try installing the latest supported one (currently April 2017) and see if that helps. There was a new driver performance issue fixed by Microsoft in a Microsoft update. See the list of supported Microsoft Project updates with the MSP New Driver 14.4 and higher at: How do Microsoft Project monthly patches impact CA PPM?
Also, there is a Microsoft Project limitation that I've seen if the XML is larger than about 95,000 KBs. To check if this is what you are running into, check the size of the xml for the project attempting to be exported. (See KB: In MSP, what are some Best Practices to prevent Performance Issues?)
MSP2016 with latest patches, and XML interface downloaded from 15.2.
Currently, we don’t own MSP2016 – had it temporarily installed on a loaner laptop for testing – had to turn it back in.
Willing to try again, but will need to start again – another loaner, have MSP2016 installed, latest patches installed, etc.
Topic was dropped for a year. Now that MSP2016 is our standard, picked it up again and it is continued, here: MSP XML Interface - Limit on number of Assignments?
Kristin supplied the correct answer:
In the MSP New Driver, Incorrect Rate Dates Preven - CA Knowledge via discussion thread: MSP XML Interface - Limit on number of Assignments?
15.2 Patch 7 (latest as of this writing) installed and issue resolved.