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.
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.
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.
Posted: 5 years ago
Posted: 9 Oct 2015 3:37 EDT
Dhevendra Earva (earvd)
Senior Manager, Cloud Engineering
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.
Posted: 5 years ago
Posted: 27 Oct 2015 1:05 EDT
Nandhini Nataraj (natan)
Principal Software Engineer - Customer Success