Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Shiva Gupta (ShivaGupta)
Virtusapolaris

Virtusapolaris
IN
ShivaGupta Member since 2015 4 posts
Virtusapolaris
Posted: Jul 31, 2015
Last activity: Apr 6, 2018
Posted: 31 Jul 2015 2:26 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

"PZUPGRADERULEMESSAGES - Rule not found exception"

While performing the Rules upgrade it failed due to some DB issues. We resolved the issues and resumed the operation using 'resume.sh' but again the Rules upgrade failed during "Upgrade Rule Messages" step with the following exception. Kindly help us in resolving the issue.

java] 2015-07-28 16:48:16,570 [ WGUPTS10W7HYD] [ STANDARD] [ ] ( etier.impl.EngineStartup) INFO - PegaRULES engine successfully started. TimeZone: Asia/Calcutta AESPerfStatMode: PUSH Server: WGUPTS10W7HYD System: y55_test Description: WGUPTS10W7HYD y55_test 2015-07-28 06:58:22.584 GMT URL: [unable to determine]
[java] 2015-07-28 16:48:16,572 [ WGUPTS10W7HYD] [ STANDARD] [ ] ( internal.mgmt.EngineImpl) INFO - Embedded Environment initialization is complete.
[java] 2015-07-28 16:48:16,580 [ WGUPTS10W7HYD] [ STANDARD] [ ] (ernal.util.UpgradeRuleMessages) INFO - Upgrading Rule-Message instances...
[java] 2015-07-28 16:48:17,317 [ WGUPTS10W7HYD] [ STANDARD] [ ] (l.access.RuleCandidateIterator) INFO - Single candidate rule resolution optimization is enabled
[java] Jul 28, 2015 4:48:18 PM com.pega.pegarules.internal.bootstrap.PRBootstrap
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.generator.RuleNotFoundException: pyVTable-RuleNotFound-NoMatches RULE-OBJ-ACTIVITY PZUPGRADERULEMESSAGES Pega-Landing-System-Upgrade 2 The 2 rules named 'PZUPGRADERULEMESSAGES' defined in the rulebase are:
[java] 2 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, Pega-LP-SystemSettings:07-10-17}.
[java]
[java]
[java] Current RulesetList:
[java] Pega-ProcessCommander:06-02,
[java] Pega-LP-ProcessAndRules:06-02,
[java] Pega-LP-Integration:06-02,
[java] Pega-LP-Reports:06-02,
[java] Pega-LP-SystemSettings:06-02,
[java] Pega-LP-UserInterface:06-02,
[java] Pega-LP-OrgAndSecurity:06-02,
[java] Pega-LP-DataModel:06-02,
[java] Pega-LP-Application:06-02,
[java] Pega-LP:06-02,
[java] Pega-UpdateManager:06-02,
[java] Pega-SecurityVA:06-02,
[java] Pega-Feedback:06-02,
[java] Pega-AutoTest:06-02,
[java] Pega-AppDefinition:06-02,
[java] Pega-ImportExport:06-02,
[java] Pega-LocalizationTools:06-02,
[java] Pega-RuleRefactoring:06-02,
[java] Pega-ProcessArchitect:06-02,
[java] Pega-Portlet:06-02,
[java] Pega-Content:06-02,
[java] Pega-IntegrationArchitect:06-02,
[java] Pega-SystemArchitect:06-02,
[java] Pega-Desktop:06-02,
[java] Pega-EndUserUI:06-02,
[java] Pega-EventProcessing:06-02,
[java] Pega-Reporting:06-02,
[java] Pega-UIDesign:06-02,
[java] Pega-Gadgets:06-02,
[java] Pega-UIEngine:06-02,
[java] Pega-ProcessEngine:06-02,
[java] Pega-SearchEngine:06-02,
[java] Pega-IntegrationEngine:06-02,
[java] Pega-RulesEngine:06-02,
[java] Pega-Engine:06-02,
[java] Pega-ProCom:06-02,
[java] Pega-IntSvcs:06-02,
[java] Pega-WB:06-02,
[java] Pega-RULES:06-02
[java]
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.throwDetailedRuleNotFoundException(VirtualTableResolver.java:726)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveToContainer(VirtualTableResolver.java:401)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveRule(VirtualTableResolver.java:155)
[java] at com.pega.pegarules.generation.internal.vtable.VirtualTableImpl.resolveRule(VirtualTableImpl.java:301)
[java] at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:474)
[java] at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3483)
[java] at com.pega.pegarules.deploy.internal.util.UpgradeRuleMessages.main(UpgradeRuleMessages.java:79)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[java] at java.lang.reflect.Method.invoke(Method.java:601)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java]
[java] Exception in thread "WGUPTS10W7HYD" java.lang.RuntimeException: Problem during method invocation (main)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:278)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java] Caused by: com.pega.pegarules.pub.generator.RuleNotFoundException: pyVTable-RuleNotFound-NoMatches RULE-OBJ-ACTIVITY PZUPGRADERULEMESSAGES Pega-Landing-System-Upgrade 2 The 2 rules named 'PZUPGRADERULEMESSAGES' defined in the rulebase are:
[java] 2 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, Pega-LP-SystemSettings:07-10-17}.
[java]
[java]
[java] Current RulesetList:
[java] Pega-ProcessCommander:06-02,
[java] Pega-LP-ProcessAndRules:06-02,
[java] Pega-LP-Integration:06-02,
[java] Pega-LP-Reports:06-02,
[java] Pega-LP-SystemSettings:06-02,
[java] Pega-LP-UserInterface:06-02,
[java] Pega-LP-OrgAndSecurity:06-02,
[java] Pega-LP-DataModel:06-02,
[java] Pega-LP-Application:06-02,
[java] Pega-LP:06-02,
[java] Pega-UpdateManager:06-02,
[java] Pega-SecurityVA:06-02,
[java] Pega-Feedback:06-02,
[java] Pega-AutoTest:06-02,
[java] Pega-AppDefinition:06-02,
[java] Pega-ImportExport:06-02,
[java] Pega-LocalizationTools:06-02,
[java] Pega-RuleRefactoring:06-02,
[java] Pega-ProcessArchitect:06-02,
[java] Pega-Portlet:06-02,
[java] Pega-Content:06-02,
[java] Pega-IntegrationArchitect:06-02,
[java] Pega-SystemArchitect:06-02,
[java] Pega-Desktop:06-02,
[java] Pega-EndUserUI:06-02,
[java] Pega-EventProcessing:06-02,
[java] Pega-Reporting:06-02,
[java] Pega-UIDesign:06-02,
[java] Pega-Gadgets:06-02,
[java] Pega-UIEngine:06-02,
[java] Pega-ProcessEngine:06-02,
[java] Pega-SearchEngine:06-02,
[java] Pega-IntegrationEngine:06-02,
[java] Pega-RulesEngine:06-02,
[java] Pega-Engine:06-02,
[java] Pega-ProCom:06-02,
[java] Pega-IntSvcs:06-02,
[java] Pega-WB:06-02,
[java] Pega-RULES:06-02
[java]
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.throwDetailedRuleNotFoundException(VirtualTableResolver.java:726)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveToContainer(VirtualTableResolver.java:401)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveRule(VirtualTableResolver.java:155)
[java] at com.pega.pegarules.generation.internal.vtable.VirtualTableImpl.resolveRule(VirtualTableImpl.java:301)
[java] at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:474)
[java] at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3483)
[java] at com.pega.pegarules.deploy.internal.util.UpgradeRuleMessages.main(UpgradeRuleMessages.java:79)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[java] at java.lang.reflect.Method.invoke(Method.java:601)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)
[java] ... 1 more

