Hi,

To work around the issue and get the Pega login page to display, place the below entry in prconfig.xml and restart JVM

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

Try this and see if issue is resolved or not.

Thank You.

Hi MattE957,

Thanks for attaching the stack trace as it definitely helps but also raises a couple of questions.

1. was there any Pega application (R-A-P) deployments done recently?

2. Application definition changes

3. Access Group configurations

4. Is this account a local pega account or is the authentication/authorization done via SSO/external to Pega

The above questions are come from reviewing the stack trace information:

Caused by: com.pega.pegarules.pub.context.InvalidApplicationReferenceException: No such Rule-Application instance: ALMFW:01.01.01
From: (H4FBA505A24118CD163772EDFED0C8948)

This indicates (at least to me) that either a built-on application or application dependency could find not find application ALMFW:01.01.01  which would appear to be framework application;  which also indicates a relatively new deployment where the R-A-P did not include the ALMFW or the separate deployment for ALMFW was not deployed which would appear to affect your authorization process (especially if authorization logic resides in the ALMFW layer)

hope this helps.

Rob

To work around the issue and get the Pega login page to display, the following entry can be placed in prconfig.xml:

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

The System Name prpc is a special value that is associated with its own Browser Requestor.

After logging into Pega using administrator@pega.com / install,  look at the Browser REQUESTOR:

REQUESTORS are located under Records -> SysAdmin->Requestor Type

Open the Browser REQUESTOR then open the Default Access group, verify Access Group saved correctly or not.

Update,

 The problem was fixed by following the procedure below :

https://community.pega.com/support/support-articles/initializationfailederror-log-file-during-prpc-start