All projects locked by single user in Clarity

book

Article ID: 140610

calendar_today

Updated On:

Products

STARTER PACK-CLARITY PPM Clarity PPM SaaS

Issue/Introduction

All clarity projects are locked in the application. 

Cause

One reason this can happen is if the Autoschedule Project job was run against the projects without the parameter PUBLISH AFTER SCHEDULING being checked. If this option isn't checked all projects will remain locked. 

To verify this is the cause:

  1. Go to Home->Reports and Jobs
  2. Click on Jobs
  3. From the Jobs tab drop down, select Scheduled Jobs
  4. Filter for *Auto* in the job name
  5. Click on the instances of this job that have completed.
  6. Check the Project and OBS field. If the OBS field has a value, all projects in the OBS would have been updated. If both the project and OBS field are blank, all projects in the application would have been impacted. 
  7. Scroll down and check to see if Publish After Scheduling is unchecked

Note: The above is depended on whether job history retained from the date the projects were locked

Environment

Release : All supported Releases

Component : CA PPM SAAS PROJECT MANAGEMENT

Resolution

1. Rerun the Autoschedule Project job against impacted projects with 'Publish After Scheduling' checked. 


(IMPORTANT: this can impact task data as it will publish changes done by the tentative schedule created for the project(s))


2. If projects still remain locked, you can clear them from the Security Locks page in Clarity

  • Go to: http(s)://<server>/niku/nu#action:security.locks
  • Filter on lock type of 'Project Insert Lock'
  • Check the boxes for the projects you want to unlock click on 'Clear Locks' button

IMPORTANT: Before unlocking, make sure that the projects are not intentionally checked out by a user (it can be locked if the user is working on the project in MSP, OWB, or created there own tentative schedule via the Gantt)


3. If you get an error trying to access the security.locks page (and have Administrative access) this could be due to a high # of projects being locked. In order to fix this, please contact Broadcom support. 


To check for project locks from the DB side: 

Select * from prlock where prtablename = 'SRM_PROJECTS'