/build/static/layout/Breadcrumb_cap_w.png

Install shield exit code -2147213312 , SCCM package

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

Answers (5)

Posted by: terebent 7 years ago
Second Degree Brown Belt
2
I had this issue installing JMP 13 application even if all the paths were added between quotes. 

This is the command line used: "%~dp0setup.exe" -s -f1"%~dp0silent.iss" /f2"c:\temp\jmp13_install.log"

My problem with this installation was the installation folder. If the installation folder is already created the installation fails when is running silently.
So if your are doing an update for previous version you have to be sure that the installation folder is deleted.


Comments:
  • What do you mean by 'be sure the installation folder is deleted'? I'm running an update for Fujitsu ScanSnap Manager so I think this must be my problem. I think the previous version has to be installed to run this update package so I don't know what you mean by delete the install folder. - kbelcher 6 years ago
Posted by: dunnpy 8 years ago
Red Belt
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
Posted by: jagadeish 8 years ago
Red Belt
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"
Posted by: anonymous_9363 8 years ago
Red Belt
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.


Posted by: revel 8 years ago
White Belt
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.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