401 failure of the “admin update jasperParameters” command

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

After DB refresh activity (Clarity and DWH schema). 

User ppmjasperadmin_xxxxxx not available in report server Code: 401 parameter

ClarityJasperAdmin : Could not login to http://localhost:/reportservice/ with username jasperadmin

Cause

User ppmjasperadmin_xxxxxx not available in Clarity

Resolution

Validate user name and user UID from cmn_sec_users

1. Run the following query against PPM schema to validate:-
   SELECT USER_NAME, USER_UID FROM cmn_sec_users WHERE USER_NAME LIKE 'ppmjasperadmin'
2. Notice how USER_UID is ppmjasperadmin_xxxxxx instead of ppmjasperadmin
3. Update USER_UID to ppmjasperadmin
4. UPDATE CMN_SEC_USERS SET USER_UID='ppmjasperadmin' WHERE USER_NAME='ppmjasperadmin'

 

Additional Information

DUPLICATE users

If you get duplicate constraint warning when running the update, you have duplicates. To fix this:

1. Please run the query:
   select user_name, user_uid from cmn_sec_users
   where USER_UID ='ppmjasperadmin' or user_name ='ppmjasperadmin'
2. Note the user_name and USER_UID for both entries. You want to have one that is ppmjasperadmin/ppmjasperadmin
3. Update the username and UID as follows (assuming duplicate username was 'OLD1_ppmjasperadmin' if not replace it with the exact entry).
   update cmn_sec_users set USER_UID ='ppmjasperadmin_OLD1'
   where user_name ='OLD1_ppmjasperadmin'
   commit
4. Then run:
   UPDATE CMN_SEC_USERS SET USER_UID='ppmjasperadmin' WHERE USER_NAME='ppmjasperadmin'
   commit