I am trying to create a package which seems to install fine but from SCCM it does not work.
Following command line is working from admin command prompt and when run manually 
setup.exe -s -f1c:\temp\setup.iss
%~dp0setup.exe -s -f1c:\temp\setup.iss
%~dp0setup.exe -s -f1%~dp0setup.iss

But none of these command lines run from SCCM. I verified that setup.iss is there in temp folder and install just errors out 
%~dp0setup.exe -s -SMS -f1%~dp0setup.iss did not work from SCCM either

Process 3992 terminated with exitcode: 2147753984
Looking for exit code -2147213312 in exit codes table...
Unmatched exit code (2147753984) is considered an execution failure

I have run out ideas how to get this to work from SCCM 2012.


0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0
How is the setup.iss file getting into C:\Temp? Isn't it part of your package?

You should just be able to run 'setup.exe -s -SMS' without referencing the setup.iss file - if it's in the same directory as setup.exe then it is automatically picked up and used.
If you're running from DP, try download to cache and run - I've had some success with that in the  past.

This post has lots of useful info on various approaches you could try.

I would also run this as package, and not an application in SCCM 2012.

Hope that helps,
Dunnpy
Answered 08/21/2015 by: dunnpy
Red Belt

Please log in to comment
0
If I remember correctly, it will try to create a log file for installation on the source folder itself if the log file name and location are not mentioned explicitly.
So, when you run this installation manually, it should have created a log file for installation on the source folder, where as it can not create it when you install the same via SCCM.

So, you have to use the following command

"%~dp0setup.exe" -s -f1"%~dp0setup.iss" -f2"%Temp%\MyAppInstall.log"
Answered 08/21/2015 by: jagadeish
Red Belt

Please log in to comment
0
Do the maths and then look up the exit code: -2147213312 as hex is FFFFFFFF80042000. Remove the leading Fs and Google for 'installshield exit 80042000':

0x80042000    installation exited with the abort keyword because the end user canceled the installation.
Now of course we know that no user cancelled anything so we can safely assume that the EXE didn't like the command line, as entered. I'm with Jags on this one - you must include quote marks around the paths, something I always do anyway.


Answered 08/23/2015 by: VBScab
Red Belt

Please log in to comment
0

I had a similar issue previously.

Resolved it by making a batch script with the above commands entered and saved the application as an application in SCCM.

Dump everything into the source folder and target the batch script and it runs fine the .iss fine.

Answered 08/27/2015 by: revel
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity