Support Article
Server initialization fails post Pega 7.1.9 upgrade
SA-17760
Summary
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
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:396)
...
Caused by:
com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "wfe!BATCH" not found
From: (BAB6617B058EAAEE092812AE2D246EEB6)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(SessionAuthorization.java:450)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:245)
... 72 more
Steps to Reproduce
- Upgrade Rules and Data to update to a split schema
- 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".
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.