I have created an SAP 7.2.10 self-contained .exe file using the SAP Tool, NWSapSetupAdmin.exe. When I click on the self-contained package to test the install, I receive an error message in a splash screen that reads, "The package cannot be installed as it contains components with failing prerequisites" If I click through the error to the next screen and select the presented components that are contained within the .exe file, the package installs. I've read the log files and have checked that .NET is there on Windows 7 and Windows XP machines as well as other software such as Office, Adobe Reader, MSXML 4, and java. It still gives me the error regardless of what is included on the VM OS for software.

When I try to run the .exe to install from the command line, it extracts all the files and then throws either the Return-Code: 70 or 48, depending on the syntax of the command line. I've tried /silent /package="MySAP.exe" and just about any other suggestion from forums. The only thing that changes is the Return-code from 70 to 48. I've tried searching for the error code hoping it will tell me what is missing. Does anyone have any idea what is causing this Prereq error?

Thanks so much for any help! I must have this installer ready for testing in 2 days.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


What version of Microsoft Outlook (if any) are you running on the installation target ? Only reason I ask is that some SAP-related forum entries seem to indicate there is a possible incompatibility with the Outlook client extension general add-on for SAP GUI 7.2 and MS Outlook 2010.

Answered 03/08/2012 by: spartacus
Black Belt

Please log in to comment
i had a similar issue and i found out that the sap installer was looking for a registry key that was not the correct one.

the setup was looking for a key under HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5\SP with value 1. since my installation of .net 3.5 sp1 did not have that key, i lie to setup with a wrapper.

my wrapper check if the correct key for .net 3.5 sp1 exists on the computer and if so, it adds the key that the setup is looking for. that way, setup is bluffed and installs sap fine.

i hope this help!
Answered 03/08/2012 by: kardock
Second Degree Green Belt

Please log in to comment