BUILD FAILED
C:\Pega7.1.8\scripts\setupDatabase.xml:317: The following error occurred while executing this line:
C:\Pega7.1.8\scripts\setupDatabase.xml:2333: Java returned: 1



**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 9 years ago
Posted: 31 Jul 2015 2:30 EDT
Nandhini Nataraj (natan)
PEGA
Principal Software Engineer - Customer Success
Pegasystems Inc.

Hi Shiva,

The root cause of the issue is System name used for ‘Rule Upgrade ‘ step ( i.e. y55_test in this case)  is not getting reverted to ‘prpc’ when upgrade process fails during ‘Upgrade Rule Base (_upgradeRuleBase )’ stage.
This is because on resume, customer system name is NOT getting recomputed due to which ‘Revert system name’ (_revertSystemName target) is failing to replace system name in prcofig.xml. Hence the next process, i.e. ‘Upgrade Rule Message’ target is getting executed with customer system name where requesters are pointed to older PRPC version (see all the rulesets are pointing to 06-02).

This is a bug and will be fixed in the next ML. The solution is to revert back the environment and re-run the upgrade process.

 

Thank you,

Nandhini

To see attachments, please log in.
Posted: 8 years ago
Posted: 25 Feb 2016 10:41 EST
Dinu Pankajakshanraghavan (dpr_2018)
Cognizant Technology Solutions

Cognizant Technology Solutions
US

What if it again fails?I am also getting same error when i do an upgrdae from 55sp1 to pega 718.Please assist.

To see attachments, please log in.
Posted: 8 years ago
Posted: 25 Feb 2016 15:17 EST
Chandra Sekhar Bhagath Vasireddy (Bhagath_Vasireddy)
Cognizant
Chandra Sekhar Bhagath Vasireddy
Cognizant
IN

you have to update the prconfig.xml as below

<env name="Identification/SystemName" value="prpc7" />

This config change will resolve the problem without upgrading the DL

To see attachments, please log in.
Posted: 7 years ago
Posted: 11 Jan 2017 13:15 EST
abdul qaadir (abdulq95)
JP Morgan

JP Morgan
US

I'm upgrading from 62 to 7.2 and observed the exact similar error. I changed the system name to "prpc7". Still observing the same error.

Please assist if there is more to this.

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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