search

sbcgua / sap-nw-abap-vagrant

Vagrant config for SAP NW developer edition
46 stars 15 forks source link

Installation fails - 750sp04 #15

Closed g-back closed 4 years ago

g-back commented 4 years ago

Hi, I'm getting below error during the installation (not sure if this is because of your script or something else). OS: Windows Fresh installs of vagrant and VirtualBox distrib files downloaded yesterday from https://developers.sap.com/trials-downloads.html?search=7.52%20SP04

It even offers a solution SOLUTION: Ensure that you use the latest available version of Software Provisioning Manager downloaded from the SAP Service Marketplace and do not change its content but I'm not sure what to do with that...

context of error messsage:

    sapnw: Modified files: ['JAVA/750/J2EEINSTALL.SDA', 'PVIND/XML7XX/dialog.xml', 'PVIND/XML7XX/javaSteps/nw.jar']
    sapnw: Signer messages:
    sapnw: SAPCryptolib ERROR, see stack of latest warnings and errors:
    sapnw: Digest of file >JAVA/750/J2EEINSTALL.SDA< is not correct
    sapnw: VerifyEntry: ManifestCloseFile failed
    sapnw: SAPCryptolib ERROR, see stack of latest warnings and errors:
    sapnw: Digest of file >JAVA/750/J2EEINSTALL.SDA< is not correct
    sapnw: Digest of file >PVIND/XML7XX/dialog.xml< is not correct
    sapnw: VerifyBuffered: ManifestCloseFile failed
    sapnw: SAPCryptolib ERROR, see stack of latest warnings and errors:
    sapnw: Digest of file >JAVA/750/J2EEINSTALL.SDA< is not correct
    sapnw: Digest of file >PVIND/XML7XX/dialog.xml< is not correct
    sapnw: Digest of file >PVIND/XML7XX/javaSteps/nw.jar< is not correct
    sapnw: VerifyBuffered: ManifestCloseFile failed
    sapnw: ERROR      2020-08-06 14:47:55.873 (root/sapinst) (startInstallation) [iaxxbjsmod.cpp:83] id=modlib.jslib.caughtException errno=MUT-03025
    sapnw: Caught ESAPinstException in module call: The integrity check for [JAVA/750/J2EEINSTALL.SDA, PVIND/XML7XX/dialog.xml, PVIND/XML7XX/javaSteps/nw.jar] of Software Provisioning Manager failed. DETAILS: The content has been tampered with and must not be used. SOLUTION: Ensure that you use the latest available version of Software Provisioning Manager downloaded from the SAP Service Marketplace and do not change its content..
    sapnw: ERROR      2020-08-06 14:47:56.106 (root/sapinst) (startInstallation) [CSiStepExecute.cpp:1104] id=controller.stepExecuted errno=FCO-00011 CSiStepExecute::execute()
    sapnw: The step setDefaultDataPath with step key |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|PrerequisiteCheckerDialogs|ind|ind|ind|ind|prc|0|setDefaultDataPath was executed with status ERROR (Last error reported by the step: Caught ESAPinstException in module call: The integrity check for [JAVA/750/J2EEINSTALL.SDA, PVIND/XML7XX/dialog.xml, PVIND/XML7XX/javaSteps/nw.jar] of Software Provisioning Manager failed. DETAILS: The content has been tampered with and must not be used. SOLUTION: Ensure that you use the latest available version of Software Provisioning Manager downloaded from the SAP Service Marketplace and do not change its content).
    sapnw: INFO       2020-08-06 14:47:56.329 (root/sapinst) (startInstallation) [syuxcpath.cpp:441] id=syslib.filesystem.creatingFile CSyPath::createFile()
    sapnw: Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/INSTANA.XML.
    sapnw: INFO       2020-08-06 14:47:56.549 (root/sapinst) (startInstallation) [syuxcpath.cpp:441] id=syslib.filesystem.creatingFile CSyPath::createFile()
    sapnw: Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/instslana.xml.
    sapnw: a /tmp/sapinst_exe.3079.1596718041/dev_selfex.out
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/control.xml
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/controllerKdbClient.dmp
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/instana.xsl
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/keydb.xml
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapinst.log
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapinst_dev.log
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/sapinst_loginquirer.log
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/start_dir.cd
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/stepKeydbClient.dmp
    sapnw: a /tmp/sapinst_instdir/NW73/SBC/STANDARD/syslib_priv.log
    sapnw: #

