Software Provisioning Manager: new logfiles to check kernel archives dependencies
With the latest version of SAPinst, a new and better logfile for kernel archives (*.sar) errors is available
You may be aware that underlying the Software Provisioning Manager is the SAPinst which gets updates independent from Software Provisioning Manager release.
With the latest update of SAPinst, version 749.0.45, there is a new functionality that improves the error analysis in case the wrong archives were chosen for the installation of a software product (e.g. installation of Netweaver 7.50).
Up to now you had to search in different logfiles, manifest files etc. to find the reason why an archive was rejected from the installation procedure. Dependencies of different packages made the analysis of the root cause of the problem quite difficult.
Now with the new functionality this becomes much easier!
On this screen, you see where the packages (archives) for the installation have to be entered in Software Provisioning Manager:
As you can see, 4 files are necessary and the path to the four files needs to be entered. Those four archives have dependencies and will be checked before being accepted by the installation.
If one or more of the archives is wrong, you will get a link <information file>.
And going from there you get a summary logfile inside the Software Provisioning Manager that shows exactly the reason for not accepting one or more of the archives.
In the below case, the wrong Kernel Patch Version is provided:
And now you will also get the information what kind of dependencies cause the problem:
In the case that is shown here, the version requested in the manifest file and the available archives version do not match.
As mentioned, the functionality for the second case, wrong dependencies, is available as of SAPinst version 749.0.45. You will get this version automatically when you download the latest version of Software Provisioning Manager from the Service Marketplace.
Stefan Jakobi Product Management CLM