Question
Common Wealth Bank of Australia
AU
Last activity: 8 Mar 2017 7:14 EST
Pega 7.2 - Designer Studio in Development environment has broken
We are facing a weird issue on Pega development server.
There is absolutely no change in the Pega dev server or in Infrastructure.
But the designer studio is showing up as below
No errors on any of the logs.
The application is working fine in IE 9 but in Google chrome it is broken.
Not sure whether it is related but the only weekend OOTB agent running on the server is "PurgeAssemblyDatabaseCache". Could this have impacted anything on the cache?
Does anyone else have faced this issue or similar?
Please let us know.
Regards,
Sri
Accepted Solution
Common Wealth Bank of Australia
AU
We have raised an SR with GCS:
Although we have found a workaround as mentioned in the pdn link and the following worked for us.
https://community.pega.com/support/support-articles/portal-styles-do-not-load-after-logging
As we had followed the steps as mentioned in the PDN link and resolved the problem, before even we receive the response from Support team.
We couldn't try the below steps as mentioned by the GCS team,
1). Shutdown node(s)
2). Truncate "pr_sysgen_static_content";
3). Clear Pega TEMP
4). Startup node(s).
5). Revalidate the scenario.
Regards,
Sri
Pegasystems Inc.
IN
Hello Srividhya,
I found a similar post raised by another customer.
https://mesh.pega.com/thread/61223
For the above mentioned post, we suggested to raise an SR. If you find your issue to be on the similar line, I may request you as well to raise a SR with GCS.
Pegasystems Inc.
IN
If you end up raising an SR for this issue , I request you to share the SR number here, so that we can track it for you within the thread.
Thanks,
Vidyaranjan A V | Community Moderator | Pegasystems Inc.
Accepted Solution
Common Wealth Bank of Australia
AU
We have raised an SR with GCS:
Although we have found a workaround as mentioned in the pdn link and the following worked for us.
https://community.pega.com/support/support-articles/portal-styles-do-not-load-after-logging
As we had followed the steps as mentioned in the PDN link and resolved the problem, before even we receive the response from Support team.
We couldn't try the below steps as mentioned by the GCS team,
1). Shutdown node(s)
2). Truncate "pr_sysgen_static_content";
3). Clear Pega TEMP
4). Startup node(s).
5). Revalidate the scenario.
Regards,
Sri
Cognizant
IN
Couple of things we could try...
- SMA >> ETier Static Content Management >> Click the button Delete Rule-File Cache Only
- Re-validate and save the concerned skin rule (when this occurs in a business user portal)