ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Ms project integration issue

book

Article ID: 112045

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Getting this error message when trying to save a project open in MSP back to PPM:

<Please see attached file for image>

User-added image

The task number indicated in the error message does not exist, and the task name identified in the error message has no predecessor or successor tasks.

Environment

MSP 2013, SP 1 (x86) 
New XML Driver
MSP Update: July 2018 (MSP 2013) Update (KB4022171) 
 

Resolution

We noticed that the PM had an alternately named version of the project plan in MyDocuments, but not the normal naming convention one would expect, e.g. "PRJ400655.mpp." This led me to believe the root cause of the issue may be down to (a)synchronization between the PPM server and the PM's local machine. As a result, the end user performed the following steps (under my direction) to mitigate:

1 Launched MSP 2013 by itself
2 From MSP 2013 > CA PPM Integration (tab) > Open a Opened “PRJ400655” from Clarity server using only MSP 2013
3 Plan opened
4 Saved plan back to Clarity server via CA PPM Integration (tab)
5 Copied off, then deleted local copies of: a .mpp file in MyDocuments b Deleted Registry Entry for PRJ400655 in Regedit (pathway = Local User > Software > Niku > Schedulers > MPPLookup)
6 Launched project from Clarity and saved back through CA PPM Integration (tab) in MSP 7 Closed plan/reopened through Clarity After several round trips between Clarity and MSP, the plan appears to have stabilized, with normal open/close functionality restored. 

Attachments

1558697174707000112045_sktwi1f5rjvs16iu2.png get_app