Portal Theme Editor does not open Portal 7.4 SP10

[SandipAgarwalla]

Hi Experts

We currently have an issue with the Theme Editor in Portal The Editor does not open, but just a blank page.

Tried in all 3 browsers, but the same issue.

Found the following errors while accessing the editor, seems like some issue with the UI rendering libraries

[removed per request] Failed to load resource: the server responded with a status of 404 (Not Found)

UCF_RequestUtil.sendRequest @ :5

[removed per request]

[removed per request]

404 (Not Found)

UCF_RequestUtil.sendRequest @ lightspeed.js?M6v7Z52F7f-VQKKE5-dV7A==:61

UCF_RequestUtil.sendSyncRequest @ lightspeed.js?M6v7Z52F7f-VQKKE5-dV7A==:61

UCF_MessageBundle.loadTexts @ MessageBundle.js:1UCF_MessageBundle.sGetRawText @ MessageBundle.js:1

UCF_MessageBundle.sGetText @ MessageBundle.js:1UCF_LS.sGetText @ lightspeed.js?M6v7Z52F7f-VQKKE5-dV7A==:54UCF_LS.attachOfflineListener @ lightspeed.js?M6v7Z52F7f-VQKKE5-dV7A==:54

UCF_LS @ lightspeed.js?M6v7Z52F7f-VQKKE5-dV7A==:54(anonymous function) @ PageBuilder;jsessionid=OAseZ-f-34IhVKr-r4lMp7SB31gcTgGkf3QA_SAP:1

Any correction note to be applied?

Thanks

Sandip

Message was edited by: Moshe Naveh

[hemanth2 · Accepted solution]

Hi Sandip,
 

Hope you are doing good.

Along with the SP upgrade point, please do a force bootstrap as well, as this may help.

Such an issue can be caused due to inconsistencies and it will be worthwhile to run the force bootstrap once:

1)

Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename
the bootstrap folder as this is needed for the sync process.
2)

Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.

3)

Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.

4)

Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.

Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth
SAP Active Global Support

_ _ _ _ _ _ _ _ _
 

[SandipAgarwalla · Accepted solution]

Thanks Samuli, Hemanth

Re starting the server couple of times seem to fixed the issue.

Regards

Sandip