Question
Last activity: 25 May 2016 12:31 EDT
Portal Corruption - common causes?
Finding all portals "messed up" on a freshly restarted ML7 system. This includes both developer portal and designer studio - even when logged in as [email protected]
It's like style sheets and static content are just not working right.
Tried refreshing browser cache but that did not help. Tried restarting the server
Have tried deleting static content via prsysmgmt but that does not appear to do anything.
Out of desperation, we tried
- down server
- delete pega temp path
- clear browser cache
- start server
to my surprise, that did the trick - partially. The application portal is still corrupted but designer studio works again?
Is this a common situation?
How should I debug this?
Shouldn't there be something in prsysmgmt to 'unhose' corrupted static content?
Accepted Solution
The resolution was ugly.
1) Shutdown node(s)
2) truncate pr_sysgen_static_content;
3) Clear Pega TEMP
4) Startup node(s)
There is one common cause to similar symptoms. Did you see any glaring errors in the logs? Such as 404s described here. https://community.pega.com/support/support-articles/portals-displays-contain-missing-style-sheets-404-errors
chase
US
Hi Andrew,
For earlier versions on PEGA 6, we sometimes face similar issue, as in portal seems not to load properly, try Revalidate and save for Rule-Portal-Skin, Rule-Portal and Rule-Obj-Html and see if that helps.
steps to revalidate
Designer studio-->System-->Release-->Upgrade-->Validate
Hope this helps
