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

Data-Admin-Requestor instance "wfe!BATCH" not found

SA-23281

Summary



After migrating a system from PRPC 6.3 to Pega 7.1.9, an error occurred during start-up in the logs.

Error Messages



**Date and time**,698 [          SERVERNAME] [          ] [                    ] [                    ] (
internal.access.DatabaseImpl) INFO    - Checking schema PEGA719RULES for obsolete triggers
**Date and time**,241 [          SERVERNAME] [          ] [                    ] [                    ] (  internal.access.DatabaseImpl) INFO    - No obsolete triggers detected
.
.
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
        at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:396)
        at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1998)
.
.

Steps to Reproduce



Migrate the system, and start the application server.

Root Cause



The above error can occur if the system name is not present in the prconfig.xml or through the Dynamic System Setting.

Resolution

Perform any one of the following local-changes:
  • Add the Dynamic System Setting as:
          Owning Ruleset: Pega-Engine
          Setting Purpose: prconfig/identification/systemName/default
          Value: Pega
           (or any system name)
  • Adding the following to the prconfig.xml file:
          <env name="Identification/SystemName" value="pega"/>
Suggest Edit

Published May 21, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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