Support Article

RuleNotFound Pega-Landing-System-Upgrade during upgrade to 7.1.7



Upgrading from Pega 6.x to 7.1.7 split schema and upgrade failing during "Upgrade Rule Messages" task upgrading rules schema

Error Messages

[java] Caused by: pyVTable-RuleNotFound-NoMatches RULE-OBJ-ACTIVITY PZUPGRADERULEMESSAGES Pega-Landing-System-Upgrade 1 The 1 rules named 'PZUPGRADERULEMESSAGES' defined in the rulebase are:
[java] 1 related to applies-to class 'Pega-Landing-System-Upgrade', but were defined in rulesets which are not in your rulesetlist: 'Pega-LP-SystemSettings:07-10-15'.

[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.throwDetailedRuleNotFoundException(
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveToContainer(
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveRule(
[java] at com.pega.pegarules.generation.internal.vtable.VirtualTableImpl.resolveRule(
[java] at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(
[java] at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
[java] at com.pega.pegarules.deploy.internal.util.UpgradeRuleMessages.main(
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(
[java] at java.lang.reflect.Method.invoke(
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(
[java] ... 1 more

Steps to Reproduce

Run upgrade for rules schema

Root Cause

While trying to resolve a previous error, you notice that the setupDatabase.xml file that comes with the media was altered to change the system name defined in the prconfig.xml file from prpc to pega.  The access groups of the Pega requestor types on this system have not yet been updated to be to the correct Pega 7 rulesets.  The prpc systemName should be used for the upgrade.


To resolve this issue, perform the following local change: 

Use setupDatabase.xml file that comes with the media and resume the upgrade.

Published February 26, 2016 - Updated October 8, 2020

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.