Which situations cause the Microsoft Project (MSP) Project Save failed error message when integrating with Clarity? How can we identify the cause / troubleshoot?

Step 1: Review app-ca.logs

Check the app-ca.logs for related errors/warnings that can help to pointing to root cause

1. See KB: Access the app-ca.log or other Clarity Logs for how to get to app-ca.logs (for both On Premise and SaaS customers)
2. In App-ca.logs, look for Niku.Schedulers referenced in the logs
3. Check for the time frame the issue happened as their can be multiple instances/causes

Step 2: Review known causes

Below are a list of known issues related to this error. You can see if there are matches based on the symptoms and error in the app-ca.logs

Task / Summary Task Caused

• MSP Error: "Project Save Failed" due to task Start or Finish dates missing
  • "ImportTaskProcessor.doProcess(): Illegal Task Start and/or Finish dates" in app-ca.logs
• MSP Error: "Project Save Failed" if task Finish date is prior to Start date
  • "ImportTaskProcessor.doProcess(): Illegal Task Start and/or Finish dates" in app-ca.logs
• MSP Error "Project Save Failed" due to summary task start / finish date
  • • Prior to the project save failed message, you may see message "<task> in <Project Name> cannot be completed in the time allocated.."
    • "ImportTaskProcessor.doProcess(): Illegal Task Start and/or Finish dates" in app-ca.logs

• MSP Save Failed Error Due to Summary Task with Assignment
  • "Summary task configure test environment(null) cannot have assignments." in app-ca.logs
• MSP: Project Save failed even if Assignment is removed from Summary task 

General

• MSP "Save Failed" error and Unique Constraint Violation in the log
• MSP Project Save Failed Saving Local project to an existing project in Clarity
  •  "Referenced Project record (UID=xxxxxxxxxxxxxxx) does not exist" in app-ca.logs
• MSP Project Save Failed after Clarity Timeout
  • "ImportProjectProcessor.setProjectRecords(): Insufficient right to add/modify project record" in app-ca.logs
• MSP Error "Save Failed" if project has subproject
  • "ImportProjectProcessor.setProjectRecords(): Insufficient right to add/modify project record" in app-ca.logs

Resource Issues

• MSP Error "Save Failed" - "Referenced Resource record...does not exist"
  •  "ImportTeamProcessor.doProcess(): Referenced Resource record (UNIQUE_NAME=<Userabc>) does not exist referenced" in app-ca.logs

Known Defects

• MSP Project Failed to Save Error in 14.3 - If the Project Team has More than One Instance of the Same Role

Enterprise Fields

• MSP Project Save Failed due to Enterprise fields
• MSP Save Failed Due to Resource Initials incorrectly being changed - appears to happen if enterprise fields being associated on the project. 

Custom Fields

• MSP Project Save Failed in upload due to internal DuationText field
  • ImportTaskProcessor.doProcess(): Illegal Task Start and/or Finish dates referenced in app-ca.logs

Step 3: Search the general knowledge base for other known causes

• MSP Integration - Master KB of Known Issues
• MSP Integration Known Defects - Master KB
• Searching for known Clarity Issues using Self Service

If assistance is needed

Please reach out to Broadcom support for assistance. If you provide a copy of the below, this will help expedite troubleshooting:

• app-ca.logs
• copy of mpp for project with error

• See MSP Integration known issues - master KB
• See MSP Integration known defects - master KB