Unable to login after upgrade
Pega engine can't be initialized post upgrade
**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.
Pegasystems Inc.
Issue might be because of configuring custom Access Group to the System Name: Pega. It can be solved by following below steps.
1) Add Dynamic System Settings in prconfig.xml
<env name="Identification/SystemName" value="prpc" />
2) Restart application server
3) Change the access group to PRPC:Agents for the system Name Pega: Batch
4) Undo the change made in prconfig.xml in the step 1
5) Restart application server
6) User will be able to login
Scope International
SG
Hi Natan,
I am also facing similar issue migration of the lower ENV rules after upgrade. We changed the ENV to PRPC and Restarted the application server. Can able to access the URL but not able to login with [email protected] operator too. Only can see Blank Screen. Not able to proceed with the 3 rd step you mentioned above. Can you please help me to understand the step3. Do we need to change the access group in DB or from PRPC portal?
Thanks In Advance.
Cognizant Technology Solutions
US
Hi Prameela,
Check the prconfig.xml from Pre-upgrade system and use the same value in <env name="Identification/SystemName"> tag in the new environment prconfig.xml. It is not necessary to have the system name value as prpc always. If it is customized, use the same name in the new environment. Also, verify the logs to see if the error occurring 'Data-Admin-Requestor instance "pega!BATCH" not found'. If yes, changing the SystemName would solve the issue.
Best Regards,
Accenture
IN
Is it during upgrade from 6.x to 7.x. or from 5.x to 7x?
Regards
Shankha
Incessant Technologies
IN
I have seen multiple queries/posts with above system name issue in upgrade forum. This seems to be one of the common issue encountered during upgrade. Can we have an article published with the problem statement, root cause and the steps to resolve? We do have multiple articles on common upgrade issues encountered. I am not sure if we have one for the above mentioned issue.
Updated: 1 Jun 2016 5:49 EDT
Cognizant
IN
We have faced such issues earlier; the articles below have helped us every time.
(SA-16161) https://community.pega.com/support/support-articles/system-error-startup-after-upgrading-prpc-55-sp1
(SA-14866) https://community.pega.com/support/support-articles/pegarules-initialization-fails-error-message-log
(SA-11777) https://collaborate.pega.com/discussion/data-admin-requestor-instance-sdev718batch-not-found-52-718-upgrade
(SA-8670) https://community.pega.com/support/support-articles/pegarules-initialization-fails-after-pega7-upgrade
(SA-8411) https://community.pega.com/support/support-articles/pega-717-does-not-restart-after-changing-systemname
(SA-4859) https://community.pega.com/support/support-articles/unable-start-application-server-after-upgrade-prpc-v717
(SA-655) https://community.pega.com/support/support-articles/system-name-changes-when-we-do-updateupgrade