Question
Accenture
IN
Last activity: 7 Feb 2017 2:00 EST
Issue during opening the URL :: Error: You lack access required to execute RULE-OBJ-ACTIVITY
We are facing issue during opening the URL.
The log and the url screenshot are attached.
Please suggest what to do.
Error:
[10/25/16 23:50:27:267 EDT] 00000013 stdout Z 2016-10-25 23:50:27,267 [.PegaWorkManager : 0] [ STANDARD] [ ] [ SbiApp:01.01.01] ( internal.mgmt.Executable) ERROR - Only authenticated client may start this activity: RULE-OBJ-ACTIVITY SBIO-SBIAPP-WORK CALLACTIVITY #20160524T063319.799 GMT
com.pega.pegarules.pub.PRRuntimeException: Error: You lack access required to execute RULE-OBJ-ACTIVITY SBIO-SBIAPP-WORK CALLACTIVITY #20160524T063319.799 GMT.
at com.pega.pegarules.session.internal.mgmt.Executable.updateStepStatusAndLog(Executable.java:836)
at com.pega.pegarules.session.internal.mgmt.Executable.activityProlog(Executable.java:768)
at com.pegarules.generated.activity.ra_action_callactivity_1f49d82610cd771054caadafc4cf3db6.perform(ra_action_callactivity_1f49d82610cd771054caadafc4cf3db6.java:52)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721)
Pegasystems Inc.
IN
Have you configured your activity's security tab like below? if not can you configure as below and check again?
'Require authentication to run' should be unchecked and check 'allow direct invocation....'
Pega
IN
Hi PrasenjitK,
If the issue is not getting resolved after making the above changes means, please create an SR in my support portal.
Accenture
IN
Confidential
IN
Hi You shouldnt check "Requires authentication to run" in your activity's security tab.
Please check once.
ING
NL
Hi PrasenjitK,
Thant issue is due to Requester Type,
It is present in SysAdmin, Category, any of you requester might be deleted, Kindly re check it once,
System Name : PRPC
Requester Type : Browser.
Go to Data base from Back end and then add a new row in DB,
I got same issue, and Resolved it..
Do necessary changes in below query.
INSERT INTO personaledition.pr_data_admin(
pxcommitdatetime, pxsavedatetime, pxcreatedatetime, pxcreateopname,
pxcreateoperator, pxcreatesystemid, pxinsname, pxobjclass, pxproductname,
pxproductpatchversion, pxproductversion, pxupdatedatetime, pxupdateopname,
pxupdateoperator, pxupdatesystemid, pyaccessgroup, pydefaultappname,
pydefaultappversion, pyexpiration, pylabel, pymanager, pyname,
pyorgdivision, pyorgunit, pyorganization, pyowner, pypurpose,
pyrulesetname, pysystemname, pytimestamp, pyworkbasket, pyworkgroup,
pyworkgroupname, pyworkpool, pysetting, pynodename, pxsystemnamesetfromfile,
pzinskey, pzpvstream)
VALUES ('21-OCT-16','21-OCT-16','21-MAY-10','Ed Keisling',
Hi PrasenjitK,
Thant issue is due to Requester Type,
It is present in SysAdmin, Category, any of you requester might be deleted, Kindly re check it once,
System Name : PRPC
Requester Type : Browser.
Go to Data base from Back end and then add a new row in DB,
I got same issue, and Resolved it..
Do necessary changes in below query.
INSERT INTO personaledition.pr_data_admin(
pxcommitdatetime, pxsavedatetime, pxcreatedatetime, pxcreateopname,
pxcreateoperator, pxcreatesystemid, pxinsname, pxobjclass, pxproductname,
pxproductpatchversion, pxproductversion, pxupdatedatetime, pxupdateopname,
pxupdateoperator, pxupdatesystemid, pyaccessgroup, pydefaultappname,
pydefaultappversion, pyexpiration, pylabel, pymanager, pyname,
pyorgdivision, pyorgunit, pyorganization, pyowner, pypurpose,
pyrulesetname, pysystemname, pytimestamp, pyworkbasket, pyworkgroup,
pyworkgroupname, pyworkpool, pysetting, pynodename, pxsystemnamesetfromfile,
pzinskey, pzpvstream)
VALUES ('21-OCT-16','21-OCT-16','21-MAY-10','Ed Keisling',
'keise','pega','PEGA!BROWSER','Data-Admin-Requestor','',
'', '', '21-OCT-16', 'WellCare',
'WellCare','pega','','',
'','','BROWSER Starting connection','','',
'','','','','',
'LoginScreen','prpc','','','',
'','','','','',
'DATA-ADMIN-REQUESTOR PEGA!BROWSER','(BLOB)';