Pega Devstudio UI is not shown up after user login.
We were developing and running apps on the Pega Platform, but suddenly Dev Studio was not displayed on.
How should we resolve this ?
We were developing and running apps on the Pega Platform, but suddenly Dev Studio was not displayed on.
How should we resolve this ?
2024-12-17 09:45:11,903 [ttp-nio-8080-exec-29] [ STANDARD] [ ] [ PegaRULES:8] (a_Portal_DesignerStudio.Stream) ERROR stg-webnode-v.intra.stg.jp.local| Proprietary information hidden HAM8KUC8JPJEU4LQI9QK8VIKX7HFGC2Z6A [email protected] - Section 'HarnessFail' execution error on page 'pyDisplayHarness' of class 'Data-Portal-DesignerStudio'. java.lang.NoSuchMethodError: com.pegarules.generated.PageExists_080101__6096686135488994622.PropertyExists(Ljava/lang/String;)Z at com.pegarules.generated.PageExists_080101__6096686135488994622.PageExists08_01_01(PageExists_080101__6096686135488994622.java:117) ~[?:?] at com.pegarules.generated.PageExists_080101__6096686135488994622.invoke(PageExists_080101__6096686135488994622.java:82) ~[?:?] at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:238) ~[prprivate-generation.jar:?] at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:125) ~[prprivate-generation.jar:?] at com.pega.pegarules.generation.internal.library.LibraryFunctionUtilityImpl.resolveMethodCall(LibraryFunctionUtilityImpl.java:2932) ~[prprivate-generation.jar:?] at com.pega.pegarules.session.internal.mgmt.Executable.resolveMethodCall(Executable.java:12063) ~[prprivate-session.jar:?]
***Edited by Moderator Marije. to add INC case id***
Accepted Solution
Updated: 22 Jan 2025 21:56 EST
Rakuten Inc
JP
We followed the steps below and were able to resolve it.
Clear cache data
-
Shutdown all the nodes. Shut down all the nodes.
-
Backup the temp directory under the Pega installation directory from one node, and then delete it. The purpose of backing up the temp directory is to use it for identifying the root cause of the issue, although it is unclear how much it will help. Take a backup of the temp directory located under the Pega installation directory on one node, and then delete it.
-
Truncate the cache tables from the database. Truncate the following cache tables from the database:
- PEGA_RULES.pr_sys_appcache_dep
- PEGA_RULES.pr_sys_appcache_entry
- PEGA_RULES.pr_sys_appcache_shortcut
- PEGA_RULES.pr_sys_app_hierarchy_flat
- PEGA_RULES.pr_sys_ruleset_index
- PEGA_RULES.pr_sys_class_ancestors
- PEGA_RULES.pr_sys_rule_impl
- PEGA_RULES.pr4_rule_sysgen
- PEGA_RULES.pr_assembledclasses
- PEGA_DATA.PR_SYS_UPDATESCACHE
- PEGA_RULES.pr_sysgen_static_content
- PEGA_DATA.PR_SYS_STATUSNODES
- PEGA_DATA.PR_SYS_STATUSDETAILS
After above all,
-
Start one node and verify that there are no issues. Start one node and check if there are any issues. Clear the browser cache, navigate through the application, and open some rules to verify.
We followed the steps below and were able to resolve it.
Clear cache data
-
Shutdown all the nodes. Shut down all the nodes.
-
Backup the temp directory under the Pega installation directory from one node, and then delete it. The purpose of backing up the temp directory is to use it for identifying the root cause of the issue, although it is unclear how much it will help. Take a backup of the temp directory located under the Pega installation directory on one node, and then delete it.
-
Truncate the cache tables from the database. Truncate the following cache tables from the database:
- PEGA_RULES.pr_sys_appcache_dep
- PEGA_RULES.pr_sys_appcache_entry
- PEGA_RULES.pr_sys_appcache_shortcut
- PEGA_RULES.pr_sys_app_hierarchy_flat
- PEGA_RULES.pr_sys_ruleset_index
- PEGA_RULES.pr_sys_class_ancestors
- PEGA_RULES.pr_sys_rule_impl
- PEGA_RULES.pr4_rule_sysgen
- PEGA_RULES.pr_assembledclasses
- PEGA_DATA.PR_SYS_UPDATESCACHE
- PEGA_RULES.pr_sysgen_static_content
- PEGA_DATA.PR_SYS_STATUSNODES
- PEGA_DATA.PR_SYS_STATUSDETAILS
After above all,
-
Start one node and verify that there are no issues. Start one node and check if there are any issues. Clear the browser cache, navigate through the application, and open some rules to verify.
-
If everything is fine, start all other nodes. If no issues are found, start all the remaining nodes.
Thank you all and support center engineer.
NCS Pte. Ltd
SG
Hi @MasashiY: Is there any recent change in application (or) infra like hotfix installation (or) server patching?
Have you tried to restart the server by clearing pega temp?
Thanks.
Pegasystems Inc.
GB
@MasashiY I can see that you have logged support ticket INC-C1131 in parallel (please refer to these tickets to help track issues).
The GCS engineer is following the same line of enquiry as correctly stated by @ArulDevan .
-> Please continue to work with our GCS engineers in your ticket and update this forum post when you receive any progress/solution.
Rakuten Inc
JP
1) I have known about the browser cache problem on Pega platform already. But I tried to delete the cache this time, but I could not solve it. Other members tried to delete caches the same way, but the same error result was still shown.
2) We have restarted all node in our closter several time, but it did not changed, error happens.
3) All member that is using this pega platform have been facing this trouble now.
4) I'm also trying to login with Administrator. And the same error ocur now.
Updated: 20 Jan 2025 6:31 EST
Pegasystems Inc.
GB
@MasashiY please can I ask again that you work with our GCS team, and not through this forum post.
Our GCS engineer in ticket INC-C1131 is the one investigating your issue in detail, so please post your response and work with them to completion.
Rakuten Inc
JP
@MarijeSchillern OK. I might post here later.
Accepted Solution
Updated: 22 Jan 2025 21:56 EST
Rakuten Inc
JP
We followed the steps below and were able to resolve it.
Clear cache data
-
Shutdown all the nodes. Shut down all the nodes.
-
Backup the temp directory under the Pega installation directory from one node, and then delete it. The purpose of backing up the temp directory is to use it for identifying the root cause of the issue, although it is unclear how much it will help. Take a backup of the temp directory located under the Pega installation directory on one node, and then delete it.
-
Truncate the cache tables from the database. Truncate the following cache tables from the database:
- PEGA_RULES.pr_sys_appcache_dep
- PEGA_RULES.pr_sys_appcache_entry
- PEGA_RULES.pr_sys_appcache_shortcut
- PEGA_RULES.pr_sys_app_hierarchy_flat
- PEGA_RULES.pr_sys_ruleset_index
- PEGA_RULES.pr_sys_class_ancestors
- PEGA_RULES.pr_sys_rule_impl
- PEGA_RULES.pr4_rule_sysgen
- PEGA_RULES.pr_assembledclasses
- PEGA_DATA.PR_SYS_UPDATESCACHE
- PEGA_RULES.pr_sysgen_static_content
- PEGA_DATA.PR_SYS_STATUSNODES
- PEGA_DATA.PR_SYS_STATUSDETAILS
After above all,
-
Start one node and verify that there are no issues. Start one node and check if there are any issues. Clear the browser cache, navigate through the application, and open some rules to verify.
We followed the steps below and were able to resolve it.
Clear cache data
-
Shutdown all the nodes. Shut down all the nodes.
-
Backup the temp directory under the Pega installation directory from one node, and then delete it. The purpose of backing up the temp directory is to use it for identifying the root cause of the issue, although it is unclear how much it will help. Take a backup of the temp directory located under the Pega installation directory on one node, and then delete it.
-
Truncate the cache tables from the database. Truncate the following cache tables from the database:
- PEGA_RULES.pr_sys_appcache_dep
- PEGA_RULES.pr_sys_appcache_entry
- PEGA_RULES.pr_sys_appcache_shortcut
- PEGA_RULES.pr_sys_app_hierarchy_flat
- PEGA_RULES.pr_sys_ruleset_index
- PEGA_RULES.pr_sys_class_ancestors
- PEGA_RULES.pr_sys_rule_impl
- PEGA_RULES.pr4_rule_sysgen
- PEGA_RULES.pr_assembledclasses
- PEGA_DATA.PR_SYS_UPDATESCACHE
- PEGA_RULES.pr_sysgen_static_content
- PEGA_DATA.PR_SYS_STATUSNODES
- PEGA_DATA.PR_SYS_STATUSDETAILS
After above all,
-
Start one node and verify that there are no issues. Start one node and check if there are any issues. Clear the browser cache, navigate through the application, and open some rules to verify.
-
If everything is fine, start all other nodes. If no issues are found, start all the remaining nodes.
Thank you all and support center engineer.