Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

ERROR - 404 on request: Failed to resolve rule file



Application developers and users observe wrong styles applied to text, buttons, and links in the PRPC application. When this issue occurs, there are numerous errors for static content in the PegaRULES logfile.

Error Messages

2015-06-29 05:20:55,058 [fault (self-tuning)'] [ STANDARD] [ ] (ticcontent.StaticContentClient) ERROR
- 404 on request: /5WLTDGgK-rG7mCyHWR_Ni9M1pztFIxjg*/webwb/css/desktopbase_1989329173.css!Failed to resolve rule file
Rule-File-Text.webwb.desktop_somethingskin.css!!.css; Referring URL: [URL]; Requestor ID: H7A5563C0AA030D7C3A5AF62A63BA1565


Steps to Reproduce

Not Applicable

Root Cause

Due to a rule resolution issue, the application searches in the wrong place for this CSS file. The application is not set up to use a custom CSS file, but it is attempting to resolve one.


As a local-change without applying a HFix, you can SaveAs the desktop CSS file as a custom desktop CSS file (for example, desktop_yourappskin.css). This will create the CSS file in the place that rule resolution can correctly access.

HFix-9610 addresses the underlying root cause of the incorrect rule resolution process.

Published July 24, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us