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

System-Work-Indexer not found in dictionary upgrading 5.4 SP3



User is upgrading from PRPC 5.4 to Pega 7.1 and receive an error: Class not defined in dictionary: System-Work-Indexer aClassName PRThread.createPage

Error Messages

2015-03-20 13:46:20,396 [ ] [ STANDARD] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(
at com.pega.pegarules.session.internal.mgmt.EngineImpl.startEngineImpl(
at com.pega.pegarules.session.internal.mgmt.EngineImpl.startEngine(
at com.pega.pegarules.session.internal.mgmt.EngineImpl.startEngine(
at com.pega.pegarules.deploy.internal.archive.ParUtilsImpl.ensureEngineStarted(
at com.pega.pegarules.deploy.internal.util.ImportImpl.importArchive(
at com.pega.pegarules.deploy.internal.util.ImportImpl.main(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(
Caused by: InvalidParameter Class not defined in dictionary: System-Work-Indexer aClassName PRThread.createPage
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.createPageInternal(
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.createPage(
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.createPage(
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.createPage(
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.initializeSystem(
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(

Steps to Reproduce

Upgrade Pega 5.4 to 7.1 on Oracle 11g DB referring the PegaRULES Process Commander Upgrade Guide.

Root Cause

The root cause of this problem is defect or misconfiguration in the PRPC operating environment.

On the PRPC 5.4  SP3 system the dynamic system setting (DSS) indexing or enabled is set to true.  

As a result when the engine is started to do the upgrade it is trying to run work indexing.  Starting in PRPC 5.5 work indexing uses the System-Work-Indexer class.  
Since the PRPC 5.4 SP3 database that is being upgraded does not contain this class the Pega 7.1 engine fails when looking for it.


This issue is resolved through the following local-change: 

In PRPC 5.4 SP3 system, change the DSS for indexing or enabled to false.  

With this change the upgrade to Pega 7.1 runs fine.


Published March 10, 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