Any ideas?

sbcgua commented 4 years ago

Hmmm, haven't seen this error before. Just in case, could you check checksums of distro files ? Maybe there was some change from SAP side ? Here is the checksums of the files I have (downloaded ~year ago)

d81f5fd54b7cfd671e207822e70a008b  ./server/TAR/x86_64/SWPM10SP25_0-20009701.SAR
e1c646f4c5e1694bd58bb7213042a1d5  ./server/TAR/x86_64/dbdata.tgz-ae
3d1a41c0a0c05b766d0563958a469c3f  ./server/TAR/x86_64/sapmnt.tgz-aa
c281adcb1597f0ffdd992c62119683f5  ./server/TAR/x86_64/SAPHOSTAGENT42_42-20009394.SAR
856fb8b780af7a23b2a2191e231571a1  ./server/TAR/x86_64/dbdata.tgz-ac
eff3b688ae2dd906d0e7d6f2018d7512  ./server/TAR/x86_64/sapinst.txt
fb58a41502a95270b3a6e309141d2d7f  ./server/TAR/x86_64/dbdata.tgz-ad
7c5f888eacf1da4c5e576c78d60f2903  ./server/TAR/x86_64/dbdata.tgz-aa
0399f57cee371fbe3c4bc953c7eb71c9  ./server/TAR/x86_64/usrsap.tgz-aa
5ffcdb0b051fcf7e6f01f54c515b4371  ./server/TAR/x86_64/SAP_Software_Appliance.xml
37369eb9851469915f8dd5ccfde8bdd0  ./server/TAR/x86_64/dbexe.tgz-aa
a7d45aa312720ea6aab7a75d3a5b9da9  ./server/TAR/x86_64/dblog.tgz-aa
62d1d1cc7cd0496927cd57d9b19dd62d  ./server/TAR/x86_64/dbdata.tgz-ab
d6b5baae3dd248e2a2f4d0a64d857b64  ./server/TAR/x86_64/IdCard.xml
1da851c4da112f848fa7257a01d64209  ./client/SAPGUI4Windows/50144807_6.ZIP
f5335b8985780cef3b8d6a294dddbbab  ./client/JavaGUI/PlatinGUI750_5-80002496.JAR
a4b0ce5dc0be31b1cdfb2518d3441008  ./client/JavaGUI/PlatinManual_12-20012039.zip
ace00723cf25bbf6d4e081259dbb8323  ./client/JavaGUI/50144807_7.ZIP
727ff5b5ec71dcce16e669af239aca1c  ./client/JavaGUI/PlatinManual750_5-80002496.ZIP
c8ff1d2126d3a432e4363e1c04009a99  ./SAP_COMMUNITY_DEVELOPER_License
88a5e1bee8c28f8bc7ad51d1465fdd46  ./install.sh
849351b6226b6fbca0f51b66892e7019  ./readme.html
a3f000fe12d57202e4189281445ccd22  ./img/cd_n702.gif
3056a0a4d381318f1058b4a423c36817  ./img/top_nav.jpg
4bd992dae2dbbe35b4ec51458103f729  ./img/spacer.gif
f446c2a20d18082bee11e054f4874af0  ./img/Thumbs.db
f4e78f83f4f6e7194fc9ed9c26f4daf8  ./img/blank.gif
27c19ae9098d05d491007ed70dd791c1  ./img/slogan.gif
ccb3d9f6e15e802ff54d585bd4da5057  ./img/sap_logo.png
3332f0c3a2efd46608efa66bc1b0307e  ./img/sapstyle.css
d8f4a922bfb27353e3e4be376901857e  ./img/technology_4.jpg

the linux command (assuming you are in distrib folder)

find . -type f -exec md5sum \{\} \;
g-back commented 4 years ago

hmm... MD5 hashes are identical

sbcgua commented 4 years ago

strange ... let me check the installation from scratch today/tomorrow, maybe some accumulated changed impacted ...

sbcgua commented 4 years ago

Sorry for late response. Just finished a fresh installation. All went well. One specifics - the host was a linux machine, but it should not affect the sap script anyway Not sure what to suggest :(

g-back commented 4 years ago

Ya, I've tried it many more times, even manually with a different guest OS... whatever the issue is, it's not caused by this repo! Still, thanks a lot for the help!