Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

PegaRULES initialization fails with error message in log



When trying to start the tomcat server, PegaRULES initialization failed error message is generated.

After refreshing the environment with an old database backup, the below error is received.

Status fail
Message There has been an issue; please consult your system administrator
Operator ID Unauthenticated or not available
Requestor ID No ID available
Timestamp Wed Sep 16 23:47:06 UTC 2015
Engine Version PegaRULES 7.10 ML8 (coreAssemblyCached_718_675)

Error Messages

2015-09-16 06:08:47,658 [LOAD_PEGACONCLUSIONS] [  STANDARD] [                    ] (dictionary.ConclusionCacheImpl) INFO    -  Starting conclusion pre-load...
2015-09-16 06:08:49,599 [] [  STANDARD] [                    ] (res.CacheDataToCandidateMapper) WARN    -  Unable to load RULE-OBJ-ACTIVITY MOVERULESTORS #20150508T074713.618 GMT due to Database-BadClassDef Work; This may cause the wrong rule to run during rule execution.
2015-09-16 06:08:51,363 [] [  STANDARD] [                    ] (ternal.vtable.VirtualTableImpl) INFO    -  ...Finished. Preloaded 16.6MB for 68531 rules in 5741 ms
2015-09-16 06:08:52,824 [1] [  STANDARD] [                    ] (   internal.mgmt.PREnvironment) ERROR   - Method Invocation exception
2015-09-16 06:08:52,927 [] [  STANDARD] [                    ] (      etier.impl.EngineStartup) ERROR   -  PegaRULES initialization failed. Server: PRNodeImpl init failed
                at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(

                at java.util.concurrent.Executors$
                at java.util.concurrent.ThreadPoolExecutor.runWorker(
                at java.util.concurrent.ThreadPoolExecutor$
Caused by: Method Invocation exception
                at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(
                at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
                at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
                at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(
                ... 28 more
Caused by: java.lang.reflect.InvocationTargetException
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(
                at java.lang.reflect.Method.invoke(
                at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(
                ... 31 more
Caused by: Unable to construct authorization core due to authorization failure
                               ... 36 more
Caused by: No such Rule-Application instance: PegaRULES:06.02
From: (A9C8CC9DF1E6B8D1382FFA76508038530) 
                at com.pega.pegarules.session.internal.authorization.context.RuleApplicationFlattener$DbAppReader.toClipboardPage(
                at com.pega.pegarules.session.internal.authorization.context.RuleApplicationFlattener.addApplicationNode(
                at com.pega.pegarules.session.internal.authorization.context.RuleApplicationFlattener.<init>(
                at com.pega.pegarules.session.internal.authorization.context.ContextUtils.getAppStackForApplication(
                at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.createAppStackForAccessGroup(
                at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.updateDefinition(
                at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.<init>(
                at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getBasicApplicationContext(
                at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getLocalizedApplicationContext(
                at com.pega.pegarules.session.internal.authorization.context.AuthorizationContextManagerImpl.getContext(
                at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(
                at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(
                at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(
                at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(
                ... 60 more
2015-09-16 06:08:52,930 [1] [  STANDARD] [                    ] (      etier.impl.EngineStartup) INFO    -  PegaRULES initialization failed. Server:
2015-09-16 06:08:53,031 [] [  STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) ERROR   -  Enterprise tier failed to initialize properly, PegaRULES not available
2015-09-16 06:08:53,139 [] [  STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) INFO    -  Web Tier initialization is complete.
2015-09-16 06:08:58,986 [LOAD_PEGACONCLUSIONS] [  STANDARD] [                    ] (dictionary.ConclusionCacheImpl) INFO    -  Pre-Loaded 25803 conclusions
2015-09-16 06:08:58,986 [LOAD_PEGACONCLUSIONS] [  STANDARD] [                    ] (   external.async.IStartupTask) INFO    -  load pegaConclusions ..done


2015-09-16 06:25:18,236 [] [          ] [                    ] (  internal.access.DatabaseImpl) INFO    -  Checking schema PEGARULES for obsolete triggers
2015-09-16 06:25:38,637 [] [          ] [                    ] (  internal.access.DatabaseImpl) INFO    -  No obsolete triggers detected
2015-09-16 06:25:44,679 [] [          ] [                    ] (      etier.impl.EngineStartup) ERROR   -  PegaRULES initialization failed. Server: PRNodeImpl init failed
                at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(
                at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(
                at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(
                at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(
                at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(
                at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(
                at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(
                at java.util.concurrent.ThreadPoolExecutor$
Caused by: Unable to construct authorization core due to authorization failure
                at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(
                at com.pega.pegarules.session.internal.mgmt.PRRequestorBase.allocateSessionAuthorization(
                at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.allocateSessionAuthorization(
                               ... 28 more
Caused by: Data-Admin-Requestor instance "" not found
From: (BC2AB12FBA5EAA031EBB997E4EFF343E3) 
                at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(
                at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(
                ... 49 more
2015-09-16 06:25:44,893 [] [          ] [                    ] (      etier.impl.EngineStartup) INFO    -  PegaRULES initialization failed. Server: 
2015-09-16 06:25:45,399 [] [          ] [                    ] (ervlet.WebAppLifeCycleListener) ERROR   -  Enterprise tier failed to initialize properly, PegaRULES not available
2015-09-16 06:25:45,599 [] [          ] [                    ] (ervlet.WebAppLifeCycleListener) INFO    -  Web Tier initialization is complete.
2015-09-16 07:17:02,564 [] [          ] [                    ] (ervlet.WebAppLifeCycleListener) INFO    -  System Start Date: Wed Sep 16 07:17:02 UTC 2015

Steps to Reproduce

There is no specific use case identified to replicate the behavior.

Root Cause

1. The stack trace shows that PRPC is failing to initialize a batch requestor for the given system name configuration. The BATCH requestor type definition refers an accessgroup. The access group is pointing to an invalid application definition.

By running the query, select * from pr4_rule where pzinskey like '%RULE-APPLICATION PegaRULES:06.02%' to see if the application definition actually exists. If it does not exist, the application definition can be re-imported using the command line utility, prpcutils. This would use prpc as the systemname, so the engine start-up should go through fine. If not, one more option could be to bring up a node specifying the prconfig, identification/systemName as prpc and edit the offending accessgroup

2. PRPC does not initialize if the system name does not exist in the PR_DATA_ADMIN, the behaviour can be noticed if the user deletes browser requestor type or the access group (Developers) mistakenly. User can run the query from the DB to verify the same;

select distinct pysystemname from pr_data_admin where pxobjclass like 'Data-Admin-Requestor';
select distinct from pr_data_admin where pyaccessgroup like 'Developers';


Browser Requester Type unauthenticated access group is wrong for “pega” system name. Correct this configuration.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us