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

Upgrade error using IUA

SA-19471

Summary



Upgrading PRPC 6.1 SP2 to Pega 7.1.8 through Install and Update Assistant (IUA) and the upgrade process fails with an error.


Error Messages



[java] 2016-01-28 20:45:35,872 [ Workstation ] [ STANDARD] [ ] ( internal.util.ImportImpl) ERROR - A problem occurred during import.
[java] java.lang.ArithmeticException: / by zero
[java] at com.pega.pegarules.priv.collections.map.MostFrequentlyUsedMap.put(MostFrequentlyUsedMap.java:87)
[java] at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.doesRuleSetNameExist(StaticRulesetListImpl.java:398)
[java] at com.pega.pegarules.exec.internal.util.SpecializerImpl.doesRuleSetNameExist(SpecializerImpl.java:239)
[java] at com.pega.pegarules.exec.internal.util.SpecializerImpl.getInternationalVariants(SpecializerImpl.java:162)
[java] at com.pega.pegarules.exec.internal.util.SpecializerImpl.specializeInternationalVariants(SpecializerImpl.java:94)
[java] at com.pega.pegarules.exec.internal.util.SpecializerImpl.getSpecializedLocalizeList(SpecializerImpl.java:258)
[java] at com.pega.pegarules.session.internal.authorization.context.LocalizedApplicationContext.<init>(LocalizedApplicationContext.java:131)
[java] at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getLocalizedApplicationContext(GlobalContextCache.java:589)

 

Steps to Reproduce



Not Applicable.


Root Cause



A defect in Pegasystems’ code or rules. Most FrequentlyUsedMap code has a bug that results in this error when Engine checks for localized rulesets. If your Requestor Type records reference a custom Access Group that has localized rulesets, then that can result in the behavior.

Resolution



Perform the following local-change:

Make sure that localized rulesets are not added to out of the box Requestor Types' Access Groups before performing an upgrade. This issue will be fixed in the future Pega 7.x release.
Suggest Edit

Published February 9, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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