MSP trouble shooting: Microsoft Project(MSP) connector cannot connect


Article ID: 49035


Updated On:


CLARITY PPM FOR ITG CLARITY PPM FEDERAL CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS Clarity PPM On Premise



If MSP suddenly stops working, and was previously working(Yesterday), here is a list of items to check and trouble shoot.


If MSP suddenly stops working, first check if the issue is specific to a single-user or if it is impacting all users.

If it is impacting multiple-users or a specific Clarity instance, the list below will help your IT-Team determine root-cause.

This list is a compilation of the most common causes that can impact MSP from one day to the next.

  1. Single-Sign-On(SSO) changes

  2. Microsoft changes(Security push, patches, update)

  3. Non-Synchronized credentials (Different LDAP Server)

  4. Certificate(SSL) issue

  5. Scheduler URL in the CSA(NSA): Changed or incorrect

  6. Security changes that impact the Clarity Macro

  7. Wrong or changed Port(OOTB: Non-SSL:80 - SSL:443)

  8. IP address change(s): App-Server, or vanity URL changes

  9. Proxy-Server changes (If being used)

  10. Fire wall: Configuration change(s)

  11. Unknown Software/Security 'Push' to all end-users

  12. Load Balancer changes

  13. LDAP Synchronization/Update JOBs improperly 'Run'

In scenarios where the MSP connector is not working for multiple users and had been working the previous day.

The best action to take for resolution is to engage your internal IT-Teams.

They will be able to review any possible changes or updates that may have altered the ability for MSP to function as expected.

Keywords: MSP, connector, CLARITYKB.


Component: PROJECTS