Software Center says "failled" but software is curently installing. Why?
Hi, i`m trying to configure in SCCM 2012 a Software called Matlab 2015a.
I have the correct command line to do it ( setup.exe -inputfile "myinputfile.txt" ) but as soon as i click the install button, i get error code 0x87d00324.
If i look at the processes on my client computer, i see setup.exe running and the software does install succesfully but still shows up as a faillure until it runs a software evaluation.
It`s as if the detection methode is running before the software as a chance to install itself or SCCM is not monitoring the progress of the installation.
Anybody have had this happen before ? Is there something i can add to my command line to have that working properly ?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
9 years ago
I'd bet my last dollar that the set-up EXE you're running is extracting and executing another set-up EXE and the first is not waiting for a return value from the second. This is a favourite numpty move by vendors.
Comments:
-
OK, i found another setup.exe in a subfolder of the installation media. I`m assuming the first setup.exe is calling the second. I don`t want to run the second setup.exe directly because i`m not sure what else the first setup.exe does. Is there anything i can do to get the first setup.exe to wait ? - KevinViolette 9 years ago
Posted by:
dedenker
9 years ago
Also take a look at the exit code.
If not different defined and thus not 0, it is an error.
If not different defined and thus not 0, it is an error.
Posted by:
anonymous_9363
9 years ago
>i`m not sure what else the first setup.exe does
Easy. Take a gap-capture:
- run the second EXE
- rename any registry entries it might put beneath the 'Uninstall' branch in HKLM (so that if the first EXE checks, it will think the second EXE hasn't installed the product, see?)
- take a 'Before' snapshot using a lightweight snapshot tool of your choice
- run the first EXE
- take an 'After' snapshot
If, as I expect, this is an InstallShield script-driven installer, you might see some InstallShield related junk in the registry.
Easy. Take a gap-capture:
- run the second EXE
- rename any registry entries it might put beneath the 'Uninstall' branch in HKLM (so that if the first EXE checks, it will think the second EXE hasn't installed the product, see?)
- take a 'Before' snapshot using a lightweight snapshot tool of your choice
- run the first EXE
- take an 'After' snapshot
If, as I expect, this is an InstallShield script-driven installer, you might see some InstallShield related junk in the registry.
