Baselined projects cannot be opened with MSP 2013 SP1, user receives a Visual Basics run-time error '91'

Products

• CLARITY PPM FOR ITG
• CLARITY PPM FEDERAL
• Clarity PPM SaaS - Application
• Clarity PPM On Premise

Issue/Introduction

Symptom:

After applying SP1 on MSP 2013, a project can no longer be launched to MSP from Clarity if that project has a baseline.

Project starts to load in MSP, but then gives the following error message:

Run-time error '91':
Object variable or With block variable not set

Note: The Project Management User Guide for Clarity 13.2 and 13.3 do not mention whether or not MSP 2013 SP1 is supported.

Environment:

Any local client environment using the CA PPM Legacy MSP Interface and MSP 2013 Service Pack 1.

Resolution:

Roll back to MSP 2013 without any Service Packs.

Due to the timing of when it was released, MSP 2013 Service Pack 1 has not been tested with the CA PPM Legacy MSP Interface. Since it has not been tested, this also means that it is not supported.

Do not apply Service Pack 1 to Microsoft Project 2013 if you are using the CA PPM Legacy MSP Interface.

Microsoft Project 2013 Service Pack 1 is supported for integration with the new CA PPM Release 14.2+ MSP Interface option.

Additional Information:

Reference the Change Impact and Upgrade Guide for CA PPM 14.1, 14.2, 14.3

To help identify the exact supported service packs on a MSP version, the Project Management User Guide includes the supported service pack levels for each MSP version.

Reference TEC615024: All the actuals are zeroed out when launching a project from Clarity to MSP 2013 with SP1

 

Environment

Release: ESPCLA99000-13.2-Clarity-Extended Support Plus
Component: