Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to login into Pega application



The application server that is hosting PRPC has started successfully, without error.
However, when user attempts to navigate to the login screen an error is displayed, and user is unable to log in.

Error Messages

Status fail
Message No such Rule-Application instance: MyApp 01.08.34
Operator ID Unauthenticated or not available
Requestor ID No ID available
Timestamp Thu Jul 02 15:47:57 MEST 2015
Engine Version PegaRULES 6.2 SP1 (coreAssemblyCached_62_0096) 

Steps to Reproduce

Navigate to the login screen (https://xxx:port/prweb/PRServlet)

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment.
When you initially navigate to the login screen, a BROWSER requestor is created. However, if that browser requestor is associated with an Access Group/Application that does not exist, then this can prevent the user from logging in.


This issue is resolved through the following local-change:

Your environment contains 4 requestor type per system (BROWSER, BATCH and others).
Out-of-the-box, there is a “prpc” and “pega” system.
Check whether the system name is currently used by your application server by looking at the “SystemName” configured in prconfig.xml. For example:

<env name="Identification/SystemName" value="yoursystemnamevalue" />
If the system name is empty then “pega” is used.
To login succesfully, follow the below steps:

1. If you are using a different system name than “pega”, configure the prconfig.xml file to use “pega” instead. Restart the server and attempt to login. This will use the BROWSER instance of system “pega” instead of your custom one.
2. If you use “pega” (or not specified” ), configure the prconfig.xml file to use “prpc” instead. “prpc” is actually deprecated and so should normally not be used, this is why we recommend to use “pega” first if possible.
3. Once you are in your system, check your requestor type instances and check if they reference an application which does not exist (or for any other incorrect configuration).
4. Once corrected, edit back your SystemName to the original value and test.
5. Do not keep “prpc” as system name.

Published July 22, 2015 - Updated October 8, 2020

Was this useful?

66.666666666667% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us