SAP WEB IDE For SAP HANA Installation Troubleshooting Guide: Public 2021-09-29
SAP WEB IDE For SAP HANA Installation Troubleshooting Guide: Public 2021-09-29
2021-09-29
1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Gathering Information About the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Installation Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Basic General Landscape Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Relevant Logs for SAP Web IDE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Additional Relevant Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Builder Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2 Pre-Installation Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Logging on to the XS Advanced Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3 Installation Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Error: “User does not have required permissions”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Error: “Route with port 53075 already exists in another space”. . . . . . . . . . . . . . . . . . . . . . . . . . 16
Error: “Error staging application "di-core": Controller operation failed: Could not stage
application "di-core"”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Error: “Error staging application "javatools": 200 Application staging failed. Async execution
has failed”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Error: “Install: XSAC_HRTT (sap.com) 2.4.0, SAP_EXTENDED_APP_SERVICES (sap.com)
1.0.63”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Proxy Connection Error: “npm ERR! code ECONNRESET”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Package installation failed. “Error: No compatible version found: [email protected]”. . . . . . . . . . . . 19
1.4 Run Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Error: “ERR cp: cannot start '/hana/shared/<guid>/xs/bin/../controller_data/fss/<build pack
id>/storage': Permission denied”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
SAP Web IDE Hangs and Doesn't Open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
“Forbidden”Page is Displayed After Logon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Workspace Disappeared. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.5 Build Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
The Builder is Not Available or Outdated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Previous Builder Version Remains After Upgrade or Downgrade. . . . . . . . . . . . . . . . . . . . . . . . . 22
Build Error: “Build of HDB failed”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
HDB Build Failed with Error: “ERR no nodejs runtime found#”. . . . . . . . . . . . . . . . . . . . . . . . . . 23
HDB Build Failed with Error “Request failed”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Error Deploying the Builder Using the Space Enablement Tool. . . . . . . . . . . . . . . . . . . . . . . . . . 24
NPM Registry (Sinopia) Issue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.6 Certificate Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Browser Certificate Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Company Certificate Settings Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
This document aims to assist you with the troubleshooting of issues related to SAP Web IDE installation. The
document describes the best practices for solving the known issues, thus saving you time and effort. It is based
on the experience gathered from handling support tickets during 2017.
Some issues that you might experience can result from an incorrect installation, or from not following the
installation guide instructions, or from supplying incorrect parameters to the installation commands, to name
just a few. The following sections provide specific recommendations on how to resolve each issue.
Out of Scope
Although this document covers some issues related to XS Advanced, it doesn't serve as a troubleshooting
guide for XS Advanced. For more information about XS Advanced issues, see SAP HANA Platform
documentation.
When you contact SAP support for help with installation-related issues, providing full information about your
system landscape is essential to ensure the speed and quality of the solution.
This section explains how to gather information about various aspects of your system using XS Advanced
commands.
Related Information
Validate the environment installation using the check-webide diagnostic tool for the SAP Web IDE for SAP
HANA server environment.
With this tool, you can check if SAP Web IDE is properly installed and if XSA environment is ready to work with
it.
The tool checks some basic problems in the SAP Web IDE environment and does not contain all possible
issues.
Prerequisites
● You have performed the installation instructions described in the SAP Web IDE for SAP HANA - Installation
and Upgrade Guide.
● You are working with XSA version 1.0.122 or higher.
● The tool checks and connects to the same target organization that you located. To change the
organization, you must change the organization target.
1. Start analyzing the SAP Web IDE environment by running the following command:
xs check-webide
Or,
xs cw
xs cw > cw.txt
See Installation Validation [page 5] for the list of checks performed by the webidex tool.
Describes the checks performed by the check-webide tool and provides possible solutions to the error
messages provided by the tool.
Make sure the domain name meets the SAP Web IDE installation prerequisites.
The domain name must be compatible with the HTTP cookie requirements described in SAP Note 654982 .
Some browsers might work with a two-period domain, if the penultimate part contains at least 3 characters.
If your domain name doesn’t meet the requirements above, you may receive the following error message from
SAP Web IDE when deploying the builder:
In this case, you need to change it accordingly and perform the following steps:
1. Uninstall first SAP Web IDE, and then SAP HANA Runtime Tools.
2. Update the domain name in your machine or change from a physical host name to a DSN alias name, as
described in SAP Note 2245631 .
3. Install SAP HANA Runtime Tools, and then SAP Web IDE.
After changing the domain name, the following errors might appear in the relevant logs:
See the following SAP Notes for possible solutions to these problems:
SAP Note 2243019 - Providing SSL certificates for domains defined in SAP HANA extended application
services, advanced model
SAP Note 2866031 - SAP Web IDE fails to start with "Request to UAA failed: certificate has expired"
● SAP Web IDE Web Client (XSAC_SAP_WEB_IDE) - SAP Web IDE for SAP HANA is a comprehensive
browser-based IDE for the development of complex applications comprised of Web-based or mobile UIs,
business logic, and extensive SAP HANA data models.
If a component was not installed, you must reinstall the SAP Web IDE package. See Installing SAP Web IDE.
Make sure that SAP Web IDE was not installed in a development space. If it was, remove it and install it
again in an SAP space.
You can download the packages from the SMP .
○ di-core
○ di-runner
○ webide
○ devx-ui5
○ di-local-npm-registry
○ di-space-enablement-ui
● SAP HANA Runtime Tools (XSAC_HRTT) - SAP HANA provides a selection of tools to help in the various
phases of the design-time development and run-time administration of Multitarget Applications (MTA) on
XS advanced.
Make sure that HRTT was not installed in a development space. If it was, remove it and install it again in an
SAP space.
○ hrtt-service
○ hrtt-core
● XS Advanced Cockpit (XSAC_XSA_COCKPIT) - The XS Advanced Cockpit provides the central web user
interface for XS advanced runtime. As an application developer or an administrator, cockpit enables you to
manage your applications, services, and resources. Cockpit is an auto-content app delivered with XS
advanced runtime. The Cockpit provides an overview of the Organizations and Spaces the logged in user
has access to. Within the Spaces, the application developer can manage his/her applications and related
resources like service instances. It also provides access to the Service Marketplace and the details of the
Services enabled for the corresponding Organization.
○ xsa-cockpit
● XS Advanced System Components
○ deploy-service
○ product-installer
If the auditlog-broker or the auditlog-server component is missing, you must reinstall it. If the
product-installer-ui component is missing, it is recommended to install it.
xs t -s SAP
xs undeploy com.sap.devx.di.builder
Multiple instances
Checks if there is a possibility of multiple instances of SAP Web IDE or XSA installed.
There can only be one instance of SAP Web IDE per organization. This means that SAP Web IDE should be
installed only in SAP space.
There can be multiple instances of XSA as long as they were installed with separate ranges of ports. See SAP
Notes 2507070
Failure to do so will result in port conflicts and unexpected behavior or XSA components including SAP Web
IDE.
● SAP Web IDE Web Client (XSAC_SAP_WEB_IDE) - SAP Web IDE for SAP HANA is a comprehensive
browser-based IDE for the development of complex applications comprised of Web-based or mobile UIs,
business logic, and extensive SAP HANA data models.
If a component was not installed, you must reinstall the SAP Web IDE package. See Installing SAP Web IDE.
You can download the packages from the SMP .
○ di-core
○ di-runner
○ webide
○ devx-ui5
○ di-local-npm-registry
○ di-space-enablement-ui
○ tools
● SAP HANA Runtime Tools (XSAC_HRTT) - SAP HANA provides a selection of tools to help in the various
phases of the design-time development and run-time administration of Multitarget Applications (MTA) on
XS advanced.
○ hrtt-service
○ hrtt-core
● XS Advanced Cockpit (XSAC_XSA_COCKPIT) - The XS Advanced Cockpit provides the central web user
interface for XS advanced runtime. As an application developer or an administrator, cockpit enables you to
manage your applications, services, and resources. Cockpit is an auto-content app delivered with XS
An application that has not been restaged and restarted, will not work.
Sample Code
Checks if the memory of the following applications is 2GB or higher (as of SAP Web IDE for SAP HANA SPS 03
FR 1):
● SAP Web IDE Web Client (XSAC_SAP_WEB_IDE) - SAP Web IDE for SAP HANA is a comprehensive
browser-based IDE for the development of complex applications comprised of Web-based or mobile UIs,
business logic, and extensive SAP HANA data models.
If a component was not installed, you must reinstall the SAP Web IDE package. See Installing SAP Web IDE.
You can download the packages from the SMP .
○ di-core
○ di-runner
If was installed with an mtaext extension file or upgraded from a lower release, it might override the default
settings or leave a wrong allocation of memory.
Note
If the mtaext file is used in the installation, make sure the memory allocation in this file is set to 2GB in the
applications above.
Sample Code
● SAP Web IDE Web Client (XSAC_SAP_WEB_IDE) - SAP Web IDE for SAP HANA is a comprehensive
browser-based IDE for the development of complex applications comprised of Web-based or mobile UIs,
business logic, and extensive SAP HANA data models.
If a component was not installed, you must reinstall the SAP Web IDE package. See Installing SAP Web IDE.
You can download the packages from the SMP .
○ di-core
○ di-runner
○ webide
○ devx-ui5
○ di-local-npm-registry
○ di-space-enablement-ui
○ tools
● SAP HANA Runtime Tools (XSAC_HRTT) - SAP HANA provides a selection of tools to help in the various
phases of the design-time development and run-time administration of Multitarget Applications (MTA) on
XS advanced.
○ hrtt-service
○ hrtt-core
● XS Advanced Cockpit (XSAC_XSA_COCKPIT) - The XS Advanced Cockpit provides the central web user
interface for XS advanced runtime. As an application developer or an administrator, cockpit enables you to
manage your applications, services, and resources. Cockpit is an auto-content app delivered with XS
advanced runtime. The Cockpit provides an overview of the Organizations and Spaces the logged in user
has access to. Within the Spaces, the application developer can manage his/her applications and related
resources like service instances. It also provides access to the Service Marketplace and the details of the
Services enabled for the corresponding Organization.
○ xsa-cockpit
● XS Advanced System Components
○ deploy-service
○ product-installer
○ auditlog-broker
○ auditlog-server
○ product-installer-ui
If any of the applications was installed with a disc allocation that is not <unlimited>, then use the following
command to fix the allocation:
Sample Code
ERROR: Domain <domain The domain must have 3 parts or the Server domain name
name> is invalid. penultimate part must have at least 3
characters. See SAP Note 654982 .
ERROR: Domain <domain The domain must have 3 parts or the Server domain name
name> is invalid. It must penultimate part must have at least 3
be composed of 3 parts. characters. See SAP Note 654982 .
WARNING: Domain <domain The domain must have 3 parts or the Server domain name
name> may not work in all penultimate part must have at least 3
browsers. characters. See SAP Note 654982 .
ERROR: Could not find the Download and install the <required XSA component installation
required <required app> app> application.
application.
ERROR: Could not find the Download and re-install SAP Web IDE. SAP Web IDE component installation
required <webide app>
application.
WARNING: Application di- Remove the di-builder. SAP Web IDE builder installation
builder should not be in
the SAP space.
ERROR: The application Allocate 2GB to the <di-core or di-run SAP Web IDE component memory
<di-core or di-runner app> ner app> application, then restage and
memory is <size> which is restart.
too low - a minimum of 2GB
are required.
ERROR: The disk quota for Allocate an 'unlimited' disk quota to the Disc quota allocation
<app> application is 10 <app> application.
but it should be
'unlimited'.
ERROR: The application Remove multiple instances and verify Multiple instances
<app> is running in that the application is not installed in
multiple instances. other spaces.
ERROR: The <app> Restage and restart the application. Restage and restart of relevant applica
application is not staged. tions
ERROR: The <app> Restart the application. Restage and restart of relevant applica
application is not tions
started.
ERROR: Could not find the Download and install the <XSA compo XSA component installation
required <XSA component> nent> application.
application.
INFO: Could not find the Download and install the <XSA compo XSA component installation
recommended <XSA nent> application.
component> application.
To find out which versions SAP HANA, XS Advanced and SAP Web IDE are installed in the server landscape, run
the following XS command line. The results are saved in a text file (list1.txt in the following example), which you
can attach to the incident.
To find out which builder version is installed (if any), if there are any errors in the builder installation, and if
other SAP Web IDE instances have been installed, run the following commands:
Sample Code
Note
Make sure to change the file name for each space in which you run the command line.
To to find certain known issues created during installation, in the check-webide diagnostic tool for the SAP Web
IDE for SAP HANA server environment, run the following command:
xs cw > cw.txt
Note
To find out the physical configuration of your machine, run the following command:
XSA diagnose
Check the logs after the run to verify the status is Acceptable or OK.
To find out the cause of an installation problem, export the relevant logs and environment settings into text
files, using the following XS commands:
To get the browser information (HUR file or network trace file), follow the instructions in SAP Note 1990706 .
Note
The produced HUR file might contain private data. You can delete any private data from the file before
sending it to SAP support.
● To find out the cause of a di-builder problem, export the builder log and environment settings into text files,
using the following XS commands:
xs t -s <development space>
xs logs di-builder --all > builder1.log
xs env di-builder > builderenv1.txt
● Specify how SAP Web IDE was installed (with the HDBLCM tools, or the xs install command and the used
options), and the exact location of the SAP Web IDE files on the server.
● Run SAP Web IDE in the debug mode with the additional parameter "?sap-ide-debug=true" in the URL.
Press the "F12" key when logging on to SAP Web IDE, and check the errors in the browser console. Check if
the Network view shows downloading the SAP Web IDE files.
xs t -s SAP
xs sll di-core ROOT DEBUG
xs t -s <customized development space>
xs sll di-builder ROOT DEBUG
2. Perform the action that causes a problem, such as build, and export the logs:
xs t -s SAP
xs t -s SAP
xs sll di-core ROOT ERROR
xs t -s <customized development space>
xs sll di-builder ROOT ERROR
Symptoms:
Server error when trying to log on:
Possible cause:
Untrusted connection, a certification problem.
Solution:
Use the parameter --skip-ssl-validation in the logon command line.
Example
Symptoms:
Error when trying to install SAP Web IDE using the xs install command.
Possible cause:
The user might not have the required permissions, or the system might be running out of disk space.
Solution:
To check the available disk space, run the df -h command. Free disk space, if needed.
Symptoms:
Error creating application "webide": Controller operation failed: Could not create
application "webide": Conflict: could not create route <server>:53075: Route with
port 53075 already exists in another space.
Possible cause:
SAP Web IDE was installed on the default port 53075 that already exists in another instance.
Solution:
Use a different port. See How to Change the SAP Web IDE Port [page 35].
Symptoms:
Error "FAILED: SSL connection error (supposedly untrusted connection, check the
certificates)".
Possible cause:
After an upgrade, the previous version of di-core application remains in the landscape. If the previous version
belongs to the same SPS release, the possible cause is that the parameter -o ALLOW_SC_SAME_VERSION
wasn't used in the installation command.
Solution:
Reinstall SAP Web IDE. See Cleaning up the SAP Web IDE Environment [page 28] and Installing SAP Web IDE.
Symptoms:
Possible cause:
Solution:
See How to Set the NO_PROXY Property in Environment Variable Groups [page 43].
Symptoms:
Error in the console:
Possible cause:
The version of SAP Web IDE is not compatible with the installed version of XS Advanced.
Solution:
Check the relevant SAP Web IDE release note, for example, SAP Note 2457320 for the minimal required
versions of XS Advanced and/or HRTT.
Symptoms:
Error in the console:
Possible cause:
Proxy connection problem due to a wrong XS Advanced installation.
Solution:
See How to Check NPM Registry Error Logs [page 44] and How to Set the NO_PROXY Environment Variable
[page 43].
Symptoms:
Error in the SAP Web IDE console while trying to install @sap/xsjs 2.1.2 (for example):
Possible cause:
Slow network or slow connection.
Solution:
Increase the upstream timeout using this command: xs set-env di-local-npm-registry
UPSTREAM_TIMEOUT: 120.
Symptoms:
SAP Web IDE doesn't open, error Permission denied for the XS Advanced file system. More posible errors in
the SAP WEBIde log file:
Possible cause:
Incorrect installation of XS Advanced using the hdblcm command.
Make sure that the user of the current instance of XS Advanced is assigned to all the spaces. See How to
Create/Update/Rename/Delete a Space [page 49].
Check that you have access to the path xs/controller_data/fss/<GUID>, and the rest of the path exists.
Symptoms:
SAP Web IDE SPS02 can't find the required files to load in the /watt/ directory path. You can open the log by
pressing F12. Error in the browser console: ace is not defined.
Possible cause:
The installation of SAP Web IDE was performed without the .mtaext file.
Solution:
See Installing SAP WEb IDE for SPS 02 or earlier, and How to Reinstall or Upgrade the Builder [page 33].
Symptoms:
After logging on to SAP Web IDE, you see a white page displaying Forbidden on the left.
Possible cause:
The browser cache is holding a wrong user and password. It can happen after installation, or after logging on to
another application on the server with a different user and password.
Solution:
Log on again in another browser session, or in the same session after cleaning the browser cache, for example,
by using incognito mode in Chrome.
Possible cause:
Wrong user name and/or password, or the user doesn't exist, or is not assigned to the required roles.
Solution:
Try the following: log on again; check that the user exists in the user list; reenter the password; assign the
required roles to the user; check that the user is assigned to the right space.
Symptoms:
After an upgrade, the workspace appears empty, and no existing artifacts are visible.
Possible cause:
Unknown.
Solution:
If the upgrade was performed without the deletion of services, or specifically the devx_fs service, the
workspace should remain, but might not be visible. If you see any running applications from this workspace,
this means the workspace is intact. You can find and restore it. See How to Find My Workspace on The Physical
Disk [page 41].
Symptoms:
After the organization is renamed, the workspace appears empty.
Possible cause:
The workspace is not in sync with the new organization name.
Solution:
Restore the previous organization name.
Symptoms:
Builds are failing with the error:
Possible cause:
The builder is installed in the SAP space, or in a space that is not selected for your project, or not installed at all,
or installed with an older or different version of SAP Web IDE.
Solution:
Uninstall the builder from the SAP space and reinstall it in every space in your organization. See Undeploy the
SAP Web IDE Builder [page 30], How to Install, Reinstall or Update the Builder [page 33] and How to Find out
Which Spaces Exist in My Organization [page 37].
Symptoms:
After an upgrade, builds are failing with the error:
A higher version of your MTA is already deployed. Include the command line option.
Possible cause:
After upgrading SAP Web IDE, the previous builder version remains in the space.
Solution:
Make sure that the builder in enabled in the relevant space, or reinstall the builder. If the problem persists,
uninstall and reinstall the builder. See How to Find out Which Spaces Exist in My Organization [page 37],
Undeploy the SAP Web IDE Builder [page 30] and How to Install, Reinstall or Update the Builder [page 33].
Symptoms:
An HDB module build fails with the error:
Possible cause:
SAP Web IDE was not upgraded successfully.
Solution:
Check Builder Information [page 14] for an error indicating a missing package, such as openssl, for example:
Linux command
sudo zypper
Commands
sudo zypper up
xs restage di-builder
Symptoms:
An HDB module build fails with the error:
See the error ERR no nodejs runtime found# in the Builder Information [page 14]
Possible cause:
The latest upgrade of SAP Web IDE was not successful.
Solution:
Navigate to location where the builder is installed, and then restage and restart the builder.
See How to Check if the Builder is Installed [page 40], Restage SAP Web IDE or the Builder [page 34] and
Restart SAP Web IDE or the Builder [page 35].
Symptoms:
After upgrading SAP Web IDE, an HDB module build fails with the error:
Possible cause:
During the latest upgrade, duplicate workspace records have been created. These records don't match the
existing workspaces, so the error message appears. It is also visible in the Chrome console.
In each existing workspace, update the space for each project. From a project's context menu, choose
Project Settings Space , select the relevant space, and save. After this, the builds should succeed.
Symptoms:
The error message appears in the Space Enablement (di_space_enablement_ui) application after clicking
Enable or Redeploy:
Error detecting deployed MTA: Could not create client in organization "HANAExpress"
and space "development".
Possible cause:
Solution:
In the CLI of XS Advanced, navigate to the SAP space, and perform the commands to restage and restart the
deploy-service application. See Restage SAP Web IDE or the Builder [page 34] and Restart SAP Web IDE or
the Builder [page 35].
If the builder deployment still fails, create a clean environment by redeploying the builder. See Undeploy the
SAP Web IDE Builder [page 30], Uninstall SAP Web IDE [page 29], Installing SAP Web IDE, and How to Install
the Builder [page 33].
Symptoms:
The error message appears in the Space Enablement when clicking the deploy builder button: No
configuration entries were found matching the filter specified in resource "di-
core-url".
Possible cause:
The deployment of SAP Web IDE builder on top of XS Advanced could have mixed up the configuration entries.
Solution:
In the CLI of XS Advanced, navigate to the SAP space. Undeploy the SAP Web IDE Builder [page 30], Uninstall
SAP Web IDE [page 29] completely and then reinstall it and the builder. See Installing SAP Web IDE and How
to Install the Builder [page 33].
Symptoms:
The error message appears during a build after the entry "@sap/xxx": "*", added to the dependencies in the
package.json file, and in the build console:
no such package available : @sap/<package> and npm ERR! 404 '@sap/<package>' is not
in the npm.
Possible cause:
The sinopia (di-local-npm-registry) application doesn't have the permissions to fetch the @sap/<package>
package.
Solution:
Check the errors, and set the UPSTREAM_LINK and SAPUPSTREAM_LINK environment variable. See How to
Check NPM Registry Errors [page 44] and How to Set an Environment Variable to Access Packages That Don't
Exist in the NPM Registry [page 44]
Symptoms:
After opening SAP Web IDE, getting error messages related to security certificates. The actual error messages
differ between browsers:
Chorme:
This server could not prove that it is <servername>; its security certificate is
not trusted by your computer's operating system. This may be caused by a
misconfiguration or an attacker intercepting your connection.
IE:
There’s a problem with this website’s security certificate. This might mean that
someone’s trying to fool you or steal any info you send to the server. You should
close this site immediately.
Firefox:
Your connection is not secure The owner of <server> has configured their website
improperly. To protect your information from being stolen, Firefox has not
connected to this website. Learn more… Report errors like this to help Mozilla
identify and block malicious sites
Possible cause:
The client browser doesn't trust the customer certificate.
Solution:
Accept the conditions for opening the page or use a certificate signed by an approved certificate authority.
Symptoms:
Getting certificate issues.
Possible cause:
The certificate is not properly set.
Solution:
How to Create a Domain Certificate [page 48].
This section describes problems related to the Git source control system.
Symptoms:
The following error message appears when trying to clone a Git repository in SAP Web IDE:
Possible cause 1:
SAP Web IDE is located behind a proxy server and is trying to access a public Git repository.
Possible cause 2:
SAP Web IDE is located behind a proxy server and is trying to access an on premise Git repository.
Solution:
If either the http.proxyHost or the https.proxyHost value is set, configure the JBP_CONFIG_JAVA_OPTS
environment variable with http.nonProxyHosts value that contains both the short and the fully qualified
host name of the on premise Git repository.
Symptoms:
Error in build:
(DIBuild) npm ERR! notarget No matching version found for <NPM package>
npm ERR! notarget In most cases you or one of your dependencies are requesting.
Possible cause:
During an upgrade, the cache was deleted, so the npm package can't be found.
Solution:
Check if you can access the package on another server. See How to Check an NPM Service [page 34]. If yes,
then restage the npm file system service. See How to Restage an NPM Service [page 33].
This section includes the following troubleshooting tips for working with SAP Web IDE for SAP HANA:
The best way to clean up the SAP Web IDE environment is to uninstall the whole package. See Uninstall SAP
Web IDE [page 29].
In some cases, uninstalling SAP Web IDE will not completely remove all the deployed services and installation
artifacts, which can potentially cause installation or runtime issues later on. To remove these services and
artifacts, you need to undeploy SAP Web IDE [page 30].
To remove an existing installation of SAP Web IDE from your landscape, ensure that your previous installation is
not broken or hasn't left any artifacts from a partial installation. Perform the following steps to remove SAP
Web IDE completely:
1. Switch to the SAP space. See How to Check or Change a Space in an Organization [page 36]
2. If the XSAC_SAP_WEB_IDE package is installed, uninstall it using the xs uninstall command. See How
to Find out Which Packages Are Installed [page 38] and Uninstall SAP Web IDE [page 29].
3. Check if the com.sap.devx.webide service still exists, and uninstall it. See How to Find out Which Services
Are Installed [page 38] and Undeploy SAP Web IDE [page 30].
4. If you still see SAP Web IDE and/or its components from the previous installation in the application list (see
How to Get the Application List [page 37]), delete them using the xs delete command. See Delete the
SAP Web IDE Application and Related Components [page 31].
Related Information
To uninstall SAP Web IDE, you need to run the following XS command in the SAP space.
xs uninstall XSAC_SAP_WEB_IDE
To uninstall SAP Web IDE 1.0 SPS12, run the following commands:
xs uninstall XSAC_DI_CORE
xs uninstall XSAC_SAP_WEB_IDE
To remove all the artifacts and start from scratch, run the commands with the --delete-services
parameter. See Delete All Artifacts and Database [page 32].
Caution
Be aware that this command will delete all your database and development artifacts irreversibly, so make
sure to back them up beforehand.
If you can't find the XSAC_SAP_WEB_IDE package, check if the com.sap.devx.webide service still exists, and
remove it using the xs undeploy command. See How to Find out Which Services Are Installed [page 38] and
Undeploy SAP Web IDE [page 30].
xs undeploy com.sap.devx.webide
To undeploy SAP Web IDE 1.0 SPS12, run the following commands:
xs undeploy com.sap.devx.webide
xs undeploy com.sap.devx.di
Note
To remove all the user workspaces and application artifacts, and start from scratch, run the commands
with the --delete--services parameter. See Delete All Artifacts and Database [page 32].
To remove the SAP Web IDE builder, check if the builder is installed [page 40] in each space used for
development, and undeploy the builder [page 30]. See How to Check or Change a Space in an Organization
[page 36] and How to Check if the Builder is Installed [page 40].
xs t -s <development space>
xs undeploy com.sap.devx.di.builder
If you don't find the di-builder application and the com.sap.di.builder service, try to find the IDs of failed
processes by using the following command:
xs mta-ops
You can generate the output logs of a process by running the following command:
Example
xs dmol -i 10407
If you know the ID of the failed process, you can abort it by running the following command:
Example
If after running the xs undeploy command you can still see SAP Web IDE and/or any of its components from
the previous installation in the application list, manually delete each of them using the following XS commands:
xs delete webide
xs delete di-runner
xs delete di-builder
xs delete di-core
xs delete devx-ui5
xs delete di-cert-admin-ui
xs delete di-space-enablement-ui
xs delete di-local-npm-registry
Caution
To remove the user workspaces and application artifacts, and start from scratch, run the commands with
the --delete--services parameter.
This parameter will remove all the applications, projects, and data from all workspaces.
If you suspect that any of the SAP Web IDE services remain, you can find them by running the following XS
command:
xs services
Caution
Be aware that these commands will delete all your database and development artifacts irreversibly, so
make sure to back them up beforehand.
xs delete-service devx-auditlog
xs delete-service devx-uaa
xs delete-service devx-fs
xs delete-service devx-npm-cache-fs
xs delete-service devx-ui5
xs delete-service di-cert-admin-ui
xs delete-service di-core-hdi
xs delete-service di-core-schema
Caution
Be aware that this command will delete all your database and development artifacts irreversibly, so make
sure to back them up beforehand.
If you have removed SAP Web IDE as described above, and want to start from scratch in a clean landscape, you
need to back up your database and development artifacts, and use the commands xs uninstall, xs
undeploy, and xs delete with the delete-services parameter.
Note
Be aware that this command will delete all your database and development artifacts irreversibly, so make
sure to back them up beforehand.
If you suspect that any of the SAP Web IDE services remain, you can find them by running the following XS
command:
xs services
You can manually unbind the remaining services by running the following XS command:
To enable application development, you need to create and manage spaces in XS Advanced, and make sure the
right version of the builder is installed in each space. See Managing Spaces for Development.
For detailed information about various issues you might experience with build, see Build Issues [page 21].
If the npm cache was deleted, restaging the file system service will download the missing packages again.
xs restage di-local-npm-registry
xs restart di-local-npm-registry
Example
xs login -u XSA_ADMIN
xs target -s SAP
xs set-env di-local-npm-registry UPSTREAM_LINK http://registry.npmjs.org/
xs restage di-local-npm-registry
xs restart di-local-npm-registry
xs env di-local-npm-registry | grep UPSTREAM_LINK
If you experience random issues, you can solve them by restaging and then restarting SAP Web IDE and/or the
builder.
Related Information
Example
xs restage webide
Example
xs restart webide
xs restart di-builder
The default SAP Web IDE port is 53075. If this port is not available or there is a conflict with another instance of
SAP Web IDE installed on the same machine, you can change the port by performing the following steps:
1. Open the .mtaext file for editing using the following Linux command:
vi sap-xsac-devx.mtaext
2. Change the default SAP Web IDE port from 53075 to another one, for example, 53076. To make a change,
press the Insert key, and navigate with the arrows to the port
.mtaext file
- name: webide
parameters
port: 53076
For more information about configuring multiple XS Advanced systems on the same host, see 2507070 .
If you want the deploy service to choose an available port SAP Web IDE, set the "${default-port}"
parameter in the .mtaext file as the SAP Web IDE port.
2.9 How to Check SAP Web IDE Connection with the Server
Append /che to the SAP Web IDE link and open it in the browser.
If no JSON content is returned, run the URL of the di-core application in the browser. To obtain this link, run the
command xs app di-core.
If no JSON content is returned, there might be a server connection problem, or the port is incorrect
This section explains how you can gather information about your server landscape.
Related Information
To find out in which space you're working, run one of the following XS commands:
xs o
xs a
xs apps
Example
xs t -s SAP
xs t -s PROD
To find out which spaces exist in your organization, run the following command:
xs spaces
For more information about creating, updating or renaming spaces, see How to Create/Update/Rename/
Delete a Space [page 49].
To get the list of applications, which are installed in a space, along with their URLs, switch to the SAP space, and
run one of the following XS commands:
xs a
xs apps
Example
To find out which packages are installed in a space, run the following XS command:
xs lc
Example
To find out which services are deployed in a space, run the following XS command:
xs mtas
To find out the SAP HANA Database version, run one of the following XS commands:
xs -v
HDB version
The builder should be installed in every space used for application development, apart from the SAP space,
where it might cause unexpected behavior. If you find that the builder is installed in the SAP space, remove it,
as described in Undeploy the SAP Web IDE Builder [page 30].
Switch to each space in which you want to check the builder installation and see if di_builder appears in the list
of installed applications. See How to Find out Which Spaces Exist in My Organization [page 37]
For example, if the builder should be installed in the PROD space, run the following XS commands:
xs t -s PROD
xs a
To find out the version of the builder installed in a space, run the following XS command:
xs mtas
Example
Note
The installed builder version must match the SAP Web IDE version.
Example
cd /usr/sap/hana/shared/XSA/xs/bin/../controller_data/fss/3d1eb6a1-
d6b8-4a7d-8b2d-2df72ed861c1
You can locate your project files under the following path:
For example, the following picture shows the location of workspace workspacenuwfpugwbgfwewys and
the project MyMTAProject in the subfolder:
If there are multiple workspaces in your landscape, you can see which workspace is currently opened in SAP
Web IDE, displayed in the browser console (open by pressing the "F12" key).
Example
https://<server>:53075/watt/index.html?workspaceId=workspacenuwfpugwbgfwewys
If your developers are going to use an npm registry as the upstream repository for the local cache held by SAP
Web IDE, it needs to be configured in the .mtaext file used for custom installation.
The NO_PROXY environment variable defines the host names that shouldn’t go through a proxy to access the
upstream repository. The XS Advanced host name should be included in this variable.
To check this, retrieve the PID of a running process by running the following command:
xs ps
Linux command
If NO_PROXY is not included in the output, and it hasn't been defined in the .mtaext file, you can set it in an
environment variable group by running the following commands:
xs ssevg '{"no_proxy":"{xsa-placeholder-domain-default},
$no_proxy","NO_PROXY":"{xsa-placeholder-domain-default},$NO_PROXY"}'
xs srevg '{"no_proxy":"{xsa-placeholder-domain-default},
$no_proxy","NO_PROXY":"{xsa-placeholder-domain-default},$NO_PROXY"}'
For checking the server proxy settings, run this Linux command:
vi /etc/sysconfig/proxy
To check the error logs of the sinopia (di-local-npm-registry) application, run the following XS command:
Trying to access packages that don't exist in the npm registry will cause a build failure, if the UPSTREAM_LINK
and SAPUPSTREAM_LINK environment variables are not set. To set the variables, perform the following steps:
3. In your Linux server, run the following commands for HTTP and HTTPS proxies:
Linux commands
echo "$http_proxy"
echo "$https_proxy"
4. To set the environment variables, run the following commands with the parameters returned by the echo
commands:
5. Then run the following command to restage and restart the di-core:
xs restage di-local-npm-registry
xs restart di-local-npm-registry
This section provides instructions for restarting XS Advanced and SAP HANA.
Related Information
If the server is not responding to commands, or unexpected problems occur, try restarting XS Advanced.
XSA restart
Note
To restart SAP HANA, run the following Linux commands as an XS ADVANCED user, which will also restart XS
Advanced. Note that the restart might take 20 minutes or more.
sudo su - <GUID>adm
HDB restart
sudo su - <GUID>adm
HDB stop
HDB start
or
After restarting SAP HANA, all the running applications will be restarted automatically, which might take a few
minutes.
You can experience a problem setting breakpoints in Node.js source files. The issue is caused by the SAP HANA
self-signed certificate.
To solve the issue, import the certificate into your browser so that it could trust the SAP Web IDE URLs.
In Firefox
9. Open each plugin's URL (they differ by port numbers) and repeat the above steps.
10. Refresh SAP Web IDE and verify that no error appears.
SAP Note 2243019 - Providing SSL certificates for domains defined in SAP HANA extended application
services, advanced model
To perform various tasks related to user and role management, you can use the XS Advanced CLI and/or the
administration tools in SAP HANA XS Advanced Cockpit.
Related Information
XS CLI: Spaces
Maintain and manage user spaces in an organization, for example: create, list, rename, delete.
2.18.2 How to Create and Manage SAP Web IDE Users and
Roles
Maintain and manage SAP HANA users, for example: create, list, purge, and delete users; assign and revoke
roles in organizations and spaces.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.