Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US
Anandh Palanisamy Member since 2013 62 posts
Ford Motor Company
Posted: Jul 26, 2017
Last activity: Jul 27, 2017
Posted: 26 Jul 2017 16:43 EDT
Last activity: 27 Jul 2017 14:09 EDT
Closed
Solved

Ruleset delete wizard is showing 0% not working

Hi,

We are facing some issue with delete ruleset wizard, its keep showing 0% and not moving, getting below error.

Show More

Hi,

We are facing some issue with delete ruleset wizard, its keep showing 0% and not moving, getting below error.

2017-07-26 16:28:08,537 [PRPCWorkManager : 10] [  STANDARD] [OneApp:01.01.04] (ernal.async.BatchRequestorTask) ERROR  APALANIS - Batch activity "Log-Delete.DeleteRuleSet" threw:
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
	at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:683)
	at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(ThreadRunner.java:545)
	at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(PRThreadImpl.java:581)
	at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(QueueProcessor.java:253)
	at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:316)
	at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:837)
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1079)
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:814)
	at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:586)
	at com.pega.pegarules.session.internal.async.Agent.runBatchTask(Agent.java:706)
	at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:193)
	at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:148)
	at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:312)
	at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
	at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:221)
	at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
	at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
	at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
	at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)
	at com.pega.pegarules.internal.etier.interfaces.EJSLocalStatelessEngineBMT_f2439d86.invokeEngine(Unknown Source)
	at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:151)
	at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.AsyncTask.run(AsyncTask.java:60)
	at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.RunnableWrapper.run(RunnableWrapper.java:67)
	at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:270)
	at java.security.AccessController.doPrivileged(AccessController.java:284)
	at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:796)
	at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
	at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1720)
Caused by: 
com.pega.pegarules.pub.PRRuntimeException: PRRuntimeException
	at com.pegarules.generated.activity.ra_action_deleteruleset_016fc3a550f4e5fc8239a0b1bf83cbbd.step6_circum0(ra_action_deleteruleset_016fc3a550f4e5fc8239a0b1bf83cbbd.java:966)
	at com.pegarules.generated.activity.ra_action_deleteruleset_016fc3a550f4e5fc8239a0b1bf83cbbd.perform(ra_action_deleteruleset_016fc3a550f4e5fc8239a0b1bf83cbbd.java:185)
	at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3078)
	at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:617)
	... 31 more
Caused by: 
com.pega.pegarules.pub.database.AuthorizationException: You are not authorized to list instances of class Data-Rule-Summary
From: (B8231B36E9721ECADCE150BEE09FE1A0D) 
	at com.pega.pegarules.pub.database.AuthorizationException.createCannotSearchException(AuthorizationException.java:263)
	at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:5686)
	at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:5606)
	at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:5569)
	at com.pegarules.generated.activity.ra_action_deleteruleset_016fc3a550f4e5fc8239a0b1bf83cbbd.step6_circum0(ra_action_deleteruleset_016fc3a550f4e5fc8239a0b1bf83cbbd.java:963)

We are using PRPC 6.2 sp2.

Regards,

Anandh

***Moderator Edit: Vidyaranjan | Updated Categories***


Show Less
To see attachments, please log in.
Low-Code App Development
System Administration

Accepted Solution

Posted: 7 years ago
Posted: 27 Jul 2017 14:09 EDT
Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US

Hi All,

I found the solution, while login through SSOServlet the default access group should have a access to "Data-Rule-Summary" in the access role to object.

After updating the access role to object, the wizard is working now.

Thanks everyone for replied to this thread.

Regards,

Anandh

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jul 2017 5:32 EDT
Abhishek Kumar (kumaa33)
Pegasystems Inc.
Senior Solutions Engineer
Pegasystems Inc.
IN

Hi Anandh,

you can try the sql statements to delete the rulesets. Below is the link for doing it in 5x but same should work for 6x also.

https://community.pega.com/how-delete-ruleset-using-sql-statements/how-delete-ruleset-using-sql-statements

Thank you

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jul 2017 5:38 EDT
Abhishek Kumar (kumaa33)
Pegasystems Inc.
Senior Solutions Engineer
Pegasystems Inc.
IN

Also the below error trace:

Caused by: 
com.pega.pegarules.pub.database.AuthorizationException: You are not authorized to list instances of class Data-Rule-Summary

It seems like the access group does not have desired privillges to delete the ruleset. Please check once on that also.

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jul 2017 8:07 EDT
Santhosh Bagannagari (bagas)
Pegasystems Inc.
Tech Lead, Security Engineering
Pegasystems Inc.
IN

Hi,

From the stack trace it looks permissions are missing on "Data-Rule-Summary" class. Can you try giving executeReport permissions on it  ?

 

Thanks,

Santhosh

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jul 2017 10:19 EDT
Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US

Hi All,

Even i have checked with "PRPC:Administrators" access group, still getting the same error. Any thought on this?

Regards,

Anandh

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jul 2017 11:51 EDT
Abhishek Kumar (kumaa33)
Pegasystems Inc.
Senior Solutions Engineer
Pegasystems Inc.
IN

Hi Anandh,

while looking into the past similar issues , I can see in one of the case it got resolved by setting the prconfig setting, initialization/childrequestors/uselightweightauth to false in either the prconfig.xml file or a Dynamic System Setting.

Please refer the below SA article:

https://community.pega.com/support/support-articles/unable-delete-unlocked-ruleset

You can also try above if that helps.

-Abhishek

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jul 2017 11:20 EDT
Abhishek Kumar (kumaa33)
Pegasystems Inc.
Senior Solutions Engineer
Pegasystems Inc.
IN

Hi Anandh,

Could you please set the logging level for the below :

Rule_Obj_Activity.DeleteRuleSet.Log_Delete.Action

And try deleting the ruleset and send us the log  for the same. The reason for doing this is , "Delete rule set" is the activity which is performing the deletion but some how it failing at step6. After the above logging level we might get extra information.

Meanwhile could you please try the sql method for deleting the ruleset as mentioned in one of the above comment.But back up the entire PegaRULES database and stop Process Commander before using SQL tools to perform deletions.

https://community.pega.com/how-delete-ruleset-using-sql-statements/how-delete-ruleset-using-sql-statements

Thank you

-Abhishek

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jul 2017 13:15 EDT
Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US

Thanks Abhishek, When i try to login with PRServlet its working, but when i try to login with SSOServlet its keep failing.

You mean above DSS setting does it related to SSO?

Regards,

Anandh

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 27 Jul 2017 14:09 EDT
Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US

Hi All,

I found the solution, while login through SSOServlet the default access group should have a access to "Data-Rule-Summary" in the access role to object.

After updating the access role to object, the wizard is working now.

Thanks everyone for replied to this thread.

Regards,

Anandh

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice