Support Article
Cannot start Pega instance
SA-613
Summary
While trying to start the JVM, user is getting the exception below
ERROR MESSAGES
Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException: 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(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)
at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getBasicApplicationContext(GlobalContextCache.java:402)
at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getLocalizedApplicationContext(GlobalContextCache.java:436)
at com.pega.pegarules.session.internal.authorization.context.AuthorizationContextManagerImpl.getContext(AuthorizationContextManagerImpl.java:127)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(SessionAuthorization.java:535)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(SessionAuthorization.java:510)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(SessionAuthorization.java:444)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:244)
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.
Resolution
- 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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.