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

Cannot start Pega instance



While trying to start the JVM, user is getting the exception below


Caused by: No such Rule-Application instance: X 01.02, depended on by Y 01.02
From: (A6E611E69CA4B085E33F783102C08A922)
                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>(

Root Cause

The customer has a non OOTB ‘system name’ and the Data-Admin-Requestor for type APP under this ‘system name’ has application in exception above referenced under the access group. They must have deleted this application.


  • Update prconfig to set system name to OOTB prpc or pega. Start the JVM’s
  • Login and fix the access group under the APP requestor for the custom system name
  • Revert prconfig entry and recycle JVM’s and reset the system name via DSS


Published March 21, 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