Symptom
Errors like below may be triggered by different actions and may be accompanied by additional symptoms.
Possible Symptoms When Entering Backoffice:
Depending on if there were already some fixing attempts like performing ant clean all you may see different symptoms.
- /backoffice page not found, while extension is listed in HAC as loaded.
- Page 'Error 500' tiggered on entering /backoffice page.
- errors in backoffice header after refreshing error 500 page and logging in.
- blank backoffice page after logging in.
Possible Console.log Errors:
Shows only during the first startup after the file gets missing:
ERROR [localhost-startStop-8] [ContextLoader] Context initialization failed
de.hybris.platform.servicelayer.media.NoDataAvailableException: de.hybris.platform.media.exceptions.MediaNotFoundException: Media not found (requested media location: backofficeconfiguration/h99/h06/8797907976222.xml) at de.hybris.platform.servicelayer.media.impl.DefaultMediaService.getStreamFromMedia(DefaultMediaService.java:274) ~[coreserver.jar:?]
at com.hybris.backoffice.config.impl.DefaultMediaCockpitConfigurationPersistenceStrategy$1.execute(DefaultMediaCockpitConfigurationPersistenceStrategy.java:60) ~[classes/:?]
Shows when accessing backoffice after 'ant clean all', when error 500 page is triggered:
ERROR [hybrisHTTP8] [Property] Failed to assign [label= ${labels.login.singlesignon.label}] to <A y2FQh>
de.hybris.platform.media.exceptions.MediaNotFoundException: Media not found (requested media location: backofficeconfiguration/h09/hc7/8798323343390.xml)
Shows when trying to log in to faulty backoffice after refreshing error 500 page:
INFO [hybrisHTTP8] [DefaultMediaCockpitConfigurationPersistenceStrategy] No data for media: cockpitng-config
If you do not have a shared media folder - additional errors may occur during fixing attempts if backoffice is concurently accessed from broken and fixed nodes:
ERROR [hybrisHTTP1] [DefaultCockpitWidgetEngine] Could not create widget view java.util.ConcurrentModificationException: null
It will fix itself after you re-open backoffice page again and/or restart server.
If someone is entering backoffice from node which is not yet fixed backoffice page on fixed nodes may go blank and above error will show.
This may happen if you do 'ant updatesystem' step without disabling access to backoffice on other nodes. If refresh of page does not help, restart of the server fixes this state.
Read more...
Environment
Discovered on SAP Commerce 1808
Product
Keywords
backofficeconfiguration cockpitng-config 500 blank-page blank page , KBA , CEC-SCC-CDM-CKP-COR , Core , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.