Support Article
prpcUtils: RAP Imports not working, engine fails to intialize
SA-4365
Summary
Using prpcUtils to import Rule-Admin-Product files, RAPs, the PRPC engine is not properly starting and the import of the RAP is not working.
Error Messages
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:393)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
...
Caused by: com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:248)
at com.pega.pegarules.session.internal.mgmt.PRRequestorBase.allocateSessionAuthorization(PRRequestorBase.java:498)
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.allocateSessionAuthorization(PRRequestorImpl.java:1901)
at com.pega.pegarules.session.internal.authorization.Authorization.reset(Authorization.java:405)
...
Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException: No such Rule-Application instance: PegaRULES 03.11
From: (B3E5D1CEA75B847BBBF1D2BBBD39D9DBD)
at com.pega.pegarules.session.internal.authorization.context.ContextUtils.getAppStackForApplication(ContextUtils.java:526)
at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.createAppStackForAccessGroup(BasicApplicationContext.java:619)
at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.updateDefinition(BasicApplicationContext.java:464)
at com.pega.pegarules.session.internal.authorization.context.BasicApplicationContext.<init>(BasicApplicationContext.java:153)
Steps to Reproduce
Occurs when running prpcUtils.
Root Cause
The root cause of this problem is a defect in customer application code/rules.
The Data-Admin-Requestor PRPC Batch instance was referencing and AccessGroup that was pointing to an application record that no longer existed in the system: PegaRULES 03.11.
Resolution
When using prpcUtils insure that the Data-Admin-Requestor PRPC Batch instance is using a properly configred AccessGroup record.
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.