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

Server initialization fails post Pega 7.1.9 upgrade



Server initialization fails after upgrade from PRPC 5.5 to Pega 7.1.9.

Error Messages

[12/9/15 7:37:50:272 EST] 000000a3 SystemOut O 2015-12-09 07:37:49,986 [ your_server] [ ] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: your_server PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(
Caused by: Data-Admin-Requestor instance "wfe!BATCH" not found
From: (BAB6617B058EAAEE092812AE2D246EEB6)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(
... 72 more

Steps to Reproduce

  1. Upgrade Rules and Data to update to a split schema 
  2. Deploy Pega EAR and try to initialize the system

Root Cause

Pega was unable to locate requestor records that correspond to the current system name "wfe".


Set the system name to "pega" in the prconfig.xml file and attempt startup again.
​This avoids the startup failure and allows the administrator to define the requestor records required for further operations.


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