Support Article

Data-Admin-Requestor instance "sdev718!BATCH" not found

SA-11777

Summary



I am trying to upgrade from PRPC 5.5 to Pega 7.1.8. After successfully loading the Rulebase, and redeploying the new prweb.war, PRPC's not able to initialize.

Error Messages



2015-06-16 12:02:20,083 [servername] [ ] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: servername
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:394)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1998)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:664)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:311)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:218)

Caused by: com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:249)
at com.pega.pegarules.session.internal.mgmt.PRRequestorBase.allocateSessionAuthorization(PRRequestorBase.java:539)
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.allocateSessionAuthorization(PRRequestorImpl.java:2009)
at com.pega.pegarules.session.internal.authorization.Authorization.reset(Authorization.java:433)
at com.pega.pegarules.session.internal.authorization.Authorization.reset(Authorization.java:382)
at com.pega.pegarules.session.internal.authorization.Authorization.onBeforeThreadUse(Authorization.java:1629)

... 28 more
Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "sdev718!BATCH" not found
From: (B8B4E9A1B18CEF72918E89369D4377B9D)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(SessionAuthorization.java:450)
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:245)
... 49 more


Steps to Reproduce



Restart the application.

Root Cause



Pega 7.1.8 shipped ‘sdev718’ as the default SystemName instead of ‘pega’. This only impacts upgrades from PRPC 6.1 SP2 and earlier because the ability to set prConfig settings in Data-Admin-System-Settings (DASS) was introduced in PRPC 6.2.
 

Resolution



Execute the below query to identify the systemName -
     select distinct pysystemname from pr_data_admin where pxobjclass like 'Data-Admin-Requestor';

Update systemName in the prconfig.xml with the following configuration parameter with the systemName -
<env name="identification/systemName" value="sdev718" />

Restart the server.
Suggest Edit

Published July 12, 2015 - Updated October 8, 2020

Have a question? Get answers now.

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