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 access Pega application: PegaRULES initialization failed

SA-32165

Summary



PegaRULES engine will not initialize and fail with an error in log.


Error Messages



2016-12-20 21:21:28,272 [ cs4csappd01.bns] [ ] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: your_server
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure
com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "DEV1!BATCH" not found

com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "DEV1!BATCH" not found
From: (B00E6DB5CFAB5901AA5F2A4B2E433AF43)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(SessionAuthorization.java:446)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:241)

Steps to Reproduce

  1. Clone the DB from one environment to another.
  2. Configure the application server to host the Pega application, and connect to the PegaRULES database.


Root Cause



A defect or configuration issue in the operating environment.

Out-of-the-box Pega comes with two Data-Admin-System records - prpc' and 'pega'.

The default prconfig.xml contains an entry for 'pega' system name:
<env name="identification/systemName" value="pega" />

and the Batch requestor references this 'Pega' System name:




If prconfig.xml or Data-Admin-System records point to a different System name such as DEV1, the corresponding Batch, Browser, App and Portal Requestors should also be present for this DEV1 system name.

One can see the System name records in the DB from this SQL:

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


Resolution




Perform the following local-change steps:
  • Ensure that the System name used by prconfig matches the entry in the database.
  • Clone the database from an environment that is working correctly.
  • Ensure the PegaRULES database and the new Websphere environment are also configured similarly.

Published January 31, 2017 - 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