Support Article
Null pointer exception on startup - PRGenProviderImpl
SA-22500
Summary
After upgrading to Pega 7.1.9 from PRPC 6.3, the server does not come up.
It throws a NullPointerException.
Error Messages
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)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1998)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:664)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
java.lang.NullPointerException
at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:474)
at com.pega.pegarules.session.internal.mgmt.Executable.evaluateWhen(Executable.java:4209)
at com.pega.pegarules.session.internal.mgmt.Executable.evaluateWhen(Executable.java:4128)
Steps to Reproduce
- Upgrade from PRPC 6.3 to Pega 7.1.9.
- Try to start up server after successful upgrade.
Root Cause
A defect or configuration issue in the operating environment.
The PEGA!BATCH requestor access group does not have the PegaRULES:Batch role.
Resolution
Make the following change to the operating environment:
- Start the system with the out-of-the-box PRPC system name.
- Change the PEGA!BATCH requestor access group to have the PegaRULES:Batch role.
- Restart the system with system name Pega.
Published May 4, 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.