Admin studio - Does not render landing pages
Hi All,
I have issue loading home page on one of the environment. It is working fine in another environments.
Does someone can suggest what could be plausible reason for this?
Accepted Solution
Updated: 5 Jul 2024 9:17 EDT
Pegasystems Inc.
GB
You did not specify what actions cause this - are you switching portals?
If not, issues like this have been known to happen if the pzFetchQueueProcessorInfo activity is taking a long time to load the data. This activity will run queries to get the counts for each of the queue processors.
Please look at your network trace files and pega logs.
Check if there are a number of PEGA0005 alerts generated during this process. You will need to check with your infrastructure team to clear Kafka related info and cleanup of data.
Please log a support issue via the MSP if you need further help .
Please provide the INC id here.
Eclatprime Digital Private Limited
SG
Hi Amit,
I hope your application is deployed in cloud i suggest you to check with the stream pods if it has any issue in coming up.
Also i suggest you to do a clean cache restart of the system with both DB and App cache clear which can solve the problem.
Macquarie
AU
Yes it is on clinet managed cloud.
there was a new build of application server.
Can you please elaborate your suggestion?
Thanks
Accepted Solution
Updated: 5 Jul 2024 9:17 EDT
Pegasystems Inc.
GB
You did not specify what actions cause this - are you switching portals?
If not, issues like this have been known to happen if the pzFetchQueueProcessorInfo activity is taking a long time to load the data. This activity will run queries to get the counts for each of the queue processors.
Please look at your network trace files and pega logs.
Check if there are a number of PEGA0005 alerts generated during this process. You will need to check with your infrastructure team to clear Kafka related info and cleanup of data.
Please log a support issue via the MSP if you need further help .
Please provide the INC id here.
Macquarie Group
PH
@MarijeSchillern I got the same issue in UAT Admin studio like this, and upon hitting tracer for the same activity, I'm getting this kind of error.
@MarijeSchillern I got the same issue in UAT Admin studio like this, and upon hitting tracer for the same activity, I'm getting this kind of error.
[MSG][Not enough privilege to execute][STACK][com.pega.pegarules.management.internal.system.operations.SystemOperationsException: Not enough privilege to execute at com.pega.pegarules.management.internal.system.operations.AbstractManagementAPI.checkSecurity(AbstractManagementAPI.java:237) at com.pega.pegarules.management.internal.system.operations.QueueProcessorManagementAPI.getAllQueueProcessorSummary(QueueProcessorManagementAPI.java:76) at com.pegarules.generated.activity.ra_action_pzfetchqueueprocessorinfo_8c7bfb7d78b026a49011a6fcc90fa416.step1_circum0(ra_action_pzfetchqueueprocessorinfo_8c7bfb7d78b026a49011a6fcc90fa416.java:167) at com.pegarules.generated.activity.ra_action_pzfetchqueueprocessorinfo_8c7bfb7d78b026a49011a6fcc90fa416.perform(ra_action_pzfetchqueueprocessorinfo_8c7bfb7d78b026a49011a6fcc90fa416.java:76) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:2873) at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.runRule(DeclarativePageDirectoryImpl.java:1780) at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.runLoadActivity(DeclarativePageDirectoryImpl.java:508) at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarePageLoadBatchTask.performTaskHook(DeclarePageLoadBatchTask.java:108) at com.pega.pegarules.exec.internal.async.AsyncServiceBatchTask.run(AsyncServiceBatchTask.java:495) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1381) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1124) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:931) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:897) at com.pega.pegarules.exec.internal.async.AsyncServiceBatchTask.run(AsyncServiceBatchTask.java:307) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) ]
Pegasystems Inc.
GB
@JerickEva please could we request that you do not post replies on closed posts?
A quick check on other PSC posts via a key word search reveals that likely the error message indicates that there is an insufficient privilege issue when trying to execute the checkSecurity function on the QueueProcessorManagementAP landing page. This typically occurs when the user or system does not have the necessary access rights to perform the action. To resolve this, you should verify the access roles assigned to the operator and ensure that they have the required privileges for the class involved, such as 'System-Queue-Notification'. Additionally, check if the 'Require authentication to run' setting is enabled in the activity related to the queue processor.
Access Control Policy failing for Queue Processor updates on case
Please use Ask a New Question if a PSC search does not help you identify other troubleshooting steps.