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

prpcUtils: RAP Imports not working, engine fails to intialize



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 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(

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(
at com.pega.pegarules.session.internal.authorization.Authorization.reset(
Caused by: No such Rule-Application instance: PegaRULES 03.11
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>(

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.


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

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