Getting a red "X" without any exception or stack trace
We are using a composite portal where the home or default tab has list of work items on it.Sometimes we open some work objects on another tab and navigate back to home tab then we get an exception without any details.Only requester ID and login ID will be available.When we expand the exception nothing is visible.
This is not consistent.It is currently occuring only in higher environments only.I could see some entry in log whenever such exceptions occur.
( mgmt.base.ThreadUITransaction) ERROR - ERROR: posted transaction id '796038d4195864030ffbc6a31293f23c' for frame 'pyDisplayHarness' DOES NOT match record 'ed86d44e35f468464f88088d51a3de11'
Can anyone help me how to triage such issue.
Pegasystems Inc.
US
Hi Mootavishu,
Please make sure that all the environments are running the same version of PRPC and they are all running the same Hot Fixes. Also make sure that all the Application Servers across environments are the same Version and that they are all using the same JRE Version and JDBC drivers as well. Since the error message you are getting depends on the environment you are running on we suggest that for help on the specific issue you are encountering you please submit a Service Request (SR). You can do so by accessing the new My Support Portal (https://collaborate.pega.com/question/how-raise-sr-my-support-portal-how-question).
Regards,
Henry
Pega Academy
HCL Technologies Ltd.
IN
Thanks Henry,
We are running all the environments on the same PRPC 6.1 SP2 version.Do we have any special hotfix number for such issues so that we can check it across regions.
Pegasystems Inc.
US
Hi Mootavishu,
I searched our SR Database and found a related issue. Yes, there is a Hot Fix for it: HFix-4751
ROOT CAUSE
The root cause of this problem is a defect in Pegasystems’ code/rules.
RESOLUTION
HFix-4751 fixes a defect in the grid logic that can cause this issue.
Regards,
Henry
Pega Academy
HCL Technologies Ltd.
IN
Hi Henry,
Verified all the environments. This HFIX is available in the active hot fixes available.Can we find the root cause of the issue ain any other way?