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

RuleNotFound errors in logfile after upgrade

SA-7484

Summary



Error messages appear in log files after upgrading the application from PRPC  6.1 SP2 to Pega 7.1.7.

Error Messages



com.pega.pegarules.pub.generator.RuleNotFoundException
Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException

Steps to Reproduce



Unknown

Root Cause



During upgrade, agents set with default access groups will have those access groups reset.

Resolution



Ensure that agents, which require access to custom rulesets, are given additional access groups with the full range of rulesets. These custom access groups will not be reverted during upgrades.

Published December 21, 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