MSP opening projects - known issues with Clarity

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

This article provides known KB articles related to problems opening one or more projects in Microsoft Project (MSP).

Resolution

Table of Contents

• Error Messages
  • Schedlink Error
  • "We're Sorry.." Error
  • Import Errors
  • Other Error Messages
• Hang Issues
  • Login issues (Hangs at Connecting to PPM)
  • Hangs at 'opening to XML' step
• Project dialog box popup
• General / Other

Error Messages

Schedlink Error

• MSP Projects do not open due to Project Server Enterprise Fields associated

"We're Sorry.." Error

Full error: We're sorry. There seems to be a problem with this file that keeps us from opening it. Please try using a backup copy if available.

Troubleshooting tips:

• Often on "We're sorry errors", reviewing the XML can help, so it's recommended to enable the XML using the steps at XML, MPP and MSP Logs for Troubleshooting MSP Issues. Once the XML is captured:
  1. Drag the XML into a Chrome browser tab
  2. Review the row that shows up at the top of the page in the error to find out which line in the XML is causing the issue. 
• Removing from the prdocument table has not been known to resolve any issues related to this error

Known Articles:

• MSP Error "We're Sorry..." opening a project due to special character issue in Notes - Seen after migrating from legacy driver to new driver. 
• MSP Project won't open after baselining - Error: "We're sorry..."

Import Errors

Troubleshooting Tips:

• Import errors are typically related to invalid data - which may include line breaks or tabs
• Often on Import errors, reviewing the XML can help narrow down root cause, so it's recommended to enable the XML using the steps at XML, MPP and MSP Logs for Troubleshooting MSP Issues.
• Removing from the prdocument table has not been known to resolve any issues related to this error

Known Articles:

• MSP Error "An Import Error Occurred..." on extended attribute - Look for the following in the XML: "
"
• MSP Error "An import error occurred" due to Task Name issue - Look for the following in the XML: "&#x0009"
• MSP Error "An Import error occurred..." / unable to open project a calendar has more than 51 characters

Other Error Messages

• MSP Error: "The last time you opened 'ProjectID' it caused a serious error..."
• Project cannot recognize this file format. Do you want to open this file as text only?

Hang Issues

Troubleshooting Tips:

• Determining where the project hangs can help in identifying a match for a known issue or what troubleshooting steps to take next. 
• Reviewing the XML may also help in determining where the project is getting stuck at
  • Is it blank (not loading XML at all)?
  • Does it fully load (there is a </Project> at the end of the XML)?
  • Does it partially load (stop at a certain task, assignment, etc)? If so, check that particular task, assignment, etc for a possible issue on the Clarity side that may be causing the issue. 
• What is the size of the XML? Do smaller-sized XMLs load okay? (To determine a possible performance issue)

Login issues (Hangs at Connecting to PPM)

• Opening MSP stops at 'Connecting to PPM' step (if using a Proxy)
• Opening MSP stops at 'Connecting to PPM' step if using LDAP

Hangs at 'opening to XML' step

• MSP project won't open - hangs on opening XML intermittently
• MSP Project hangs on opening to XML for a project recently baselined in Clarity
• MSP downloading gets stuck at opening xml - error: "serious error"

Project dialog box popup

• Clarity Project will not open in MSP - Project dialog box pops up due to MSP Update not being installed

General / Other

• Unable to open a master project in MSP (popup window appears) - due to a calendar associated with the project having more than 51 characters
• Save As window appears when trying to open a project in MSP
• MSP Interface stopped opening projects from Browser
• MSP Project crashing/performance issues on one project due to tasks with start/finish dates far out in past or future
• Projects open up blank in MSP due to an incorrectly formatted NSQL query

Additional Information

See also: MSP Integration known issues - master KB