SAP HANA 2.0 SPS03 on HANA Express – The (very good) first impressions
There are so many new features that I do not even know where to start! I have been playing with these for the last weeks and updating tutorials on XS Advanced. But I had to contain my excitement and wait until everybody else could get their copy.
And with Rudi’s announcement yesterday, it’s sharing time!
There are plenty of very cool features released in SAP HANA, express edition 2.0 SPS03, some are at plain sight and some not. This is my own recollection of the some of them.
If you want a full list of the updates, explained by the mere makers and experts of the product, you cannot miss the free webinars starting on Monday: https://blogs.saphana.com/2018/03/05/sap-hana-expert-webinar-series-march-2018/
This a teasing attempt to convince you that dedicating an hour of your time to those webinars is a great investment:
If the updates or new features had a “wow” effect on me and I had the chance to update the tutorials with them, you will find them in this blog post. It would be no fun if I mentioned them and did not help you try them out. There are some other updates that I think deserve their own chapter and we will get there.
I am using SAP HANA, express edition, from the launcher in Google Cloud Platform to take screenshots of this.
HXE has something to say to you
Even if you do not talk to your HANA instance, she has something to say to you. From the HANA cockpit (default for HXE is https://hxehost:51042) you can access notifications with interesting updates:
For example:
The XS Advanced cockpit
The old XSA admin tool is gone and this one has taken over. This is not really a new feature but it has some updates itself and is included by default in HANA express now.
Those who have attended my CodeJams on XS Advanced know that we make some tweaks when Web IDE needs more room to run. The part in which we stop services we are not using can be done from here too:
Allergic to the command line? Stop sneezing for UAA services
Steps are also documented in the first tutorial for the Getting started with XS Advanced development series. There is a wizard in the cockpit that will create the UAA service for you:
Those user-provided services
Another feature that makes our lives easier in the XSA cockpit (it was there before, though not installed in HXE).
Remember how you needed to create a “user-provided service” for situations like making an HTTP request or accessing a classic schema? Well, you still do.
However, you do not need to go into the console for that and struggle with the double quotes.
If you are looking for more, Denys van Kempen posted a very nice intro and tour of the cockpit here.
Information Access is installed by default
There were some requests for this and they were heard. The main problem was not really installing the plug-in in HXE but getting to it, as you needed a username for the marketplace and a valid license.
You can now go back to using Live connections to your calculation views in XS Advanced from HANA Express out of the box.
The steps to configure InA are still here and valid. You can now jump to the part where you “Configure the tenant database” and continue having fun with Calculation Views.
By the way, there’s also a lot going on in the HANA modelling world, so there goes another reason to check out the update sessions.
The clients for HANA are available from the tools repo
I don’t think this needs any further explanation on why I think it is great to have them so handy https://tools.hana.ondemand.com/#hanatools:
VERY easy cross-container access
We all want to tap into the master data created in another MTA (or the data generated automatically by the Data Generator in the SHINE model. It’s as easy as this right-click now:
It creates the resource in the mta.yaml file and shows that DB module who’s boss and also who is the default target HDI container.
I think the updated tutorial explaining how to access containers by means of synonyms and grant files shows how much this has been simplified.
Stepping into a procedure or function call during SQL debugging
Rich Heilman lists many other cool new features in his blog, including this one.
https://blogs.sap.com/2018/04/11/sap-hana-2.0-sps-03-new-developer-features-database-development/
No picture here, go to that blog post and see it for yourself if you haven’t already, because it is completely worth it.
So if you have made it this far, I’d really like to know which features are a pleasant surprise to you too. As always, let’s stay in touch in Twitter or on LinkedIn .
All the great news! I am looking forward to upgrade my HXEs to SPS3 next week 🙂
Thanks for that 🙂 It did not happen to me (but I tried upgrading in an unconventional HXE), but you might want to watch out for this: https://answers.sap.com/questions/482999/sap-hana-20-sps-03-after-update-error-variable-can.html
Hopefully I called the attention of the right people and the note gets responded
The mentioning issue only occurs with systems that have “mapped spaces” to the tenant
one more things about upgrades to watch out for:
The installation of the new cockpit will fail for the first time (not fully installed).
Reason the “di-builder” in spaces is not automatically updated to the new version of “di-core”, so after the upgrade you should go to “di-space-enablement-ui” and update it manually (see “Builder Version” and the “DI Core Version” and “outdated”).
Then re-run the upgrade shell again and it will install properly.
Hope this will help other people by upgrading ?
It would be good to reproduce and fi it..So just by upgrading an instance with a tenant mapped to a space I get this error ?
Hi Lucia,
The issue I was referring to with “systems that have mapped spaces” is “XS_APPLICATIONUSER” described in “https://answers.sap.com/questions/482999/sap-hana-20-sps-03-after-update-error-variable-can.html”.
The other issue “New cockpit failed” was due to “Di-Builder” not updated automatically during the upgrade (both spaces “SAP” and “Development”). If the reason for this was the mapping (SAP Space) or not, I will try to check that.
Hi
When installing HANA express, is it best to enter FQDN or just the local host name for the server? It seems that local host name is the most common way. But I think FQDN is needed to generate the correct certificates. Do you have any guidelines / tips ?
Br Petter Huseby
Hi Peter, is it giving you an option to change the fqdn or do you want to rename the host at is level? What installation type are you referring to?
Changing the name is possible but I have randomly faced some issues so have not done a post on that.
Petter, my experience when doing a binary install is definitely use a FQDN (important that there be 2 dots) or you get intermittent errors at random points of the install. Maybe it's improved in SPS03, but even as recently as SPS02, this gave me fits.
Lucia,
Thanks for your post! I was able to go for the VM Server-Only version and get INA up and running, so I am happy. However I noticed that it seems that the (old, I know) Web-based Development Workbench is now missing in SPS03. It was nice to use this instead of the (older) HANA Studio Eclipse plugin. Is this because the Web-based Development Workbench is now completely deprecated in SPS03 or just to cut down on HANA Express file/memory footprint? I can resort to HANA Studio and commandline so it's not the end of the world for me, and XSA is out of scope for memory savings reasons.
Hey, Mike! The installation files are still there but in a different directory. I would still recommend to stay away form the old web editor workbench. It has some problems and because it's been deprecated it is not getting any more love.
HANA studio is then your best option but if you really want to suffer and install it just the same, the installation files should be in /hana/shared/HXE/global/hdb/content (I'm at the airport now so I'm having trouble loading a console right now, you would be looking for SAP_WATT and HANA_IDE_CORE).
Cheers,
Lucia.
Ah cool, I see it:
And duly noted about not using the Web-based Development Workbench but it's sometimes nice to have 🙂
Just to follow up, I managed to install it and it's working for the things I use in there. Thanks again for the hint!
Thanks to you for the update 🙂
Hi Lucia,
We just upgraded our CAL HANA Express 2.0 SP 2 to SP 3. We no longer have Nodejstools running. I have created a question about this - https://answers.sap.com/questions/607173/xsa-webide-has-no-nodejs-build-option-after-cal-ha.html
Also when WebIDE starts, we see the error with Unable to Load features:
https://answers.sap.com/questions/607175/xsa-webide-unable-to-load-features-after-cal-hana.html#
It's been a real challenge working on HANA Express 2.0 SP 2 and we had so many issues with the WebIDE and we were hoping upgrading it to SP 3 would resolve them but we are stuck. If you can provide some help, that would be great.
Thanks,
Jay
Hi Lucia,
We started the Google HANA 2.0 SPS 3 which was working great for a day. Now the webIDE just does not start.
We tried the following:
We are trying with both Safari and Chrome browsers.
So even though webide shows as started in the xs apps list, we cannot connect to it. Before we were able to connect to it - but we cannot run the web modules. Not sure what is going on and how to fix this issue.
Regards,
Jay
In all of your questions, you need to include details. It really is hard to try to help you. What is "Web IDE does not start"? It does not load in the browser or you do not get a response from the server? The process if you list xs a | grep web ide shows "STARTED" but "0/1"? It starts but you cannot run the web modules?
Have you scaled di-core and di-runner already? What does "xs logs webide" say?
Hi Lucia,
We were going through the XSA tutorials and everything was working great for a day. Then we were no longer able to run the web module - it would show the error (MessageBus) Web socket 'wss://hxehost:53075/che/ws/u4phd' is not available: 1006
Then after a while, we could not even log into the webIDE.
We see the app running:
webide STARTED 1/1 512 MB <unlimited> https://hxehost:53075
However, the webide is timing out....
We did xs logs webide --all
Here are some error messages that seem relevant:
We will get you the full log file. We are using the Google cloud SSH browser session but the file download is not working from the menu option. We are generating an SSH key and will then be able to get you the file.
Thanks,
Jay
Hi, Jay,
We don't need the entire log and this thread belongs in the Q&A. You need to check for errors there (it is tricky because not every error is a problem). xs logs webide --last 50 will give you the last 50 lines in the log, for example. I would look at the console in the browser first.
The last thing I see is that you are being redirected to UAA to log in. So the app is up and running. Again, what is timing out? Do you get to log in? Can you capture the latest error messages? Did you check the console in the browser (F12)? Are you using a fresh incognito window? is this a deployment from the marketplace in GCP or something you installed yourself? Did you scale the backend services?
Lucia
Hi Lucia,
The system is from the Google Cloud Platform. We can't even log in now - WebIDE starts loading - but just hangs. We can get to XSA admin app at port 39030 but we still cannot get to the WebIDE. Seems like something got messed up and the webIDE is no longer working correctly. We have not scaled the backend services.
We even tried to xs restage webide.
Here is a subset of the log file.
Thanks,
Jay
Nothing useful in that log unfortunately. Why not scaling the backend processes which is a known problem (xs scale di-core -m 512M and xs scale di-runner -m 512M)? What about the other questions I asked?
Hi Lucia,
So when we try to connect to the WebIDE - the progress hangs at right under the HANA word :
Can we somehow refresh the webide cache? We did a xs restage webide and have also done a start and stop. Not sure what to do next.
Thanks for your help. It's been a real challenge to us to get a stable working development environment for HANA XSA.
Regards,
Jay
It looks like it's stuck on this step:
Hi Lucia,
So we tried to launch the WebIDE again several times and we are definitely seeing the pattern. It seems that when we have the web socket error, that's when the webide basically hangs:
So here is a full capture of when we try to start the webide:
Thanks,
Jay
For the last time…
And bringing the question from the other thread... what are the logs from di-core saying?
Hi Lucia,
We did get to the login screen and were able to enter the credentials.
Here is the console log details
- we have attached a screenshot too:
We are going to scale the backend process next and will update this post. Also, i had seen a way to launch the webide passing some flags to refresh and workspace or anything cached in it?
Thanks,
Jay
Hi Lucia,
We got through one hurdle - so the webide is coming up now. We had to launch it with:
https://hxehost:53075/watt/index.html?settings=ignore
We also ran the following to scale the backend:
xs scale di-core -m 512M
xs scale di-runner -m 512M
We can build and run the NodeJS modules.
We are running into an issue with the web module - build works but run does not. We are now looking into it.
Thanks for your help.
Regards,
Jay
Hi Lucia,
The web module is also working. There was a typo in the tutorial and I have provided feedback. 🙂
Thanks so much for your help!
Cheers,
Jay
Hi Lucia,
We recently installed HANA XS WEBIDE and URL launch is ever haning. We tried the following but still same issue.
1. Tried different versions of HRTT and WEBIDE and webide lauch is ever hang
2. Restarted HANA and XSA
Could someone suggest what causing the issue Here.
Version details -
HANA Version - 2.00.037
XS version - xs v1.0.115
com.sap.xsa.admin 1.7.1
com.sap.devx.webide 4.1.48
com.sap.core.account 1.1.13
com.sap.xsa.hrtt 2.9.42
alm-product-installer 1.17.1
Error log - xs logs webide --all > webide1.log
=========================
5/1/20 10:31:00.883 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:00:883#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o242z2#PLAIN##GET request to /watt/resources/sap/watt/ui/library-preload.js completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/ui/library-preload.js'# 5/1/20 10:31:01.734 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:01:734#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o243ms#PLAIN##GET request to /watt/resources/sap/hana/sqlanalyzer/webidex/ui/theme/style.css completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/hana'# 5/1/20 10:31:02.285 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:284#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2441y#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Browser.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.288 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:288#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o24421#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/Editor.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.290 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:290#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o24427#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/CodeCompletion.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.293 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:293#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o24423#PLAIN##GET request to /watt/resources/sap/watt/common/plugin/aceeditor/service/Editor.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/plugin/aceeditor'# 5/1/20 10:31:02.294 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:294#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2442b#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Config.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.296 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:296#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2442c#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/PrefixCalculation.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.298 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:297#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2442f#PLAIN##GET request to /watt/resources/sap/watt/common/service/platform/DocumentProvider.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.301 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:301#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2442i#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/ConfigAvailability.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.305 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:305#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2442l#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Displayinformation.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.306 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:306#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2442m#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/UndoRedo.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:31:02.331 AM [APP/2-0] SYS #2.0#2020 05 01 10:31:02:331#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2443d#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Part.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:51.181 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:51:180#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2og8a#PLAIN##GET request to /watt/sap-ui-cachebuster completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/sap-ui-cachebuster'# 5/1/20 10:46:51.596 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:51:595#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ogjt#PLAIN##GET request to /watt/resources/sap/watt/ui/library-preload.js completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/ui/library-preload.js'# 5/1/20 10:46:52.354 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:52:354#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2oh4v#PLAIN##GET request to /watt/resources/sap/hana/sqlanalyzer/webidex/ui/theme/style.css completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/hana'# 5/1/20 10:46:52.988 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:52:988#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohmh#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Browser.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:52.991 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:52:990#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohmj#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/Editor.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:52.992 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:52:992#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohml#PLAIN##GET request to /watt/resources/sap/watt/common/plugin/aceeditor/service/Editor.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/plugin/aceeditor'# 5/1/20 10:46:52.994 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:52:994#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohmp#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/CodeCompletion.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:53.004 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:53:004#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohmu#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Config.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:53.005 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:53:005#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohmv#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/PrefixCalculation.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:53.006 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:53:006#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohmx#PLAIN##GET request to /watt/resources/sap/watt/common/service/platform/DocumentProvider.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:53.007 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:53:006#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohmy#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/ConfigAvailability.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:53.010 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:53:010#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohn3#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Displayinformation.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:53.011 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:53:011#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohn5#PLAIN##GET request to /watt/resources/sap/watt/common/service/editor/UndoRedo.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'# 5/1/20 10:46:53.028 AM [APP/2-0] SYS #2.0#2020 05 01 10:46:53:028#+00:00#ERROR#/Handler#########mX0K4ZN3FpyNEnpTo3XI7DKDRs4sQbrb######k9o2ohnm#PLAIN##GET request to /watt/resources/sap/watt/common/service/ui/Part.json completed with status 404 - error during fs.realpath: ENOENT: no such file or directory, lstat '/hana/shared/<SID>/xs/app_working/<HOSTNAME>/executionroot/987daf83-37bb-4f09-8086-ee2b4101f70f/app/resources/watt/resources/sap/watt/common/service'#