Master KB related to Microsoft Project (MSP) Project Save failed error message when integrating with Clarity PPM, including steps to troubleshoot. 

Release : All Supported Releases

Component : CA PPM SAAS MICROSOFT PROJECT (MSP)

Step 1: Check the app-ca.logs for related error/warning that can help to pointing to root cause

1. See KB: KB000113183 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: Check the below articles to see if they are matches based on the error in the app-ca.logs

1. KB000044475 - Unable to Save Projects back to PPM from MSP if the Project Team has More than One Instance of the Same Role
2. KB000005264 - MSP Save Failed error due to task Start or Finish Date issues in MSP
3. KB000008031 - In MSP, receive a "Save Failed" error referencing a Unique Constraint Violation in the logs
4. KB000100653 - MSP New Driver Project Save Failed Error due to Summary task scheduling / Start Finish Date issue
5. 129049 - MSP Save Failed Error Due to Summary Task with Assignment
6. 142429 - MSP: Project Save failed message even though assignment was removed from Summary task

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

1. See KB 141061 - How to search for known Clarity PPM Issues using Self Service
2. KB000071385 - CA PPM and MSP integration - List of Knowledge Documents
3. KB000015956 - CA PPM and MSP integration known defects 

KB000071385 - CA PPM and MSP integration - List of Knowledge Documents
KB000015956 - CA PPM and MSP integration known defects 
See KB 141061 - How to search for known Clarity PPM Issues using Self Service