Support Article
Portals displays contain missing style sheets, 404 errors
SA-11168
Summary
Production Nodes are intermittently losing the style sheets on the user portal. Restarting the node fixes the issue.
Client side errors are HTTP 404, file not found, responses for style sheet requests associated to top level portal.
Server also throws a 404 error:
Error Messages
[ STANDARD] [ ] [ ] (ticcontent.StaticContentClient) ERROR - 404 on request: /iqNWzm3AMMz9xx9GNEy41Y_Tk5taLsxZmmCDZPF282k[*/webwb/pzskinv2_pzdesignerstudio_2fa2cf65d1357d12caf38c39aa870856d0540edfa641ed958d7099ff60b63bf3_2--4_13096454901.css!!.css; Referring URL: http://<app>/prweb/User/iqNWzm3AMMz9xx9GNEy41Y_Tk5taLsxZmmCDZPF282k%5B*/!STANDARD?pzPostData=-1430646426; Requestor ID: H9CDED9B0123D99DD06F4979ABC8E0DA3
[ STANDARD] [ ] [ ] (ticcontent.StaticContentClient) ERROR - pzskinv2_pzdesignerstudio_2fa2cf65d1357d12caf38c39aa870856d0540edfa641ed958d7099ff60b63bf3_2--4.css on request: /iqNWzm3AMMz9xx9GNEy41Y_Tk5taLsxZmmCDZPF282k[*/webwb/pzskinv2_pzdesignerstudio_2fa2cf65d1357d12caf38c39aa870856d0540edfa641ed958d7099ff60b63bf3_2--4_13096454901.css!!.css
[ STANDARD] [ ] [ ] (ticcontent.StaticContentClient) ERROR - 404 on request: /Snyp6ih1A0hrzKCNzEnrG7n8h7GVCwwK*/webwb/pzskinv2_pzdesignerstudio_2fa2cf65d1357d12caf38c39aa870856d0540edfa641ed958d7099ff60b63bf3_0--4_12531947152.css!!.css; Referring URL: http://<app>/prweb/User/Snyp6ih1A0hrzKCNzEnrG7n8h7GVCwwK*/!STANDARD?pzPostData=-877996457; Requestor ID: HD0E78A029230F3B80E315BBD9C7B7EE8
2015-03-03 14:28:31,659 [ttp-bio-10140-exec-8] [ STANDARD] [ ] [ ] (ticcontent.StaticContentClient) ERROR - pzskinv2_pzdesignerstudio_2fa2cf65d1357d12caf38c39aa870856d0540edfa641ed958d7099ff60b63bf3_0--4.css on request:
Steps to Reproduce
There is no specific use case to reproduce this issue.
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules.
Style sheets for portal level harness are auto generated at runtime and stored in the System-Static-Content class associated to the pr_sysgen_static_content database table.
The DeleteUnusedStaticContent agent runs every day and deletes the generated static content files in the System-Static-Content class. This should only be removing generated static content that is not currently being used. The problem is that the agent deletes portal level style sheets that are in use by currently compiled and in use portal level harness rules.
Resolution
This issue is resolved by HFix-22715.
Published June 29, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.