Error when opening the section in designer studio
Hi
We get different error messages like
" Invalid static content request: (file "null" must have name and extension: foo.js)null",
And when the section finally opens in the designer studio, a portion of it (either controls or buttons) is blank or just a square box is seen. This happens to the out of the box sections also. I have attached a sample.
Message:"Invalid Url used is request"
Description: "The request sent by the client is syntactically incorrect"
The above message and description occurs for a image added to the button (webwb/pzgrid_downarrowwhite.png) When I checked the Image library, it is available, but in the section on click of the gear icon we get this error
Also to be noted: It happens only in the production environment and not in dev or QA. Please can any one help on this.
Thank you
***Updated by moderator: Lochan to add Categories***
Hi
The version of Pega is 7.1.6. We did clear the cache and restart the environment. The common scenario that we see is, this happens when the section has Inline styles.
Hi
Any help on this issue.
Thank you
Can you capture the network traffic when this happens? Either with Fiddler, or with the network capture feature of the Browser. This can often reveal critical information about the failure.
Hi
I tried to run the developer tool when opening a section on designer studio and found that there were 24 errors. I have attached a screen shot of it but could not understand how to fix it. Any guidance will be of great help.
Note: The same section in dev does not have any error.
The "404 not found errors" indicate you are looking for something in a place that either does not exist, is not accessible to your user, or the entity being looked for is not there. Figure out which of these possibilities it is, and fix it.
Regarding the 400 errors, examine carefully the entire URL. Something is malformed. It might be the result of the previous 404 error, or it might be something entirely different. Finding the malformed piece will guide you towards a solution.
Hi Nalins,
Could you please updload the complete Pega-RULES log, after replicating the use case.
Also, did you try truncating the cache table and extract marker file and restarting the environment.
Please also let us know which version of Pega platform you are using.
Regards,
Vikash