Support Article

Issue with static content on Pega 7.1.7 with CPM 7.1.3



User has upgraded PRPC and CPM from PRPC 6.1 to Pega 7.1.7.

The custom CSS files which were available on PRPC 6.1 are not generated in Pega 7.1.7 temp folder.

Images directly referenced are displaying correctly. But unable to download any CSS hence the images referenced in the CSS is not downloading either. The requestor ID in the logs look strange as well.

Error Messages

(ticcContent.StaticContentClient) ERROR - Internal Error on request:/oO909iMscyJc_fy6LnBDxfL3At36r8Aw8k{*/webwb/default_12321109455.css!!.css
2015-04-15 15:56:31,745 [fault (self-tuning)'] [ STANDARD] [ ] [ PegaDM:07.10] (tent.StaticContentResolverImpl) ERROR - Caught unhandled error in StaticContentResolver handling request aInput = {} doWithRequestorOrThreadLocked could not obtain requestor instance from {atn} e3byfUJEWFRoODhrUGdDc3laM21GbVNjdmZHZ1lyajR2T3A4OHYxRUp4bjN5Uy9rUTc0VzQ1b2tvNU5CTGJCaExzZnkxT0lHMUN1QTJ6QUkKdjdrK0KyNzhTUT09
atcom.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorOrThreadLocked. (

Steps to Reproduce

Upgrade from PRPC 6.1 to Pega 7.1.7. Observe that the custom CSS files 
available on PRPC 6.1 are not generated in Pega 7.1.7 temp folder.

Root Cause

The explanation for this behaviour is as follows: 
  • Custom CSS styles included at skin or harness level will be merged and generated as a single harness stylesheet as pzharness_(HARNESS_NAME)xxxx(auto-generated-code)xxxxx.css from PRPC 6.3 SP1 onwards.
  • In users case, custom CSS styles like cx_custom.css are generated on Pega 7.1.7 version, but in the form of pzharnessv2_performinternalxxxxx.css which was referred on UI pages.


The skin is not generated due to the usage of a wrong mixin. Use correct mixins to generate the skin successfully.

Published June 16, 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.