Projects open blank in MSP new driver due to an incorrect MSP Mapping Field Name

Document ID : KB000031067
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When opening projects from PPM in the new Microsoft Project (MSP) driver, all projects are opening up blank, though the Project ID appears as the file name. The error in the mspxml_general.log states: Assertion fails in ..\caMsputil\MSPAttributeEnum.cpp

Steps to Reproduce:

1. Log in to Clarity PPM. 

2. Navigate to a project that has tasks. 

3. Open the project in MSP.

Expected Result: Project opens successfully displaying tasks.

Actual Result: Project opens with no data, only the Project ID appears at the top. The mspxml_general.log mentions: Assertion fails in ..\caMsputil\MSPAttributeEnum.cpp

Note: You can find the mspxml_general.log on the user's workstation in the CA\Clarity\CA Clarity PPM MSPInterface\bin\logs folder

Solution:

In PPM, go to Administration -> MSP Field Mappings (under Project Management) and check for any incorrect MSP Field Names in the Clarity PPM MSP Field Names section including:

1) Check for any leading or ending spaces in any MSP Field Name (Example ' Text1' versus 'Text1'). One way to check for this is by sorting by MSP Field Name in Clarity PPM. Any MSP Field Names that do not sort correctly would indicate there is a space incorrectly being used.

2) Also, check for any capitalization incorrectly used in the mapping name. MSP Field Names should only have the first letter of each word capitalized. (Example TEXT1 should be Text1)

This issue should only occur if you created MSP Mapping prior to 14.1 in the Database. Clarity PPM will not allow you to create MSP Field Names incorrectly in the UI, you will get an error when saving your MSP Field in Clarity PPM: "The MSP Field name is not among the allowed names: Cost1-10, Date1-10, Duration1-10, Finish1-10, Flag1-20, Number1-20, Start1-10, Text1-30."