03-11-2018 8:05 PM
Hello,
I have tried to install the SAP Netweaver ABAP AS 7.51, SP02 on ASE on a openSuse running inside a VirtualBox according to this blog post:
https://blogs.sap.com/2017/09/04/newbies-guide-installing-abap-as-751-sp02-on-linux/
I managed to set up openSuse accordingly in terms of hostnames and all. But I did not setup proxy as I have none. Now when I execute the ./install.sh I get the following error. In that scenario I am starting the ./install.sh as root user. install.sh and all installation files are located on the host machine and I am accessing them through the shared folder (I did not yet try to move the files inside the virtual box).
I also have no SAP GUI installed yet.
Could anyone imagine what's wrong here?
Here is the error. You find two logfiles below.
ERROR 2018-03-11 20:56:31.947 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/modlib/iaxxbjsmod.cpp:83] id=modlib.jslib.caughtException errno=MUT-03025
Caught ESAPinstException in module call: Validator of step |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_os_users|ind|ind|ind|ind|osUsers|0|NW_GetUserParameter|ind|ind|ind|ind|getUserParameter|0|NW_GetUserParameterUnix|ind|ind|ind|ind|users_unix|0|askSidAdm reports an error:
To solve that problem start the installation without using SAPINST_START_GUI option..
ERROR 2018-03-11 20:56:32.063 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/sapinst/CSiStepExecute.cpp:1117] id=controller.stepExecuted errno=FCO-00011
The step askSidAdm with step key |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_os_users|ind|ind|ind|ind|osUsers|0|NW_GetUserParameter|ind|ind|ind|ind|getUserParameter|0|NW_GetUserParameterUnix|ind|ind|ind|ind|users_unix|0|askSidAdm was executed with status ERROR ( Last error reported by the step: Caught ESAPinstException in module call: Validator of step |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_os_users|ind|ind|ind|ind|osUsers|0|NW_GetUserParameter|ind|ind|ind|ind|getUserParameter|0|NW_GetUserParameterUnix|ind|ind|ind|ind|users_unix|0|askSidAdm reports an error:
To solve that problem start the installation without using SAPINST_START_GUI option..).
INFO 2018-03-11 20:56:32.316 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/syslib/filesystem/syuxcpath.cpp:443] id=syslib.filesystem.creatingFile CSyPath::createFile()
Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/INSTANA.XML.
INFO 2018-03-11 20:56:32.415 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/syslib/filesystem/syuxcpath.cpp:443] id=syslib.filesystem.creatingFile CSyPath::createFile()
Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/instslana.xml.
a /tmp/sapinst_exe.4641.1520798139/dev_selfex.out
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/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/syslib_priv.log
INFO 2018-03-11 20:56:32.762 (root/sapinst) (startInstallation) [/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/syslib/process/syuxccuren.cpp:546] 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
##############################################
Installation of NPL failed, please check logifiles in /tmp/sapinst_instdir for possible root cause.
03-13-2018 3:05 PM
Additional informations:
It did not matter if install.sh was started after SU or via SUDO.
The error also occured after I have moved the installation files into home directory inside the VirtualBox.
The VirtualBox has 8 GB of RAM assigned and there is around 80 GB free disk space which I hope is sufficient.
03-18-2018 2:33 PM
Solution:
Username in openSUSE Linux virtual machine mustn't contain language specific special characters, i.e. äöü
04-14-2018 8:29 AM
I have the same problem,
but I reported in the original installation blog article
https://blogs.sap.com/2016/11/03/linux-for-newbies-installing-opensuse-on-oracle-virtualbox/
a)
"Username in openSUSE Linux virtual machine mustn't contain language specific special characters, i.e. äöü"
Does not apply to my case, I used
suse
as username, and
suse
as LINUX user/root password, and
suse2018
as general SAP password, and didn´t create any (LINUX, SAP) usernames for use with the SAP installation, as there was no need to do so by the given installation process.
b)
Obviously, there is a problem with authentification by "askSidAdm" in the current installation of SAP Netweaver.
04-19-2018 11:03 AM
Hi Rolf,
Your error message, as reported by you in the blog comments, is different:
"ERROR 2018-04-12 14:41:49.626 (root/sapinst) id=modlib.jslib.caughtException errno=MUT-03025
Caught ESAPinstException in module call: "
As I said in the blog, you need to check your license for expiry date.
More details : The install script checks for a valid license before completing the installation.
If you have downloaded the .rar files from us, then those files will contain an old license.
If you have now post-installed a valid license, and still get an error, then let me know.
But please start by doing what we suggest.
The error message "...id=modlib.jslib.caughtException..." covers many errors - they are not all the same.
Best wishes
Julie.
04-19-2018 11:14 AM
Hi Rolf,
If you do have a valid license, another user also had a similar error : "...ESAP...". Here is his solution:
https://answers.sap.com/questions/484103/installation-failed-abap-as-751-sp02-modlibjslibca.html
Please try that as well.
(I realize this is inconvenient, but we need to eliminate the basic issues one at a time, before looking at the more complex issues.)
Best wishes
Julie.