Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
julieplummer20
Product and Topic Expert
Product and Topic Expert

NOTE: ASE license expiry


 

New ASE license, valid until Q1 2019 is available in this blog post: ASE License Blog. Please see the instructions below for the correct procedure.

 

Linux for Newbies


So, you want to install a developer edition of a SAP NetWeaver ABAP AS. It should sit on a Linux distribution, in a virtual box.
However, you're a Linux newbie.
FEAR NOT!
We have created a genuine, step-by-step guide, with loads of screenshots to help you on your way.
In this example, we will focus on the openSUSe distribution.

This guide is part of a series for anyone who wants a free trial version of an SAP NetWeaver ABAP AS. To find out more about this whole series, see SAP NW 750 SP2 ABAP AS Available to Download!

A. Preparation



  1. Download the latest released version of Oracle VirtualBox from https://www.virtualbox.org/wiki/Downloads for your Operating system.

  2. Download openSUSE Leap 42.1 in your local machine (64 bit, released version) from https://software.opensuse.org/421/en

  3. Make sure the relevant ABAP download files ("abap.rar") are on your local hard drive.

  4. Download the correct version of the ASE license from this blog: ASE License Blog and store it on your local hard drive.


B. Create VirtualBox instance; install openSUSE:





    1. Start VirtualBox and create a new VirtualBox instance by clicking the New button:

    2. Enter the following values:

      • Name : MyVirtualLinux (for example)

      • Type : Linux

      • Version: openSUSE (64 bit) -> Next

      • Select Memory size : 6 GB  -> Next

      • Hard disk: Create a virtual hard disk now -> Next

      • Hard disk file type: VHD (Virtual Hard Disk) -> Next

      • Storage on physical hard disk: Dynamically allocated -> Next

      • File location and size: 100 GB

      • Choose Create.



    3. Again in the VirtualBox Manager, click on Start to start the VirtualBox:

    4. In the dialog that appears, navigate to the downloaded openSuse installation file which you downloaded in Step 2, eg openSUSE-Leap-42.1-DVD-x86_64.iso.Then select this drive, choose OK:

    5. Now choose Installation (using keyboard, not mouse):

    6. Important: Choose language and keyboard layout (test keyboard).
      NOTE: We have only tested the US English-language version. If you have problems, please use the English version.

      • Accept the License Agreement by choosing Next.

      • In Installation Options, leave the 2 options unchecked, and choose Next:

      • In Suggested Partitioning, choose Edit Proposal Settings and enter the following:

        • File System for Root partitionin: choose  Ext4 from the drop-down box.



        • Uncheck Propose Separate Home Partition
          (This step is needed so that SUSE installation creates only one drive but does not create 2 drives (Home and Extension) where Home has less space to continue the ABAP installation.)

        • (Optional: Enlarged Swap for Suspend - I left it unchecked.)



      • Choose Ok, -> Next

      • Select Region and Timezone -> Next

      • In Desktop Selection, choose GNOME desktop -> Next

      • Enter:

        • Your full name

        • (Create a ) User name

        • Create a Master password, confirm it -> Next
          (
          I ticked Use this password for system administrator and Automatic Login. Leave the authentication method and encryption method as they are.
          The password should be at least 7 characters.)





    7. IMPORTANT: In Installation Settings, do not choose Install yet! You need to make settings:
      Scroll down to find Firewall and SSH.

      • Disable Firewall

      • Enable SSH service:



    8. Click on Install and Confirm again to Install the Operating System.The Linux operating system will install (yes!)




C. Prepare openSUSE system for ABAP installation


