Status Reports not opening / Error 401 in Classic post upgrade to 15.9.3

book

Article ID: 223265

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

After a 15.9.3 Clarity upgrade, all the Status Reports in the system are throwing the below error in Classic UX / not working. 

ERRORError 401 - Unauthorized. You are not authorized to view the page. If you are sure you have access, try logging in again or contact your system administrator.

STEPS TO REPRODUCE: 

  1. Log in as admin to Classic UX (or any user who has all the rights in the system)
  2. Navigate to Projects -- Status Reports List Page
  3. Click on any Status Report and open it. 

Expected: The Status report opens

Actual: The above 401 error is thrown. 

Cause

Error Environment URL: 


https://servername/niku/nu#action:odf.cop_prj_statusrptProperties&parent_odf_view=projectCreate.subObjList.cop_prj_statusrpt&odf_code=cop_prj_statusrpt&odf_pk=5097839&grandparent_odf_view&id=5097839&ui.page.space=mainnav.work&odf_concrete_parent_object_code=project&odf_cncrt_parent_id=5096649

Working environment URL: 


https://servername/niku/nu#action:odf.cop_prj_statusrptProperties&parent_odf_view=projectCreate.subObjList.cop_prj_statusrpt&odf_code=cop_prj_statusrpt&odf_pk=5037061&grandparent_odf_view&id=5037061&ui.page.space=mainnav.work&odf_concrete_parent_object_code=project

As you can see in the above URLs,  &odf_cncrt_parent_id=5096649 has been appended which is causing the issue. Remove that part and the page loads fine. 

Environment

Clarity 15.9.3
Classic Clarity UI

Resolution

This has been flagged as defect (DE62420) and is fixed in v16.0

WORKAROUND: 

  1. If you are encountering this issue, please log a Broadcom Support case and the Support team will provide a temporary fix for this issue until Engineering delivers the fix.
  2. Once Broadcom Support confirms the activity is complete, please:
    • Flush the caches (security.caches) (See Flush Clarity server cache for steps on how to do this)
    • Logout/login
    • Then try again to confirm the issue is resolved