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

After update to 7.2, nodes fail to start



After updating to Pega 7.2.2 from 7.1.7, nodes fail to start. The caused by says there is a NullPointerException coming from SearchInitializationTask.

Error Messages

2017-09-01 17:30:58,618 [] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: your_server PRNodeImpl init failed
Caused by: java.lang.NullPointerException
at com.pega.pegarules.session.internal.async.startup.SearchInitializationTask.runTask(
at com.pega.pegarules.session.internal.async.startup.StartupTaskUtil.runTask(
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(

Steps to Reproduce

Update from Pega 7.1.7 to 7.2

Root Cause

A defect in Pegasystems’ code or rules:

If the following Dynamic System Settings (DSS) are set to false in 7.2, nodes will not start: indexing/distributed/enabled, indexing/distributed/index_enabled and indexing/distributed/search_enabled.


Perform the following local-change:
  1. Import a RAP file via prpcUtils that includes these DSS and had them set to true.
  2. Alternatively, add the following JVM argument that should force these DSS to be true on the node they are added to (after a successful startup, the DSS can be adjusted from within Designer Studio):

Suggest Edit

Published December 18, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

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