Install S/4 HANA got error:instance reached state unknown after having state starting giving up

[rokinglj]

When I install S/4 HANA got error:instance reached state unknown after having state starting giving up.

I cheked log,the infos:

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

disp+work, Dispatcher, YELLOW, Server not attached to message server, 2022 03 11 09:43:04, 0:00:07, 15853

igswd_mt, IGS Watchdog, GREEN, Running, 2022 03 11 09:43:04, 0:00:07, 15854

gwrd, Gateway, YELLOW, Scheduled, , , -1

icman, ICM, YELLOW, Scheduled, , , -1

instdir-sapcontrol-s4h-ascs02.txt

instdir-sapcontrol-s4h-d01.txt

instdir-sapcpe-sapinst.txt

instdir-sapinst.txt

instdir-sapinst-dev.txt

instdir-sapinst-loginquirer.txt

instdir-syslib-priv.txt

Please help. Thanks.

[isaias_freitas]

Hello,

From:

GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
disp+work, Dispatcher, YELLOW, Server not attached to message server, 2022 03 11 09:43:04, 0:00:07, 15853

But the file "instdir-sapcontrol-s4h-ascs02.txt" shows that the Message Server was started a couple of minutes before that.

Can you confirm that the ASCS02 processes are still running and with "green" state?

You can use the command "sapcontrol -nr 02 -function GetProcessList" (executed as SIDadm at the ASCS02 server).

If the ASCS02 processes are running, use "sapcontrol -nr 01 -function GetProcessList" to verify the current state of the D01 instance.

If it is still not attached to the Message Server, check the "dev_disp" trace file under the "D01/work" folder.

Perhaps an issue related to DNS or firewall, not allowing the Dispatcher to connect to the Message Server port 3902?

Regards,

Isaías

[rokinglj]

Thanks for your help! I solved the issue.When I change hosts related configration,It worked well.

[mamartins]

There is an error on the load of the SAPCRYPTOLIB (messages from the instdir-sapinst.txt):

WARNING 2022-03-11 09:42:49.523 (root/sapinst) id=appmod.likeySignError
Creating a license signature failed. DETAILS: 
===...could not load SSF library /usr/sap//D00/exe/libsapcrypto.so .

WARNING 2022-03-11 09:42:49.523 (root/sapinst) id=appmod.likeySignError
Creating a license signature failed. DETAILS: 543 wlikey_sign_for_installer: Couldn't load SAPSECULIB ("/usr/sap//D00/exe/libsapcrypto.so") using function SsfSupInitEx (), rc = 10 (no library).

WARNING 2022-03-11 09:42:49.523 (root/sapinst) id=appmod.likeySignError
Creating a license signature failed. DETAILS: 542 wlikey_sign_for_installer: At least one more attempt to load the SAPSECULIB will follow.

WARNING 2022-03-11 09:42:49.524 (root/sapinst) id=appmod.likeySignError
Creating a license signature failed. DETAILS: 
===...could not load SSF library .//libsapcrypto.so .

There is a permissions problem or with the kernel you used.