In this section, we will make some settings in the openSUSE system to prepare it for the ABAP installtion: Proxy settings; extract the ABAP .rar files; automount the folder containing these .rar files; install the uuidd daemon; change the hostname; assign root privileges to the install script.

  1. If you have successfully installed the openSUSE operating system, you will see something like this:

  2. Boot up the system by choosing the first option, "Boot from Hard Disk."Now, we just have these settings before we install the ABAP server.

  3. Change Proxy settings if you are behind a proxy:

    • Open Activities and enter "N" as the search term.
      The system returns something like this:

    • Choose Network.
      In the dialog that opens, choose Network Proxy, then choose Manual.

    • Change the http / https proxy settings according to your company requirements and set the port to 8080:



  4. Now we want to enter some commands using a tool called Xterm.
    (Background note: Technically speaking, we are interacting with the shell, a program that passes keyboard commands to the operating system. We are interacting with the shell using a terminal emulator, called Xterm. If these terms are unfamiliar, I would strongly recommend William Schotts' The Linux Command Line (free PDF)).

    • Again, choose Activities, then enter "X" as the search term.

    • Choose Xterm.

    • Check used memory by typing df -h :

      Minimum space in home directory should 33 GB to avoud memory errors during installation. (In this example, mine is 92G, or 5%.)



  5. AND NOW..., it is time to download and extract the abap rar files to a local folder.
    First, so that the Linux system can access this folder, we need to register it for auto-mount.

  6. IMPORTANT: Make sure your Linux system is up and running.

    • Select the folder, then choose Settings, then choose Shared Folders.

    • Add a new folder to automount, by choosing the plus icon to the right:

    • In the dialog that appears, navigate to the folder that contains the ABAP installation.

    • Change the folder name to s4installer. (You will need to enter this folder name manually later, so using this alias is less error-prone than trying to remember the complete path.):

    • Choose OK, OK.

    • IMPORTANT: Reboot the Linux system.



  7. Now we are going to change some settings, before installing the uuidd daemon. This daemen provides universal unique identifiers - essential for creating database keys. (See SAP Note 1310037 for more details.)
    (Note: You only need to do this step if you are using a proxy.)

    • Open the system tool YaST (choose Activities -> enter "Y" as search term...).

    • Enter your root password (ie the one you use to log on to the Linux system.)

    • On the left, choose Software .

    • Scroll down on the right-hand side and choose Proxy.

    • CHange the http settings, tick Use same for all, then test proxy.

    • Choose OK, OK.



  8. Now we are going to install the uuidd daemon.

    • Still in YaST, scroll back up and select Online Update.

    • Open the Search tab, and and enter the search term "uuidd", then choose Search.

    • Select "uuidd", then choose Accept.
      YaST will install uuidd, then reboot.

    • End YaST.



  9. Now we are going to start the uuidd service in Xterm.

    • Open Xterm.

    • Start uuidd, by entering:  sudo service uuidd start 

    • Enter the root's password.
      (
      Note: sudo = "superuser do" ie you need to be a superuser to execute this command. Thus you also have enter the root's password.)

    • Check if the service has started by entering: sudo service --status-all |grep uuidd

    • Your Xterm will look like this:



  10. Now, still in Xterm we will change the hostname, by entering sudo vi /etc/hostname.

    • Insert the hostname by entering i (for "insert"). It should look something like this:

    • Save your changes by hitting the ESC key, then :wq (ie "colon", "Write", "Quit")

    • Check by entering sudo cat /etc/hostname

    • Restart network by entering: sudo rcnetwork restart

    • Check that the hostname has changed by entering hostname



  11. Now we will map hosts to the new hostname.

    • Check the IP address by entering sudo ifconfig

    • Open the hosts file by entering sudo vi /etc/hosts

    • Using this IP address, add a new entry of the form:
      <IP address> <hostname> <hostname>.dummy.nodomain
      (Here it is: 10.0.2.15 vhcalnplci vhcalnplci.dummy.nodomain )

    • (To add a new entry, proceed as before:

      • Enter 

      • Enter  10.0.2.15 vhcalnplci vhcalnplci.dummy.nodomain

      • Hit ESC

      • Enter :wq



    • Save the file hosts

    • Check the changes by using the cat command: sudo cat /etc/hosts



  12. And now, we will assign root privileges, by entering sudo -i.

    • Enter the root's password.

    • Navigate to the shared folder with the ABAP installation: cd /media/sf_s4installer

    • Change the access rights of the install script: chmod +x install.sh



  13. Finally, just before we install, we will ensure that we have the correct ASE license version. To do so, put the new .lic file, which you downloaded in section A above, in the same folder as the script file, using the name SYBASE_ASE_TD.lic . Do this after you have successfully extracted the ABAP .rar files. You do not need to edit the .tar files:



(Background: The .rar files for this version, 7.50, are now relatively old. However, only 7.50 supports SLT. Therefore, if you need SLT, you need to insert the correct ASE license version before you install.)



D. Install ABAP



  1. FINALLY, we run the installation, by entering the command ./install.sh


    • Read and accept the license agreement

    • When prompted for the OS users password enter your master password of the virtual Linux OS instance twice

    • Be patient, this will take a while...

    • If the installation is successful, you will see something like this:



  2. Ok, we're almost done. We just need to enter the right proxy settings so that SAP GUI, ABAP in Eclipse etc can find your ABAP system:

    • In Oracle VirtualBox Manager, select the VirtualBox with the installed ABAP system on it, then choose Settings from the context menu.

    • From the left-hand menu, choose Network.

    • Open Advanced, then choose Port Forwarding.

    • In the dialog that appears, enter the following settings:












































      Name Protocol Host IP Host Port Guest IP Guest Port
      HTTP TCP 127.0.0.1 8000 10.0.2.15 8000
      HTTPS TCP 127.0.0.1 44300 10.0.2.15 44300
      RFC TCP 127.0.0.1 3300 10.0.2.15 3300
      SAPGUI TCP 127.0.0.1 3200 10.0.2.15 3200





And that's it! Hope this helps. Feel free to comment below.
We have also provided some additional info (admin, starting / stopping the server, created directories and users, etc) in the Concise Installation Guide.

Further reading:


The first thing to do is to make yourself familiar with the Linux command line (steps 17-21). I found the most helpful guide here:
The Linux Command Line, by William E Shotts, Jr (PDF)

For openSUSE support: openSUSE forums
278 Comments
AppMan
Explorer
0 Kudos
Thanks Taryck.

 
kyo_choi2
Participant
0 Kudos

I think it was due to corporate PC with lots of security which blocks installation of developer’s tool installation.  Is there any way SAP can provide general guidance on these developer’s server usage in corporate environment?  At the least we need the ABAP Netweaver stack 7.51 and HANA express.  These all works fine on my laptop but when I come home I have to mow the lawn, do the dishes, pickup the kids.....etc. etc.. no time for studying, X^(

How do the developer do their job or learn new technology or use them as a sandbox?  Even after SAP Academy training, we need a place to review and learn the new SAP technology which there are so many of them now: fiori, CDS views, OData, Hybris, etc, etc.

Thank you.

0 Kudos
 

Does anyone have a link to the recent NPL license download page? The old license expired end of march.
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Karl,

The license you need is not for NPL (ABAP server) but for ASE (database).

Please try this:

https://sap.sharepoint.com/sites/101566/Shared%20Documents/Forms/AllItems.aspx

Please let me know if this works . Best wishes Julie.
Former Member
0 Kudos

I followed all the instructions of this valuable blog article,

 

to install the latest free SAP Developer edition,

SAP NetWeaver AS ABAP 7.51 SP02 by SAP America, Inc. (Trial Version)

https://store.sap.com/sap/cp/ui/resources/store/html/SolutionDetails.html?pid=0000014493&catID=&pcnt...

on the current openSUSE 64-bit ( with all current patches )

openSUSE-Leap-42.3-DVD-x86_64.iso

, on current VirtualBox 5.2.8 ( 100 GB filespace, 8 GB vitual RAM ),

on a Win10 64-bit PC, i7 CPU, 32 GB RAM physical RAM.

 

I started the install script as suggested after "sudo -i" in the mounted NTFS directory

/media/sf_s4installer

by "./install.sh"

and entered

ENTER key

# after "Hit Enter to continue"

yes

# to acknowledge the license

suse2018

# I am asked to set the "password for the OS users" two times

 

But the installation script “install.sh” breaks by the error message.

*******
Abort execution because of Step returns modlib.jslib.caughtExecption.
Installation of NPL failed, please check logfiles in /tmp/sapinst_instdir for possible root cause
*******

At

/tmp/sapinst_instdir/NW73/SBC/STANDARD/sapinst.log

there are 2 ERRORs quite at the end of the logfile, after that there are 3 minor non-error messages at the end of the file:

*******

INFO 2018-04-12 14:41:46.165 (root/sapinst)
Account sybnpl does not exist.

INFO 2018-04-12 14:41:46.200 (root/sapinst)
Account npladm does not exist.

INFO 2018-04-12 14:41:46.297 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.

INFO 2018-04-12 14:41:46.336 (root/sapinst)
Execute step fillContext of component |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_os_users|ind|ind|ind|ind|osUsers|0

INFO 2018-04-12 14:41:46.514 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.

INFO 2018-04-12 14:41:46.835 (root/sapinst)
Execute step setValuesFromInputParameterFile of component |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|offlineadjustment_os_users|ind|ind|ind|ind|osUsers|0

INFO 2018-04-12 14:41:47.007 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.

INFO 2018-04-12 14:41:47.563 (root/sapinst)
Execute step fillContext of component |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

INFO 2018-04-12 14:41:47.735 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.

INFO 2018-04-12 14:41:48.203 (root/sapinst)
Execute step fillContextFromParameterFile of component |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

INFO 2018-04-12 14:41:48.375 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.

INFO 2018-04-12 14:41:48.556 (root/sapinst)
Execute step init of component |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

INFO 2018-04-12 14:41:48.722 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.

INFO 2018-04-12 14:41:48.997 (root/sapinst)
Execute step setDefaults of component |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

INFO 2018-04-12 14:41:49.196 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD.

INFO 2018-04-12 14:41:49.451 (root/sapinst)
Execute step askSidAdm of component |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

ERROR 2018-04-12 14:41:49.626 (root/sapinst) 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-04-12 14:41:49.729 (root/sapinst) 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-04-12 14:41:49.953 (root/sapinst)
Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/INSTANA.XML.

INFO 2018-04-12 14:41:50.043 (root/sapinst)
Creating file /tmp/sapinst_instdir/NW73/SBC/STANDARD/instslana.xml.

INFO 2018-04-12 14:41:50.399 (root/sapinst)
Working directory changed to /tmp/sapinst_instdir/NW73/SBC/STANDARD

 

*******

Even a local SAP Code Jam lecturer had no clue what is wrong, a year ago he succeeded with installation of SAP on openSUSE.

He suggested me not to consider the “To solve that problem start the installation without using SAPINST_START_GUI option” hint, as the installation process of the free developer edition is console/text-based only. He was unable to tell me how to apply this tip or whether this tip is useful.

Any help is appreciated.

Sincerely

Rolf

julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Rolf, Thanks for your clear summary.

I am officially out of office. But 2 users solved this issue by renewing their ASE license. Can you check yours : it may have expired in March 2018?

Best wishes, Julie.
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Nicola,

No, it says “IF you have a proxy....”.

So dont worry if you don’t- just skip those steps.

Best wishes,

Julie.
Former Member
0 Kudos

Julie,

I am very sorry, but your answer is inadequate.

I fail with the installation process prior the application or even installation of a license file. So I dont have any ASE license file installed.

Btw, the install script demands entering a general password, There was no indication about the requirements for that, so I entered

suse

, later I tried a new SAP installation with password

suse2018

as password for my local, non-productive free development SAP server.

Is that ok, or might be the reason why the installation breaks ?

What kind of passwords are expected and accepted by the script ?

 

Same failure by “askSidAdm”, looks like having the same break message ( but according to the thread creator, was solved by simply using usernames which conform to SAP standards )

https://answers.sap.com/questions/455114/abap-trial-asksidadm-reports-error-on-install-sap.html

 

Might somebody open a "ticket" ?

Or might tell me how to do that, and where ?

 

julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Rolf, I answered this in the other comment you posted.:

https://answers.sap.com/questions/455114/abap-trial-asksidadm-reports-error-on-install-sap.html?chil...

Trust me: The license may not be valid. The install script checks before completing the install.

It is quite possible that you have a different problem; if so, please then let me know. The license check is just the first step. 

See my other comment for more details.

Best wishes Julie.

0 Kudos
Hi. I've installed sap trial successfully but I cannot connect it via Eclipse because it requires SNC connection. What should I type there? In my version of Eclipse, SNC is obligatory. I've tried to use 127.0.0.1 and the host name, however it ends up with the same mistake "Logon to system NPL failed (SNCERR_BAD_NT_PREFIX, SncPImportPrName() parsing error, name="127.0.0.1")"
0 Kudos
Hi Julie,

sorry I did forget to mention. All is up and running.

Thanks,

Karl

 
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Karl, Good to know thanks!

Best wishes Julie.
0 Kudos
Thank you Julie!

Worked perfectly.

 
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Excellent!

Best wishes
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi All,

New ASE license is available here: ASE License 2019 - have updated link at top of blog.

Best wishes Julie.
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
PS taryckbensaili  - thanks a lot for all your Community support.

Best wishes Julie.
0 Kudos

Starting SAP Server after a reboot.

Hello All,

Please use following command in xterminal (xterm, not terminal)  to START your SAP server after a Linux/PC reboot:

su -c “startsap all” -l npladm

  • please wait until system is fully operative, after you should be able to connect to your SAP instance using SAPGUI from Windows/MAC
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Teodor,

Why? I have never had a problem with terminal - could you please provide details?
Thanks Julie.
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
"In my version of Eclipse, SNC is obligatory. "

I'm on Oxygen 4.7.1 - it's recommended but not obligatory.

Please update your Eclipse. AFAIK, we don't provide SNC with the free trial edition.

Best wishes Julie.
Hello Julie,

 

I faced only one issue during the setup process. I received the NPL installation failed error message, even after  i renewed the license key using untar > replace license file > tar dbexe.tgz-aa.

I resolved this issue and installed NPL Server successfully using nano application under Gnome Terminal, (not  Xterminal)

  • i opened Terminal, launched "su" command

  • navigate with nano to license file , directly under dbexe.tgz-aa (no untar needed), copied and pasted new license text then save.

  • still under Terminal i used the nano command for install.sh

  • I found this fix on youtube.

julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Teodor,

Ah, thanks for the response. I'll make a note of this.

Best wishes,

Julie.
marcobuescher
Active Contributor
0 Kudos
Hello,

 

my MINISAP runs now since a few month. -But now I have the Problem that the CPU Used 100% and the VM and also SAP freeze for ca. 1/2 up to 1 hour. After that everything is fine. On day later, the same problem. Freeze for one hour and after that everything is fine...

Had somone the same problem an solved it?

 

Best regards.
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Dear all,

As of now, I will not be able to moderate comments on this blog. Therefore, comments entered after today, 26th July, 2018 will have to be ignored. (I will try to process existing comments as soon as I can, but there is a backlog.)

From now on, please ask your question in the ABAP Development Community forum:

https://www.sap.com/community/topic/abap/all-content.html

If it is an issue involving ABAP developer edition, remember to add the hashtag #ABAP_Trial.

Please do not use comments in the blogs to ask tech support questions :

  • It makes it difficult for other users to find similar issues in future, which leads to many duplicated errors.

  • Very few people follow these blogs, so you will not get help from the vast majority of the community



I apologize for this, but there is no capacity to monitor all blogs for all released versions.

Best wishes Julie.

 

 
0 Kudos
Hi!

I am stuck at Point no.12 assign root privileges. I went step by step but I got this error which I have attached. Please guide me for this situation.

Thank you.
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Jimit,

This appears to be a known issue for some users - so far, an issue with the new VBox and MS Windows 10.

That is, it is not an issue with the AS ABAP. However, you do not have to use the "Mount" function: Instead, use WinSCP. Step-by-step guide is here:

VMWare Guide

If that fails, please please create a question - I have explained why above :

ABAP Forum

HTH Julie.
harryguenter
Member
0 Kudos
I tried the Installation but end up with:

Abort execution because of
Step Returns modlib.jslib.caughtException

I've read that it could be caused by a Licence Problem. However I saw that the ASE License provided expired by the end of march 2020.

Are there any chances that the License is prolonged?
julieplummer20
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Harry,

No, for legal reasons we cannot prolong the license.

Please upgrade to AS ABAP 7.52 SP04. All links and info here: https://blogs.sap.com/2019/07/01/as-abap-752-sp04-developer-edition-to-download/

Best wishes,
JUlie.
amani7681
Discoverer
0 Kudos
pleas asst me when try instaal abap i got error please help me

To install this TestDrive you have to accept
the SAP COMMUNITY DEVELOPER License (DEV).
Do you agree to the above license terms? yes/no:
User's response to the accept license prompt = 'y'
Please enter a password:
Please re-enter password for verification:
extracting data archives...
extracting /media/sf_ABAP752/server/TAR/x86_64/dbdata.tgz-*
extracting /media/sf_ABAP752/server/TAR/x86_64/dblog.tgz-*
extracting /media/sf_ABAP752/server/TAR/x86_64/dbexe.tgz-*
extracting /media/sf_ABAP752/server/TAR/x86_64/usrsap.tgz-*
extracting /media/sf_ABAP752/server/TAR/x86_64/sapmnt.tgz-*
Checking Linux kernel memory management parameters according to SAP Note 941735
Backing up /etc/sysctl.conf in /etc/sysctl.backup
Checking Linux kernel parameter vm.max_map_count according to SAP Note 900929
Checking presence of new SYBASE license files
Replaced the license file /sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_TestDrive.lic
Waiting 30 seconds for asynchronous call to /tmp/hostctrl/saphostexec -install to complete...
Install service
Check Installation Path ...

saphostexec is already running (pid=8077). Stopping...Stopped
ok
Copy Executable ...
ok
Generate Profile ...
ok
Install SYS-V service ...
[WARNING] installsapinit.sh exit with status 5
-> Start /usr/sap/hostctrl/exe/saphostexec pf=/usr/sap/hostctrl/exe/host_profile <-
start hostcontrol using profile /usr/sap/hostctrl/exe/host_profile
ok
[OK] SAPHostExec / SAPHostControl succesfully installed
Executing: "/usr/sap/hostctrl/exe/SAPCAR" -xvf "./SHADBMETRICSDEF.SAR" -R "/usr/sap/hostctrl/exe/config.d"
SAPCAR: processing archive ./SHADBMETRICSDEF.SAR (version 2.01)
x dbmetric.definition.db4.cimobj
x dbmetric.definition.db6.cimobj
x dbmetric.definition.hdb.cimobj
x dbmetric.definition.mss.cimobj
x dbmetric.definition.ora.cimobj
x dbmetric.definition.sap.cimobj
x dbmetric.definition.siq.cimobj
x dbmetric.definition.syb.cimobj
x dbmetric.definition.tst.cimobj
x dbmetrics.d
x dbmetrics.d/00.general.hdb.cimobj
x dbmetrics.d/00.state.hdb.cimobj
x dbmetrics.d/10.host.capacity.hdb.cimobj
x dbmetrics.d/20.indexserver.hdb.cimobj
x dbmetrics.d/20.nameserver.hdb.cimobj
SAPCAR: 15 file(s) extracted
SAPCAR: rc 0
30 seconds are up, continuing the main script.
=>sapparam(1c): No Profile used.
=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
################################################
Abort execution because of
Step returns modlib.jslib.caughtException
################################################

Error: sapinst has finished with an error code, please find logs in /tmp/sapinst_instdir
Error code: 20
++++ Support data section BEGIN ++++
* mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=4096k,nr_inodes=1048576,mode=755,inode64)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=3734164k,nr_inodes=819200,mode=755,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
/dev/sda2 on / type btrfs (rw,relatime,space_cache,subvolid=268,subvol=/@/.snapshots/1/snapshot)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17713)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda2 on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=267,subvol=/@/.snapshots)
/dev/sda2 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,space_cache,subvolid=265,subvol=/@/boot/grub2/x86_64-efi)
/dev/sda2 on /boot/grub2/i386-pc type btrfs (rw,relatime,space_cache,subvolid=266,subvol=/@/boot/grub2/i386-pc)
/dev/sda2 on /root type btrfs (rw,relatime,space_cache,subvolid=262,subvol=/@/root)
/dev/sda2 on /opt type btrfs (rw,relatime,space_cache,subvolid=263,subvol=/@/opt)
/dev/sda2 on /srv type btrfs (rw,relatime,space_cache,subvolid=261,subvol=/@/srv)
/dev/sda2 on /usr/local type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/@/usr/local)
/dev/sda2 on /tmp type btrfs (rw,relatime,space_cache,subvolid=260,subvol=/@/tmp)
/dev/sda2 on /home type btrfs (rw,relatime,space_cache,subvolid=264,subvol=/@/home)
/dev/sda2 on /var type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/@/var)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1867080k,nr_inodes=466770,mode=700,uid=1000,gid=100,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
ABAP752 on /media/sf_ABAP752 type vboxsf (rw,nodev,relatime,iocharset=utf8,uid=0,gid=465,dmode=0770,fmode=0770,tag=VBoxAutomounter)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
* df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 9.0G 4.0K 9.0G 1% /dev/shm
tmpfs 3.6G 26M 3.6G 1% /run
tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
/dev/sda2 98G 42G 55G 44% /
/dev/sda2 98G 42G 55G 44% /.snapshots
/dev/sda2 98G 42G 55G 44% /boot/grub2/x86_64-efi
/dev/sda2 98G 42G 55G 44% /boot/grub2/i386-pc
/dev/sda2 98G 42G 55G 44% /root
/dev/sda2 98G 42G 55G 44% /opt
/dev/sda2 98G 42G 55G 44% /srv
/dev/sda2 98G 42G 55G 44% /usr/local
/dev/sda2 98G 42G 55G 44% /tmp
/dev/sda2 98G 42G 55G 44% /home
/dev/sda2 98G 42G 55G 44% /var
tmpfs 1.8G 68K 1.8G 1% /run/user/1000
ABAP752 466G 103G 364G 23% /media/sf_ABAP752
* df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
devtmpfs 1.0M 481 1.0M 1% /dev
tmpfs 2.3M 2 2.3M 1% /dev/shm
tmpfs 800K 798 800K 1% /run
tmpfs 1.0K 19 1005 2% /sys/fs/cgroup
/dev/sda2 0 0 0 - /
/dev/sda2 0 0 0 - /.snapshots
/dev/sda2 0 0 0 - /boot/grub2/x86_64-efi
/dev/sda2 0 0 0 - /boot/grub2/i386-pc
/dev/sda2 0 0 0 - /root
/dev/sda2 0 0 0 - /opt
/dev/sda2 0 0 0 - /srv
/dev/sda2 0 0 0 - /usr/local
/dev/sda2 0 0 0 - /tmp
/dev/sda2 0 0 0 - /home
/dev/sda2 0 0 0 - /var
tmpfs 456K 72 456K 1% /run/user/1000
ABAP752 1000 -976K 977K - /media/sf_ABAP752
* cat /etc/os-release
NAME="openSUSE Leap"
VERSION="15.5"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.5"
PRETTY_NAME="openSUSE Leap 15.5"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.5"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap"
LOGO="distributor-logo-Leap"
* ls -ld / /sybase /usr/sap /sapmnt
drwxr-xr-x 1 root root 190 Nov 9 12:53 /
drwxr-xr-x 1 root root 6 Sep 6 2019 /sapmnt
drwxr-x--- 1 sybnpl sapsys 6 Feb 20 2017 /sybase
drwxr-xr-x 1 root root 68 Nov 9 12:55 /usr/sap
++++ Support data section END ++++
All logs have been written to the file /media/sf_ABAP752/install_2023-11-09_12-49-46.log
Please see readme.html to find out how to get help

 
Labels in this area