COULD NOT OPEN CONNECTION TO THE HOST MAC
COULD NOT OPEN CONNECTION TO THE HOST WINDOWS

Mac users can resort to nc -v hostname 3xx13 instead of telnet and should get a success message. A closed port would say something like 'Could not open connection to the host, on port 30013: Connect failed.' The connection succeeds pretty much if you do not get an error (I get a black screen for a short while).

COULD NOT OPEN CONNECTION TO THE HOST WINDOWS

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

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). The default pre-configured images on cloud providers come with the proper ports open. However, the prize goes to a user that decided to copy the entire driver's folder into the Desktop so that the permissions would not be a problem. I have some weird anecdotes from people failing to edit the host's file for the first time: some choose to create a new file like 'hosts.txt' because they do not have the necessary administrative rights while others just ignore the error message and don't save the changes. If you can reach the IP, but pinging the hostname gives you the message 'Ping request could not find host.,' it's time to go back to editing the host's file ( explained on step 4 in this tutorial). Most of the time, 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. 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.ДЄ 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 network. If instead of a reply you get ' Connection timeout.В Destination host not reachable,' your computer cannot reach the server. On a command prompt in the same computer where you have the connection issues, ping the external IP: 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. If you do not get an IPv4 address (something in the shape of 12.34.56.789 ), it is not getting one assigned. In a Virtual Machine, use the command sudo ifconfigВ to get his information from inside the VM. In a cloud environment, you will find the external or public IP in the dashboard where you can manage your virtual machine. Very old versions of HANA Studio could also be the problem. 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. Can Only Connect to SYSTEMDB But Not the Tenant

If you can effectively connect with hdbsql, let's move to seeing if you can connect from outside. If you encounter any errors when starting the database or in the logs ( /usr/sap//HDBXX//trace ), go do a search for them and best of luck fixing your database. You can start the tenant database with: alter system start database > Or check that 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' HDB info and make sure you can actually connect using hdbsql -i > -d -u > and run something like: SELECT * FROM DUMMY 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.ДЇrom the console in your server, you can use. The most typical error is: The system cannot be reached. 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.