In continuation to my previous blog cannot load tile – SAP Fiori, I continue discussion the other error we faced after the upgrade of S/4HANA system from 1511 to 1610.
“Could not open app. Please try again later”.
Ensure that the following steps are taken care off after the upgrade:
- Review OSS note 2346431 – SAP S/4HANA 1610: Release Information Note (https://launchpad.support.sap.com/#/notes/0002346431) and apply all the recommended notes mentioned for the target FPS/SPS level you just upgraded to. As a suggestion, apply all SAP_ABA, SAP_BW, and SAP_BASIS to both Frontend and Backend. While S4Core are only for backend.
- Ensure the scheduling of report /UI5/APP_INDEX_CALCULATE is running and if not, please schedule and run the job.
- Ensure the scheduling of report /UI2/GET_APP_DESCR_REMOTE is running and if not, please schedule and run the job.
- Ensure the following reports are also run in the Frontend Server:
If this does not solve your issue, jump to next steps:
Create RFC destinations as per SAP note SAP Note 2269272 and Replicate App Descriptors from Back-End System.
Check again if your app works. If not continue with next steps:
Compare the App details from the app launcher with the details on the SAP Fiori App Reference Library.
App launcher url looks like:
On app launcher, you should find the Odata (/n/iwfnd/maint_service) and ICF service (SICF) details for the app that should be active on the front end server:
Ensure that the SICF services are active and you are able to test it successfully and also the odata service is active and mapped to right System Alias.
Note: Service here points to local system alias as I have my front end and back end configured on the same application. Please check correctness of your alias to be used.
If you are not able to find the services for the app, its time for an incident towards SAP.
Please let me know if this solves your issues or if you have any questions in the comments below.
After upgrade of S/4HANA application from 1511 to 1610, we had few of our SAP standard Fiori apps choking.
Errors were different. Below are the steps we followed to fix “Cannot load tile”.
Edit home page:
Delete the tile:
Open app finder from the same screen:
Now you jump to the screen from where you can add the tiles you need.
Pin the tiles which you need.
Now go back to the home screen and see if you have the apps you need back on the screen.
2425949 – Analytical apps cannot be loaded.
2485294 – Cannot load tile after transporting from client to a client on the same system
2503862 – Cannot load tile Schedule Billing Apps
2471599 – Cannot load Fiori Analytical Applications
2594655 – Fiori Launchpad – Cannot Load Tile error on some tiles
When you change the password of connecting user of SAP HANA database, same should be updated in the key file of the HDBUSERSTORE on the Application Server.
You should be logged in with <SIDADM> for this procedure. Take care of this specially if you application server and database are running on same server.
#> hdbuserstore SET DEFAULT <hostname>:3<instance Number>15 <user> <password>
Note: User option -i along with the command if you want to enter the options (mainly password) interactively.
hdbuserstore SET DEFAULT hanahost:30015 SYSTEM Hana@123
Once updated check the list using the below command.
#> hdbuserstore list
DATA FILE : /home/appadm/.hdb/hanahost/SSFS_HDB.DAT
KEY FILE : /home/appadm/.hdb/hanahost/SSFS_HDB.KEY
ENV : HANAHOST:30015
You can now check the connectivity with the DATABASE using R3trans -d.
If R3trans -d reports error, check the connectivity with hdbsql using the key created above.
#> hdbsql -U <KEY> #Key is “DEFAULT” in our example.
This should connect to the database without any issues.
You might receive error sql code rcSQL = -10709 in case of connectivity issues. Please check the host name and port again in case of issues.
In case of any issues/questions please leave a comment below. Happy learning.
2250144 – FAQ: SAP HANA Secure User Store
2563762 – hdbuserstore still using old hostname after updating
2399996 – How-To: Configuring automatic SAP HANA Cleanup with SAP HANACleaner
2653777 – Phyton connection to HANA database using hdbuserstore-key fails
2416706 – Check file permissions for SAP HANA client hdbuserstore on application server
2130496 – Application does not start after takeover-HANA Disaster Recovery
2709350 – How To set a HANA System License via HDBSQL