'sapstartsrv' service not started - on AWS HANA environment

[Former Member]

Hi All,

I've created a HANA instance on Amazon Web Services and can successfilly connect to the instance from SAP HANA Studio on my laptop.  However ,I'm getting the following warning message:

'sapstartsrv' service not started. (see attached screenshot)

Does anyone know what the impact of this is and how I can go about starting the service?

Regards,

Herman

[Former Member]

I Opened 50013,30015,50014 and 30017 ports and it solved my problem.

[christian_buckowitz]

Just started with a fresh HANA developer edition on AWS. Ran into this same issue that sapstartsrv was marked yellow for not being started. Based on this thread http://scn.sap.com/thread/2075466 i spent some time trying until I found this solution working for me:

Enter the public IP of the HANA AWS instance in the hosts file (C:\Windows\System32\drivers\etc\hosts), with just the default hostname of the HANA system (imdbhdb) e.g.

54.229.123.234    imdbhdb

In HANA studio just add a new system (or change existing) with hostname setting imdbhdb:30015

That fixed this and the service shows up green now.

[Former Member]

Hi Herman,

You may see an yellow triangle next to “HANA system”, indicating some sap services is not started. This is not an issue and is a redherring.

If you do not want to see this message, add the following entry in the windows 'host' file under C:\Windows\System32\drivers\etc.

<elastic ip address> imdbhdb

e.g

23.XX.183.XXX imdbhdb

Thanks,

Baski

[Former Member]

Hi Baski,

# Copyright (c) 1993-2009 Microsoft Corp.

#

# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.

#

# This file contains the mappings of IP addresses to host names. Each

# entry should be kept on an individual line. The IP address should

# be placed in the first column followed by the corresponding host name.

# The IP address and the host name should be separated by at least one

# space.

#

# Additionally, comments (such as these) may be inserted on individual

# lines or following the machine name denoted by a '#' symbol.

#

# For example:

#

#      102.54.94.97     rhino.acme.com          # source server

#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.

#          127.0.0.1       localhost

#          ::1             localhost

   107.21.225.26    imdbhdb

i did it like this.  Where is my mistake cus still i have this problem 😃

Thanks,
Emrah

[Former Member]

Emrah,

I have the same problem and have even created a new instance and installed the client and studio on a new machine. No change in status. Please do respond to me if you figure it out.

BTW, did you change the Active Provider to Direct in the network connections? See if that works for you. It did not for me.

Best,
Amit.

[Former Member]

Amit,

I am facing the same problem and changing Active Provider to Direct did not work for me.

[Former Member]

Found a post that already deals with this in detail (albeit not in the context of AWS instances):

http://scn.sap.com/thread/2075466.

Regards,

Herman