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

Performing developer actions throws unspecified error



Unable to open case stages in a newly installed instance on Oracle and WebLogic. An error appears on screen and exceptions are thrown in the PegaRULES log files.

Error Messages

Status fail
Message There has been an issue; please consult your system administrator

Problem invoking function: pega_wb_lookuplist.readFileAsPage--(String)
java.lang.ClassNotFoundException: com.pegarules.generated.readFileAsPage_071017_SiW_nNAJCjXQ7Jp_PS2DSw
at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.findClass(
at java.lang.ClassLoader.loadClass(
at com.pega.pegarules.internal.bootstrap.phase2.PRBaseLoader.loadClass(

Steps to Reproduce

  1. Log in as a developer.
  2. Access an existing case type, and view the life cycle.
  3. Click an existing step within that case type.

Root Cause

The log file showed LibraryFunctionNotFoundException and ClassNotFoundException errors for a few different functions and libraries.


Perform the following local-change and regenerate libraries.
  1. Open the System Management Application (SMA).
  2. Select Rule Utility Library Extractor from the Administration section.
  3. Click the Extract Libraries button. Do not enter any specific library names or rulesets. This will cause the system to regenerate all libraries.

Published March 29, 2016 - Updated October 8, 2020

Was this useful?

100% 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