Failed to Load Groups and UI5 Libraries partially upgraded

[Virinchy]

Dear Experts,

Finally, i am also stuck with the most common error "Unable to load groups " when starting the Launchpad in 7.4 system with a central hub deployment running SAP_UI5 - SP10 and system details as below

.

In the process to fix this , we have applied all the required notes in the front end system as suggested here and followed the steps described here . As a result the UI5 runtime libraries should upgrade to 1.24.3 or higher, but only a few were only upgraded to 1.24.3 and rest in 1.24.2 and 1.24.1 .(SAP.FIORI , SAP.UISHELL ,SAP.Ushell_abap were in 1.24.3)

Screenshot of SAP Notes in front end system and SAP version running in browser

Screenshot taken from :

http://hostname:port/sap/bc/ui5_demokit/index.html#versioninfo.html  ,

Snote tcode in front end system and

checking the UI version with sap.ui.version in the browser when running Launchpad

Adding to that the launchpad designer also has an error loading the catalogs in chrome ,(Catalogs are loaded successfully in IE , screenshot attached)

Error: "Unable to load groups"

Console Logs:

http://Hostname:port/sap/opu/odata/UI2/INTEROP/TargetMappings?sap-cache-id=761167D9542EAA02F58CC4997... Failed to load resource: the server responded with a status of 404 (Not Found)

IWFND/ERROR_LOG

Any pointers to fix these ?

Regards

Virinchy

[masa_139 · Accepted solution]

Hi Virinchy,

Have you looked at SAP Fiori - SAP Fiori launchpad troubleshooting?

Regards, Masa

SAP Customer Experience Group - CEG

[Virinchy · Accepted solution]

, We have tried these steps as well, but facing the same error .

Is there any fix with UI5 libraries for this? Can we soon expect any new release of UI5 libraries/ Notes to fix this error ?

Regards

Virinchy

[Virinchy · Accepted solution]

The Page builder , Interop , Transport services in the front end services are pointed to the system alias of the backend instead of Local. (These are the front end services and should refer to the frontend) This created a mismatch for the hash key values comparing with the values in the table at USOBHASH for reading the metadata and throws an error of 404 .

Also making sure of applying the notes mentioned here and debugging the logs in browser console has helped.

Regards

Virinchy

[masa_139 · Accepted solution]

Hi Virinchy,

Thank you for sharing the solution. I see the root cause was the wrong system alias assignment.

Regards, Masa

SAP Customer Experience Group - CEG