Hello experts

Following the tutorial below I was able to install an ABAP AS (SAP NetWeaver 7.5 SPS2 ASE) on Virtualbox few weeks ago:

Linux for Newbies: Installing ABAP AS on Oracle VirtualBox

Later on I was forced to reinstall the ABAP AS again due some data corruption issues. But this time I got the following error during the installation despite following the howto in the same way as before:

ERROR      2017-07-05 16:46:49.480 (root/sapinst) [CInstallerCallBackImpl.cpp:259] id=ind-rel.ind-os.ind-db.assertionFailed errno=CJS-00030
Assertion failed: Unable to generate a new password for database login 'sa'. Refer to trace file sapinst_dev.log for further information.
ERROR      2017-07-05 16:46:49.481 (root/sapinst) [iaxxbjsmod.cpp:97] id=modlib.jslib.caughtException errno=MUT-03025
Caught ESAPinstException in module call: Assertion failed: Unable to generate a new password for database login 'sa'. Refer to trace file sapinst_dev.log for further information..
ERROR      2017-07-05 16:46:50.601 (root/sapinst) [CSiStepExecute.cpp:1107] id=controller.stepExecuted errno=FCO-00011
The step syb_step_reset_db_passwords with step key |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_db_post|ind|ind|ind|ind|db_post|0|syb_rename_db_post_dia|ind|ind|ind|ind|syb|0|NW_SYB_DB_REN|ind|ind|ind|ind|syb2|0|syb_step_reset_db_passwords was executed with status ERROR ( Last error reported by the step: Assertion failed: Unable to generate a new password for database login 'sa'. Refer to trace file sapinst_dev.log for further information.).
INFO       2017-07-05 16:46:53.068 (root/sapinst) [syuxcpath.cpp:443] id=syslib.filesystem.creatingFile CSyPath::createFile()
Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/INSTANA.XML.
INFO       2017-07-05 16:46:54.315 (root/sapinst) [syuxcpath.cpp:443] id=syslib.filesystem.creatingFile CSyPath::createFile()
Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/instslana.xml.
a /tmp/sapinst_exe.9779.1499265854/dev_selfex.out
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/cleanipc.1.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/cleanipc.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/control.xml
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/controllerKdbClient.dmp
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/date.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/df.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/hostname.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/instana.xsl
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/keydb.xml
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/rpm.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/rsecssfx.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapcontrol.1.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapcontrol.2.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapcontrol.3.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapcontrol.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapinst.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapinst_dev.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapinst_loginquirer.log
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/start_dir.cd
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/stepKeydbClient.dmp
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/summary.html
a /tmp/sapinst_instdir/NW73/SBC/STANDARD/syslib_priv.log
INFO       2017-07-05 16:46:54.923 (root/sapinst) [syuxccuren.cpp:540] id=syslib.process.currentProcessEnv.cwdSuccessful CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(const CSyPath& /tmp/sapinst_instdir/NW73/SBC/STANDARD)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.
###############################################
Abort execution because of
Step returns modlib.jslib.caughtException
##############################################

Furthermore I've got the following message in the installation log "sapinst_dev.log"

Execute step syb_step_reset_db_passwords of component |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_db_post|ind|ind|ind|ind|db_post|0|syb_rename_db_post_dia|ind|ind|ind|ind|syb|0|NW_SYB_DB_REN|ind|ind|ind|ind|syb2|0
Execution of preprocess block of |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_db_post|ind|ind|ind|ind|db_post|0|syb_rename_db_post_dia|ind|ind|ind|ind|syb|0|NW_SYB_DB_REN|ind|ind|ind|ind|syb2|0|syb_step_reset_db_passwords returns TRUE
syb_step_reset_db_passwords: start
NWUsers.getMasterPassword() done: undefined (no master password set)
  password:XXXXXX
syb_start_db_server_reset_sa_password: creating ase start script
syb_start_db_server_reset_sa_password: creating start script /tmp/sapinst_instdir/NW73/SBC/STANDARD/startase_reset_sa
syb_start_db_server_reset_sa_password: starting ase
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.42 kernel  SySAM: Using licenses from: /sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_DE.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_TestDrive.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_XE.lic
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: Failed to obtain license(s) for ASE_CORE feature from license file(s) or server(s).
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: Licenses exist for ASE, but a license containing the configured (PE=EE;LT=AC) attributes could not be obtained. Verify that ASE is configured to use the correct type of license, and either reconfigure; or generate and deploy the desired license from the Sybase Product Download Center.
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: Feature has expired.
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: License feature name:  ASE_CORE
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: Expire date:   30-jun-2017
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: License search path:   /sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_DE.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_TestDrive.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_XE.lic:
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: FlexNet Licensing error:-10,32
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  SySAM: For further information, refer to the Sybase Software Asset Management website at http://www.sybase.com/sysam
syb_start_db_server_reset_sa_password: 00:0000:00000:00000:2017/07/05 16:46:49.47 kernel  There is no valid license for ASE server product. Installation date is not found or installation grace period has expired. Server will not boot.
syb_start_db_server_reset_sa_password: closing out stream
syb_start_db_server_reset_sa_password: generated sa password is empty
Assertion failed: Unable to generate a new password for database login 'sa'. Refer to trace file sapinst_dev.log for further information.
Caught ESAPinstException in module call: Assertion failed: Unable to generate a new password for database login 'sa'. Refer to trace file sapinst_dev.log for further information..
The step syb_step_reset_db_passwords with step key |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_db_post|ind|ind|ind|ind|db_post|0|syb_rename_db_post_dia|ind|ind|ind|ind|syb|0|NW_SYB_DB_REN|ind|ind|ind|ind|syb2|0|syb_step_reset_db_passwords was executed with status ERROR ( Last error reported by the step: Assertion failed: Unable to generate a new password for database login 'sa'. Refer to trace file sapinst_dev.log for further information.).
SAPInst calls the LogInquirer because of an error in execution of step |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_db_post|ind|ind|ind|ind|db_post|0|syb_rename_db_post_dia|ind|ind|ind|ind|syb|0|NW_SYB_DB_REN|ind|ind|ind|ind|syb2|0|syb_step_reset_db_passwords.

Especially the message "There is no valid license for ASE server product. Installation date is not found or installation grace period has expired. Server will not boot." seems a little odd. Does it mean that the DB server packaged with the ABAP AS is invalid due to time constraints?

I've also tried the installation in a newly created Virtualbox instance and also extracted the installation package again into a folder shared read-only within the Virtualbox VM.

Does anybody know a way to fix this issues?

Thank you all very much in advance for your replay!