/build/static/layout/Breadcrumb_cap_w.png

setup.exe calling msi

In Blackberry Desktop Manager when i try to run setup.msi it throws up an error message saying

"This installation cannot be run by directly clicking msi file"

there is a SETUP.EXE file which calls SETUP.MSI.

I want to run SETUP.MSI directly

SO how to go bout that?

reply as soon as possible.

0 Comments   [ + ] Show comments

Answers (12)

Posted by: bheers 15 years ago
Second Degree Blue Belt
0
I do not think this is an ideal method but still works

Open the setup.msi in Orca and check the launch condition table for the error you are getting and remove it or you can use a transform to remove the launch condition.
Posted by: Bladerun 15 years ago
Green Belt
0
what version of desktop manager?
Posted by: sunny_sahdev 15 years ago
Senior Yellow Belt
0
i m working on version 3.6.2.9
Posted by: sunny_sahdev 15 years ago
Senior Yellow Belt
0
there is no entry for the error message i m getting in the condition table.
Posted by: Thaiboxer 15 years ago
Orange Belt
0
Try running "setup.exe /a". This should allow you to create an administrative installation point for your msi. A lot of Installshield setups make you run setup.exe because there's an isscript*.msi wrapped up in there that needs to be installed as a prerequisite to the msi.

Good luck.
Posted by: bheers 15 years ago
Second Degree Blue Belt
0
there is a property STANDARD_USE_SETUPEXE which is used to run the msi from the setup.exe. deleting the property does not help. there should be a way to get around this property.
Posted by: totoymola 15 years ago
Orange Belt
0
What is the value of the property STANDARD_USE_SETUPEXE? Don't delete it. Try setting it's value to zero (or NO if it's set to YES).

Or, if it's an InstallScrpt MSI, try using ISSETUPDRIVEN=1 property.

About making an AIP, sometimes setup.msi /a doesn't work. It has to be msiexec /a setup.msi sometimes. I don't know why.
Posted by: sunny_sahdev 15 years ago
Senior Yellow Belt
0
guys its still not working out.

actually ISSCRIPT.MSI is also involved.

SETUP.EXE calls ISSCRIPT.MSI which in turn calls SETUP.MSI

I have tried the diffrent approaches you people suggested, but its still not working out.

HELP ME OUT>>>>>>>>>>>>
Posted by: totoymola 15 years ago
Orange Belt
0
If it has isscrpt.msi, then it's InstallScript. This is my experience with InstallScript (long time ago).

1. Install the isscrpt.msi first.
2. Install the setup.msi with the ISSETUPDRIVEN=1 commanline switch.

example batch file:

@ECHO OFF
START /W MSIEXEC /I ISSCRIPT.MSI /QB
START /W MSIEXEC /I SETUP.MSI /QB ISSETUPDRIVEN=1
EXIT


This used to work with the software that I was trying to install before.
Posted by: Bladerun 15 years ago
Green Belt
0
Admin Studio 6 claims that it can convert an ISscript install to a standard MSI using the repackaging tool.

That being said, I've attempted it once and it didn't work.
Posted by: sunny_sahdev 15 years ago
Senior Yellow Belt
0
the scenario is something like this>>>

setup.exe extracts some files in user profile and then isscript uses them in msi.

so even if i somehow manage to run msi directly, i'll most probably get an error related to those files extracted by setup.exe.

LIFE IS NOT SO EASY........
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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