MSP Project Save Failed after Clarity Timeout

book

Article ID: 138534

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

I am receiving a project save failed error after my session times out for Clarity when trying to save my project back from Microsoft Project (MSP).

Steps to Reproduce: 

  1. Open a Project in MSP and stay inactive in Clarity for more than the SSO Timeout
  2. Attempt to save the Project back to Clarity  through MSP

Results: Since the session has been inactive MSP requests for Login credentials. Entering in the believed password (LDAP Password) the password is not accepted and receive the save failed error. 

Errors seen in app-ca.logs:

ERROR 2019-10-07 15:42:14,955 [http-nio-14001-exec-482] directory.LDAPDirectoryService (clarity:unknown:none:schedulers.loginScheduler) 

Authentication failed for::cid=admin... :due to this reason::[LDAP: error code 49 - Invalid Credentials]

WARN 2019-10-07 15:43:16,617 [http-nio-14001-exec-488] niku.schedulers (clarity:unknown:none:schedulers.postProject) ImportProjectProcessor.setProjectRecords(): Insufficient right to add/modify project record

Cause

This issue can be due to providing an incorrect password. If you are a SaaS customer and behind the Portal: 

  • If External Authentication is checked, the application would be looking for the user's password for logging in to the Portal
  • If External Authentication is unchecked, the application would be looking for the Clarity user's password

As referenced in the following link, if you are using federated single sign-on (SSO), you must have an open Clarity  browser session. This browser session must be in the environment to which you are trying to connect, which is defined in the CA PPM Host field. See more details at: MSP: Install and Configure the Microsoft Project Interface

Environment

Release : All Supported Releases

Component : CA PPM MICROSOFT PROJECT (MSP)

Resolution

To avoid the timeout: 

  1. Increase the Portal SSO timeout to the default of 120 mins and increase the Clarity Timeout to 119 minutes, as that will give more room for Project Managers to update their Project Plans. 
  2. Keep the session alive by keeping an active Clarity browser window open. 

If you do face the login timeout issue:

  1.  Save a Local Copy of the plan and upload it later. (Make sure to keep the project locked in Clarity if at all possible to avoid other users from updating the project in MSP or Clarity which can cause changes to be overwritten 

OR


       2. Log in with one of the below passwords depending on how External Authentication is configured:

    • If External Authentication is checked, the application would be looking for the user's password for logging in to the Portal
    • If External Authentication is unchecked, the application would be looking for the Clarity user's password

Additional Information

For other causes of the Project Save failed error see: MSP Project Save Failed Errors - Master KB

Clarity MSP Support Document Indexes: