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

PegaRULES server not available error

SA-32687

Summary



After upgrade, when user try to hit application URL "PegaRULES server not available" is thrown on the screen.


Error Messages



PegaRULES server not available on screen.

Exception in rules log -

com.pega.pegarules.pub.PRRuntimeException: This node not found in the database - Either the record was never saved or was deleted. Unable to join the cluster
2017-01-18 11:30:07,444 [abc.abc.xxx.local] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: ab12305.xxx.abc.local
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed

Caused by: com.pega.pegarules.pub.PRRuntimeException: This node not found in the database - Either the record was never saved or was deleted. Unable to join the cluster


Steps to Reproduce

Upgrade application from Pega 7.1.7 to 7.2.2.


Root Cause



User cloned the database to the develop environment.

Hence it was observed that all the details of the UAT cluster environment was available in the pr_sys_statusnode table.

Resolution



Delete the rows of pr_sys_statusnode table and restart the system.

Published February 14, 2017 - Updated October 8, 2020

Was this useful?

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.

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