Skip to Content
Author's profile photo Lucia Subatin

Troubleshooting connection problems: HANA express from HANA Studio

After repeatedly seeing questions around failed connections to HANA Express, I’m compiling the basic troubleshooting steps I take when, for example, HANA Studio does not connect to my HXE instance. The most typical error is:

The system cannot be reached. logon data cannot be used.

The order in the steps is not random. If any of the tests fail, moving forward with the next step does not make any sense without fixing whatever is causing the test to fail.

Is the database running?

Sounds obvious but worth checking.

From the console in your server, you can use ./HDB info and make sure you can actually connect  using hdbsql -i <<instance number>> -d <<database name> -u <<some user>> and run something like:


Or check the tenant database is actually running if that is what you want to connect to (if it is not, the error will say “general error: database ‘hxe’ is unavailable SQLSTATE: HY000”):

select * from "SYS"."M_DATABASES";

You can start the tenant database with:

alter system start database <<tenant name>>;

If you encounter any errors when starting the database or in the logs ( /usr/sap/<SID>/HDBXX/<server name>/trace ), go do a search for them and best of luck fixing your database.

If you can effectively connect with hdbsql, let’s move to seeing if you can connect from outside.

Can only connect to SYSTEMDB but not the tenant

If your SQL client (HANA Studio) can connect to the SYSTEM database but not to the tenant database AND you could connect to the tenant in the previous step, you may need to take some additional steps like the ones described here:

Very old versions of HANA Studio could also be the problem.

Ping the external IP

In a cloud environment, you will find the external or public IP in the dashboard where you can manage your virtual machine.

On Google Cloud Platform:

On Amazon Web Services:

On MS Azure:


On SAP Cloud Appliance Library:

In a Virtual Machine, you will get it with command sudo ifconfig from inside the VM. If you do not get an IPv4 address (something in the shape of ), it is not getting one assigned. This may be solved by changing the network configuration in the Virtual Machine but I’m not covering this here as it is already covered here..

On a command prompt in the same computer where you have the connection issues, ping the external IP:

If instead of a reply you get “Connection timeout.Destination host not reachable“, your computer cannot reach the server. The IP may be wrong, you may be behind some corporate firewall or proxy or for some reason (not the case of the default configurations for HXE), there’s no reply sent back.

A firewall kind of problem could be ruled out by using an online ping tool, such as or connecting from another place like your phone or home.

Most of the times, I’ve seen either the IP has changed because the server was restarted and the IP was set to ephemeral or the temptation to use the internal IP was too big.

Ping hxehost

Or whatever your hostname is. If you can reach the IP but pinging the host name gives back “Ping request could not find host ..”, time to go back to editing the hosts file (explained on step 4 in this tutorial).

Some coffee corner here

I have some weird anecdotes from people failing to edit the hosts file for the first time: some choose to create a new file like “hosts.txt” because they do not have the necessary administration rights while others just ignore the error message and don’t save the changes. However, the prize goes to a user that decided to copy the entire drivers folder into the Desktop so that the permissions would not be a problem.

Are the ports reachable?

The default pre-configured images on cloud providers come with the proper ports open. Make sure you can reach the ones needed by SQL clients (for example, 3xx13, 3xx15, 3xx17 – where “xx” stands for your instance number and 90 is the default for HXE).

I use Telnet for this. In my Windows computer, I had to enable it in the programs and features.

The connection succeeds pretty much if you do not get an error (I get a black screen for a short while). A closed port would say something like “Could not open connection to the host, on port 30013: Connect failed”.

Mac users can resort to nc -v hostname 3xx13 instead of telnet and should get a success message.

Note: The ports that are actually being used can be found using the SQL in this blog by Abdel DADOUCHE

If you cannot reach the ports but got so far, you probably need to ask your network admins to enable the ports needed to reach your HANA instance. Make sure you match the instance number and version/flavor of your server.

Trace the connection

You are not behind a firewall or proxy, all of the previous steps worked and still cannot connect from the SQL client? Enable the JDBC trace

In HANA Studio, Right click on the connection –> Properties–>JDBC trace:

Options for other clients can be found in the help.

Further help, as usual, can be found in the Q&A. Be sure to search for your question before you post it and add all the information you consider relevant (what error you are getting, what have you already tried and failed, some screenshots).


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Daniel Poblet
      Daniel Poblet

      Excelent Blog Lucia! Thanks for sharing!

      Author's profile photo Patrick Steffens
      Patrick Steffens

      I just had problems pinging the IP of my HXE server (loval VM) which was also solved by updating the hosts file (as hinted in the section "Ping hxehost"). You might consider adding the hint to the "Ping the external IP" section, too.

      Thanky anyway. Your summary helped me to find this (obvious) solution.


      Author's profile photo kyo choi
      kyo choi

      Excellent blog.  Thanks.

      Author's profile photo Francisco Gaitan
      Francisco Gaitan

      Thanks for the articule, I had the same message for a long day studing with Hana Express 2.0 SP3, and the reason was that I had a tenant database and I drop it, Then, I create it again with the same name and after that I couldn’t connect to database again,  I had to have to create the database with a different name, after that it works perfectly, I was looking for a solution but I didn’t, ¿do someone know if that is usual?

      Author's profile photo Jonas Rabello
      Jonas Rabello


      I'm trying to connect to SAP HANA EXPRESS using JDBC.

      It seems I can connect to the server but there is a error:

      Message: [10]: authentication failed

      The code (java project in Eclipse)

      import java.sql.DriverManager;
      import java.sql.SQLException;


      public class TestJDBCDriver {

      public static String connectionString = "jdbc:sap://hxehost:39015";
      public static String user = "hxeadm";
      public static String password = "password";

      public static void main(String[] argv) {
      Connection connection = null;
      try {
      connection = (Connection) DriverManager.getConnection(connectionString, user, password);
      } catch (SQLException e) {
      System.err.println("Connection Failed: Message: " + e.getMessage());
      if (connection != null) {
      try {
      System.out.println("Connection to HANA successful!");
      Statement stmt = (Statement) connection.createStatement();
      ResultSet resultSet = (ResultSet) stmt.executeQuery("select 'hello world' from dummy");;
      String hello = resultSet.getString(1);
      } catch (SQLException e) {
      System.err.println("Query failed!");

      I did the SQL test and is working well.

      The ping test is working well.

      Also, using the Perspective SAP HANA I can access the database normally. I have create tables, and views, and even another user. But the access by JDBC is not working.


      Please, could you help me?

      I am new in SAP HANA EXPRESS, and I have tried to find a solution without success.

      Author's profile photo Jonas Rabello
      Jonas Rabello

      I forgot to mention.

      I am using VmWare Linux installation and create client in /usr/sap/hdbclient/ with success.


      Author's profile photo Jonas Rabello
      Jonas Rabello

      Finally my user connect to Hana database.


      The solution is here



      I used the connection like that according to Carl



      Author's profile photo Markus Perndorfer
      Markus Perndorfer

      Finally figured out why I couldn't connect to the tenant database when booting up a HANA express instance in CAL

      The HANA hostname resolution returned the wrong IP adress

      To mitigate, I've disabled it:

      alter system alter configuration('global.ini','system') set ('public_hostname_resolution','use_default_route')='no' with reconfigure;