Support Article
DASS not being saved after upgrading from Pega 7.1.7 to 7.1.8
SA-16350
Summary
After upgrading to Pega 7.1.8 if user updates DATA-ADMIN-SYSTEM-SETTING in a shared layer through an agent activity,it throws exception.
It is updated if user executes the activity manually.
Error Messages
2015-10-15 00:33:21,485 [ PegaRULES-Batch-1] [ STANDARD] [ shared] [ PegaRULES:07.10] ( internal.access.Saver) ERROR You are not authorized to save instance DATA-ADMIN-SYSTEM-SETTINGS PEGAAESREMOTE!AESSETTING/LASTPUSH/8B34FFE9FFC91F974EC6B88FEE9E38C1, of class Data-Admin-System-Settings
2015-10-15 00:33:21,485 [ PegaRULES-Batch-1] [ STANDARD] [ shared] [ PegaRULES:07.10] (sageData.PegaAESRemote_.Action) DEBUG - obj-save failed due to an invalid page.
com.pega.pegarules.pub.database.AuthorizationException: You are not authorized to create, modify, or lock instance DATA-ADMIN-SYSTEM-SETTINGS PEGAAESREMOTE!AESSETTING/LASTPUSH/8B34FFE9FFC91F974EC6B88FEE9E38C1
From: (B0C9F87D305D179D1A83E058D1FCE1670)
at com.pega.pegarules.pub.database.AuthorizationException.createCannotModifyException(AuthorizationException.java:255)
at com.pega.pegarules.data.internal.access.Saver.checkSecurity(Saver.java:709)
at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:598)
at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:5045)
at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:5031)
at com.pegarules.generated.activity.ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.step26_circum0(ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.java:2071)
at com.pegarules.generated.activity.ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.perform(ra_action_pushlogusagedata_5b19b97cae0347247e60446a7287f691.java:549)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:945)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1259)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:901)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:670)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)
at java.lang.Thread.run(Thread.java:724)
2015-10-15 00:33:21,485 [ PegaRULES-Batch-1] [ STANDARD] [ shared] [ PegaRULES:07.10] (sageData.PegaAESRemote_.Action) DEBUG - Running step 27_circum0
Steps to Reproduce
1. Upgrade to Pega 7.1.8.
2. Updates DATA-ADMIN-SYSTEM-SETTING in a shared layer through an agent activity.
Root Cause
Pega code issue.Agent Requestor was missing the tenant context. Setting the tenant name in requestor page solves the issue.
Resolution
Apply HFix-24545.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.