Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Dinesh Malikireddy (malid)
PEGA

Pegasystems Inc.
malid Member since 2015 2 posts
PEGA
Posted: Jul 10, 2015
Last activity: Apr 6, 2018
Posted: 10 Jul 2015 2:49 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

Data-Admin-Requestor instance "sdev718!BATCH" not found in 5.2 to 7.1.8 upgrade
We were performing the upgrade assessment for one of our customer from PRPC 5.2 to PRPC 7.1 ML8. The upgrade went successful and post upgrade after deploying the war/ear files the PRPC engine didn’t come up providing the following exception as it is referring to requestor type "sdev718!BATCH". Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "sdev718!BATCH" not found


**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 9 years ago
Posted: 10 Jul 2015 2:54 EDT
Ganesh Damisetty (Ganesh_Damisetty)
PEGA
Senior Manager, Cloud Engineering, PDC
Pegasystems Inc.
IN

Add <env name="Identification/SystemName" value="prpc" /> Entry in prconfig.xml file and Restart the Server, this should solve the issue. 

-Ganesh

To see attachments, please log in.
Posted: 9 years ago
Posted: 10 Jul 2015 3:02 EDT
Nandhini Nataraj (natan)
PEGA
Principal Software Engineer - Customer Success
Pegasystems Inc.

Hi,

 

Customers upgrading from PRPC 6.1 SP2 and earlier versions to 7.1 ML8 would envounter this issue. While upgrading an auto-generated prconfig.xml is used with setting source set to ‘file’ which ignores the DASS values.  And while bringing up the system post-upgrade, the system tries to use the setting from DASS.

 

We have overcome this issue by adding the following code in proconfig.xml and restarted the instance after which the PRPC engine was started properly.

 

<env name="Identification/SystemName" value="prpc" />

 

Thank you,

Nandhini

To see attachments, please log in.
Posted: 9 years ago
Posted: 6 Oct 2015 20:44 EDT
Dinu Pankajakshanraghavan (dpr_2018)
Cognizant Technology Solutions

Cognizant Technology Solutions
US
Hi ,I too got the below error when i did an upgrade from 55sp1 to 718 Caught exception while retrieving Data-Admin-Requestor instance "pega!BATCH".I changed the system name in prconfig and redeployed the ear and still facing the issue.Above solution is not working.
To see attachments, please log in.
Posted: 9 years ago
Posted: 9 Oct 2015 3:37 EDT
Dhevendra Earva (earvd)
PEGA
Senior Director of Cloud Engineering
Pegasystems Inc.
IN

Hi,

What is the system name you have updated in prconfig.xml file ?. Please share the system startup logfile.

 

Thanks,

Dhev

To see attachments, please log in.
Posted: 9 years ago
Posted: 26 Oct 2015 12:43 EDT
Jaffer Sathick Mohideen Abdul Kather (jafferSathick)
TCS
Engineering Lead
TCS
GB

After making the temp fix to switch the system name to PRPC in prconfig file, I believe one has to reconfigure the system name to the oringinal instance. For example, in the scenario posted in the question, the system name has to re-configured to 'sdev718' post-upgrade.

 

Thanks,

Jaffer

To see attachments, please log in.
Posted: 9 years ago
Posted: 2 Nov 2015 12:31 EST
Dinu Pankajakshanraghavan (dpr_2018)
Cognizant Technology Solutions

Cognizant Technology Solutions
US

Hi,

The issue has been resolved after changing the system name to prpc in prconfig.Thanks for your help.

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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