Question

4
Replies
136
Views
Chetan Naik (ChetanNaik)
Mindtree
Senior Architect
Mindtree
IN
ChetanNaik Member since 2009 11 posts
Mindtree
Posted: March 2, 2017
Last activity: April 6, 2018
Posted: 2 Mar 2017 6:37 EST
Last activity: 6 Apr 2018 19:26 EDT
Closed
Solved

Rules Upgrade - Failed with NoClassDefError - DirectStreamEnvironmentAdapter

As part of Upgrade process, we are upgrading from PRPC6.1 to PRPC 7.2.2, we ran the migrate rules and this was successful. Our current 6.1 environment, system name has been updated to "Pega_DEV4_ENV". We updated the setupDatabase.properties file with the current system name, that is changed "pega" (that is default in media file properties) to "Pega_DEV4_ENV". Now we ran the upgrade, the upgrade is failing with error:

NoClassDefFoundError - com.pega.pegarules.data.internal.clipboard.directstream.DirectStreamEnvironmentAdapter error. I did some research for this issue on PDN and found following links:

Link1: https://pdn.pega.com/community/pega-7-upgrade-center/question/pzupgraderulemessages-rule-not-found-exception

This says this might be a bun and could be fixed with next ML release.

Link 2: htts://pdn.pega.com/support-articles/rulenotfound-pega-landing-system-upgrade-during-upgrade-717

This says update the system name to fix this issue. I wanted to confirm what the system name should be when I run the rules upgrade. Should it be current system name for PRPC 6.1 environment (Pega_DEV4_ENV) or should remain "pega" which comes OOTB with the media file.

My understanding was that we need to update system name to "Pega_DEV4_ENV".

**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.

System Administration Upgrades
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.