Question Re: Missing installation options in Software Provisioning Manager in Technology Q&A

Missing installation options in Software Provisioning Manager

timkudla — Fri, 16 Nov 2018 08:29:38 GMT

Hi community,

I'm about to install an SAP Diagnostic Agent. I had already downloaded the files and used them for a previous installation. Now the error has occurred that the start page of the Software Provisioning Manager opens, but this time no installation options are displayed. Unpacking the <SWPM>...<.SAR> file again was not successful at this point. Are there any other things I might have overlooked this time?

Thanks in advance!

Re: Missing installation options in Software Provisioning Manager

BJarkowski — Fri, 16 Nov 2018 09:11:51 GMT

When you start SWPM for the first time, it asks to provide root username and password. Such a blank screen happened to me a few times, where I either missed the credentials or provided an incorrect one. Try to open the browser in private mode and open SWPM there - it should ask you to provide the credentials again.

If that won't help, then we probably need to look at SAP Host Agent log files. Check the first point from following guide:

https://wiki.scn.sap.com/wiki/display/ATopics/SAP+Host+Agent+Troubleshooting+Guide

Re: Missing installation options in Software Provisioning Manager

timkudla — Sat, 17 Nov 2018 10:21:16 GMT

The window for the registration came reliably with each attempt. In the log I found several lines with the hint for missing permissions. Do I have to be a local admin to install it?

Re: Missing installation options in Software Provisioning Manager

BJarkowski — Sat, 17 Nov 2018 11:27:05 GMT

Yes, you need to be local admin - root in Linux or user belongin to the admin group in Windows.

Check the installation guide for details:

https://help.sap.com/viewer/30839dda13b2485889466316ce5b39e9/CURRENT_VERSION/en-US/035d56523c9e4730a6d99b2dca29cb43.html

Re: Missing installation options in Software Provisioning Manager

timkudla — Mon, 21 Jan 2019 06:51:45 GMT

The cause was a missing authorization at system level. The user was in the local admin group, but was apparently not restarted after the adjustment in the AD.