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

UnresolvedAssemblyError:Rule resolution multiple versions error

SA-19083

Summary



Errors appear sporadically in the logs regarding, UnresolvedAssemblyError: Rule resolution identified multiple versions of the rule with class. 


Error Messages



com.pega.pegarules.pub.generator.UnresolvedAssemblyError: Rule resolution identified 3 versions of the rule with class Rule-Obj-Activity and name ClassName!ActivityName
at com.pega.pegarules.generation.internal.vtable.VirtualRuleTableDispatchImpl.useRuleResolutionToSelectRule(VirtualRuleTableDispatchImpl.java:765)
at com.pega.pegarules.generation.internal.vtable.VirtualRuleTableDispatchImpl.resolveRule(VirtualRuleTableDispatchImpl.java:455)
at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:586)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3260)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10274)


Steps to Reproduce



There is no specific use case to replicate this behavior.


Root Cause



A defect or configuration issue in the operating environment.

Resolution



Perform the following local-change:
  1. Set dynamic system setting, systempulse/scanoffsetms, to 60000 or 30000.
  2. Reassemble virtual table cache for affected rules.
    1. Open the System Management Application.
    2. Open the node experiencing the issue.
    3. Expand the Advanced menu.
    4. Select the Virtual Rule Table Cache Management landing page.
    5. Type the rule type class followed by a colon and the rule pxInsId.
    6. Click the button to get cache detail on the typed in rule.
    7. Click the button to reassemble cache for the rules captured from the cache detail search.​
  3. Attempt the error case to confirm resolution. Navigate to System Management Application > Advanced Area, to reassemble the identified activity.

Published January 30, 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