Skip to Content

Continued from my last blog, Caboodle – Overview

Before I jumped into the download and installation, I made sure of a couple of things that I knew I would run in to. So I performed a little system preparation.

Update: As I found out later, and I should have really known this, the VM would have a Virtual Network Connection of some sort or another, so there was no need to have prepared the loop back adaptor, for the VM. It has caused me a little grief, So now I do not have the VMs network connected.



I remember when installing the NSP 7.0, there were some fully qualified domain name (FQDN) issues. So prior to installing, I configured my VM to have a FQDN in Windows.

Navigate to the Computer Properties. Under the “Computer name, and workgroup settings, select the “Change Settings”.

I changed my Computer name to “vm”.


I then pressed the “More…” button, to add the Primary DNS “”.


After re-starting, and returning into the Computer Properties, you can see my VM’s Full computer name, is “”.



For the NSP installation only, I needed a JRE v1.4 or v1.5. I think 1.5 is badged as 5.x under the sun downloads, not 100% sure, as I went for my reliable 1.4.2_19. The file name is j2re-1_4_2_19-windows-i586-p.exe. I found under the archives section at Install as normal.


Go to “SDN”->”Downloads”, from here it’s immediately visible, in the middle section. It took me just over an hour to get both in parallel, and here they are.



Unpacked, they look like this




I eventually saved them onto my VM’s Desktop


It goes without saying, that you must have administrator rights on the machine, and wherever possible, always install under an administrator.

There is no real need to dig out any other documentation. What you see here should hand hold you. If I point you to somewhere, then that means, that documentation is sufficient and correct.

Having said that, should you wish to see more in depth documentation, under a nested sub directory called “DOCS”, there is a document called “FullInstallationGuideNW702MaxdbWin32”. It’s good, but a little overkill for reading right now. I simply started with the “start.htm” located in “NWABAPTRIAL70206_64NWABAPTRIAL70206_64”. 

Try to follow my notes here, first, and if you run into any trouble, take a peek at the documentation, or do both.

Loopback Adapter

So after starting up the installation overview page, do check out the prerequisites. Make sure you do the Loopback Adapter. The install screenshots are slightly different, but you can guess what is required from Windows 7. My hardest task was finding out how to execute the Hardware Wizard. Here’s how “Start”->”Run” and entered “hdwwiz”.

My entry in the hosts file looked like this


The fun starts under the section “Installation”.

Time: 09.45

I found the “sapinst.exe” and fired it up. I decided not to snap every screen.

“Ok” to log off, and log on. This is not a Cold Reboot. The screenshot is a little bad, because i needed to reduce the size, but it is simply the “Log you off” prompt.



It automatically logged me off, and back on again. You may have to perform the log on manually, I cannot remember if I set my user to automatically logon. The installation continued


Point to JRE, “Next”


Passwords: DO NOT USE “@” or other strange characters. If you use a Group Domain Policy, make sure the password adheres to it. These will catch you out. “Next”

Prompted with a system requirement message, and selected “Cancel” to continue


Now pointed to the second downloaded file, the Exports. There was no need for me to perform a copy, as the files are fine where they are (my desktop)


I have always been happy with the default database configuration, so I left it as it is.


But then I got an error saying there was not enough room on my hard drive. I thought I had given it 100GB, so I went off to investigate. When I looked at my VMs Local Disk Drive, it reported 40GB size.

So I had to “Exit” the installation and go see what the deal is with the VM.

I then realized, when I specified the VMs hard drive to 100GB, from it’s original 40GB, it did not automatically increase the partition size inside the VM to suit. So in the VM, I increased the partition manually to the full 100GB available.

After making the changes, I restarted the installation, again using “sapinst.exe”, but this time using the “Continue with the old option” option.


It soon catches up to where I exited, and continued on from there. All the “Parameter Summary” parameters were left to default, and then the actual installation tasks began. I wish I had a snapshot for you to see, but I missed it.

Time: 10:12hrs



It stays around here for hours, and I mean, HOURS, about 8 in all



Eventually, at 18:55hrs, a good 9 hours later



I restarted the VM to double check the installation, and was presented with an extra three desktop users. I logged on using “nspadm”, and will do as default from now on.

Here’s how to set a user to log on automatically when you reboot or restart, even if they have a password. Use the command “control userpasswords2” in the “Run” prompt.


Before you try starting the NSP, navigate to the “Windows Services” and manually start the “MAXBD: NSP”. Now start the NSP from the “SAP Management Console”, on the desktop. It will fool you by turning green in a matter of seconds, then drop into yellow before returning back to green, after about 4 minutes.


Although there is a SAP GUI and SAP GUI for Java included, I decided to download the full SAP GUI 7.2 #50102369_4 from the SMP. Previously the SAP GUI installed with the trial software was a cut down version. Not saying that this is the case now, just that I prefer the main download.

As well as the SAP Logon, I also installed the Business Explorer, BW 3.5 Add-On for SAP 7.2, Unicode RFC Libraries.

I then setup the SAP GUI configuration,


and logged in with user BCUSER. There is no need to create this user as instructed, because it already exists.

All user passwords are set to what was prompted for during install.


  • Passwords: Do not use characters such as “@”, and adhere to a Group Domain Policy, if present (mentioned earlier)

  • Do not do an SGEN unless you can leave the machine running for 2 or 3 days

  • Do not change SID, or any other defaults, if you can help it

  • Change the “MAXDB” Services in Windows to Start Type “Automatic” to automatically start the DB Services

  • Stop the NSP System in the MMC, before you close down the computer

  • If the NSP does not start using the MMC, try this command line and look for any messages.  Substitute -P for your user password and -e for your user

“C:usrsapNSPDVEBMGS00exesapstartsrv.exe -r -q -p C:usrsapNSPSYSprofileSTART_DVEBMGS00_pc -s NSP -n 00 -U pcSAPServiceNSP -P abcd1234 -e PC


Continue to my next blog, Caboodle – Part 2 – The NSP 7.02 Post InstallCaboodle – Part 2 – The NSP 7.02 Post Install

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

Leave a Reply