portal login error
Hi All,
Below is my Login Screen
When I logged in, the page redirect to error page like below picture:
and when i reload the url, the page redirect to the below page:
Hi All,
Below is my Login Screen
When I logged in, the page redirect to error page like below picture:
and when i reload the url, the page redirect to the below page:
and below is the error message in JBOSS
15:49:37,956 STDOUT [stdout] (Dispatcher-Thread-95) 2018-01-09 15:49:37,956 [tp-/xx.xxx.x.xx:80-1] [ STANDARD] [ ] [ HRAPP:01.01.01] (eOnOpen.Rule_PortalSkin.Action) ERROR xxx.xxxx.co.id|xx.xxx.x.xx MaintainERec@xxx - UnresolvedAssemblyError - Method "Exit-Activity" (class
"com.pega.pegarules.exec.internal.rules.methods.MethodExitActivity") is not recognized
15:49:37,967 STDOUT [stdout] (Dispatcher-Thread-95) 2018-01-09 15:49:37,959 [tp-/xx.xxx.x.xx:80-1] [ STANDARD] [ ] [ HRAPP:01.01.01] (ngineinterface.service.HttpAPI) ERROR xxx.xxxx.co.id|xx.xxx.x.xx MaintainERec@xxx - xx.xxx.x.xx: com.pega.pegarules.pub.PRRuntimeError
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
Please Help Me All, How Can I Fix This?
Pegasystems Inc.
US
Hi Adrian,
As a basic test could you clear the PegaTemp cache folder and try to restart the appserver to test the behavior as i can see UnresolvedAssemblyError. Also kindly share the complete PegaRULES log once you test the behavior to troubleshoot further.
Regards
Mahesh
EPAM Systems, Inc.
ES
Adding to Mahesh,
If issue still persist,
You can truncate the following cache tables. Restart after truncation and delete the PegaRULES_Extract_Marker.txt file.
TRUNCATE TABLE PR_SYS_APP_HIERARCHY_FLAT;
TRUNCATE TABLE PR_SYS_APP_RULESET_INDEX;
TRUNCATE TABLE PR_SYS_CLASS_ANCESTORS;
TRUNCATE TABLE PR_ASSEMBLEDCLASSES;
TRUNCATE TABLE PR4_RULE_SYSGEN;
TRUNCATE TABLE PR_SYS_APPCACHE_ENTRY;
TRUNCATE TABLE PR_SYS_APPCACHE_DEP;
TRUNCATE TABLE PR_SYS_APPCACHE_SHORTCUT;
TRUNCATE TABLE PR_SYS_CACHE_DEP;
Adding to Mahesh,
If issue still persist,
You can truncate the following cache tables. Restart after truncation and delete the PegaRULES_Extract_Marker.txt file.
TRUNCATE TABLE PR_SYS_APP_HIERARCHY_FLAT;
TRUNCATE TABLE PR_SYS_APP_RULESET_INDEX;
TRUNCATE TABLE PR_SYS_CLASS_ANCESTORS;
TRUNCATE TABLE PR_ASSEMBLEDCLASSES;
TRUNCATE TABLE PR4_RULE_SYSGEN;
TRUNCATE TABLE PR_SYS_APPCACHE_ENTRY;
TRUNCATE TABLE PR_SYS_APPCACHE_DEP;
TRUNCATE TABLE PR_SYS_APPCACHE_SHORTCUT;
TRUNCATE TABLE PR_SYS_CACHE_DEP;
TRUNCATE TABLE PR_SYS_CACHE_ENTRY;
TRUNCATE TABLE PR_SYS_CACHE_IMPL;
TRUNCATE TABLE PR_SYS_CACHE_DEP;
Kindly note:- Truncating cache tables is not something that should be done as part of a standard operating procedure. If the issue is occurring often, please contact GCS through an SR for root cause analysis.
Hope it helps in resolving the issue at your end, please mark this post as answered if it does.
Regards,
Asif
KBRU
ID
Thank you for your answer Mahesh and AsifHasan,
Can You Tell Me where is the location PegaTemp Folder or PegaRULES_Extract_Marker.txt file?
My PEGA Application is PEGA V 7.2.1. After I searching in pdn (https://collaborate.pega.com/question/how-clear-cache-721-version), PegaRULES_Extract_Marker.txt file. has been removed in PEGA 7.2.1.
When I Searching folder with "PegaTemp" keyword in jboss folder, windows explorer said "No items match your search".
and when I search with "temp" keyword in jboss folder. there is temp in jboss/standalone/tmp/vfs/temp. Is this the PegaTemp cache folder?
Pegasystems Inc.
IN
Hello Adrian ,
In my local jboss i found the Temp directory in below path where the logs also present
"F:\Application Servers\jboss-eap-6.4\standalone\tmp\work\jboss.web\default-host\prweb"
You can create your PRPCTemp directory like with below binding name in domain:naming subsystem element of your configuration file .
<simple name="java:/url/pega/none" value="temp/directory/path"/>
I have followed below document
https://docs-previous.pega.com/pega-721-platform-installation-guide-jboss-red-hat-eap-and-oracle
So you can follow below steps now
1)Create your own Temp Directory by editing either standalone or standalone-full.xml
2)Stop your application server .
3)Clear the temp folder .
4)Truncate cache tables .
5)Restart your application server and test the usecase .
Thanks,
Arun