MSP Project won't open after baselining - generates a We're sorry error

book

Article ID: 144208

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

  • Project won't open after baselining. It goes from writing to XML to not responding.
  • MSP eventually crashes with a "We're sorry. There seems to be a problem with this file" error. 

Cause

This can happen if the project being exported is too large for MSP to open.

Environment

Release : All Supported Releases

Component : CA PPM MICROSOFT PROJECT (MSP)

Resolution

1. See Clarity PPM MSP Interface Performance Best Practices at: 13911 to see if there are any best practices that can be used to help reduce the size of the project (durations, # of tasks, assignments, baselines, ect)

2. As of April 3, 2018 MSP Update a configuration is available to help with this issue:

  • As this requires a registry setting change, it's recommended to take a backup of the registry prior to making the change
  • See the following Microsoft article for more details on this improvement and steps to update the registry:

https://support.microsoft.com/en-us/help/4018320/april-3-2018-update-for-project-2016-kb4018320#RegKey

  • This change would need to be made on any workstation that would be opening the larger projects

Additional Information

  • List of Clarity PPM KB articles related to issues opening projects in MSP  (Article: 138671)
  • See KB: 141061 for tips on how to optimize use of Self Service for Clarity PPM
  • CA PPM and MSP integration known defects - Support Technical Document Index (KB000015956)
  • CA PPM and MSP integration - List of Knowledge Documents (KB000071385)