cancel
Showing results for 
Search instead for 
Did you mean: 

HANA Express 2.0 SP3 XSA installation fails (VM)

maklucksap
Explorer
0 Kudos

Hi guys,

I am trying to install HANA Express 2.0 SP3 with XSA on my notebook. The hypervisor (Virtual Machine) I use is "VMware Workstation 15 Player".

The installation fails at the step "Check/Wait for Cockpit app to start". It says: "FAILED to communicate with XS Controller" It also says: "Please start required Cockpit apps and rerun register_cockpit.sh."

Any idea how I start the Cockpit apps and how to rerun this Cockpit registration? Does anyone experienced the same and found a solution for this?

I've followed the installation steps, that you can see in this Blog: https://developers.sap.com/group.hxe-install-vm-xsa.html

Same steps in a YouTube clip: https://www.youtube.com/watch?v=71Z4F5eKR-g

My notebook has:

  • 2,8 GHz CPU with 4 Cores
  • 32 GB RAM
  • Windows 10 Home 64 Bit
  • 320 GB free disc space

In VMware I've granted GB RAM, which should also be sufficient.

Kind Regards
Mark André

Accepted Solutions (0)

Answers (4)

Answers (4)

lsubatin
Active Contributor

Hi, Mark André,

If you want to try importing the VM again, change the settings in the network fo the VM to NAT before starting the VM as that MAY help. After sudo su - hxeadm, stop the setup script with CTRL+C and make sure you have an IPv4 address assigned. You'd need to fix that before running the setup script (go sudo su - hxeadm again and the setup script should start).

If you're feeling bold, another option after the error and after you are sure you have an IP address assigned, log in to the XS CLI with:

xs login -a https://hxehost:39030 -o HANAExpress -s development -u XSA_ADMIN --skip-ssl-validation

and use xs start + :

cockpit-admin-web-app

cockpit-adminui-svc

cockpit-collection-svc

cockpit-hdb-svc

cockpit-persistence-svc

cockpit-telemetry-svc

cockpit-xsa-svc

To start each of the cockpit apps the script needs. Once they are all started, run /usr/sap/HXE/home/bin/register_cockpit.sh -action register

Leave the default users and enter the master password.

Hope that works,

Lucia.

maklucksap
Explorer
0 Kudos

Hi Lucia,

Thanks for the hints. I did change the VM to use NAT. I also saw that there is an IPv4 address assigned.

Now I get a little bit further. This time I get a time out while waiting fo the Cockpit apps. When I logon and enter xs apps I can see that all the apps you've mentioned are in status started. I assume in the meantime they started automatically after the time out.

o I've executed the register_cockpit.sh, like you proposed. This time again it went a little bit further, but unfortunately still time outs appeared.

I've repeated the previous step and but unfortunately an error appears during registration of the database. Everytime I repeat it gets stuck at the same command.

Any ideas?

Kind Regards

Mark André

Steven_UM
Contributor
0 Kudos

Hi there,

I have been running HANA 2 SPS03 for several months now using VMware player ...

I haven't encountered your specific error but maybe some general remarks:

  • do you have a SSD or a normal HD ? I noticed a huge difference when switching towards SSD for running the system ... with a normal HD it took ages to get stuff running.
  • are you only using 16 GB memory for the VM ? I would go for 24 GB ...

Kind regards,

Steven

alex_qin
Employee
Employee
0 Kudos

Hi Mark,

I can not reproduce this issue on my laptop with hana express version 2.00.036 and vm play version 15.1.0 build-13591040.

Could you please tell me your hxe version and your vm player version?

umberto_panico
Participant
0 Kudos

Hi,
after start/login need wait about 20 minutes, system load all app and services.

Best Regards.
Umberto

maklucksap
Explorer
0 Kudos

Hi Umberto,

thank you for the quick response. From login it took almost 45 minutes until the configuration stopped at the step I mention above. I fear just waiting would not change anything as the process has already stopped.

I've just looked at the sequence of events:

1. After start I see this screen

2. Approximately 35 minutes later I see this screen:

After another X minutes I see the error that I've posted above.

Kind Regards
Mark André