HI All,

I am trying to package the above application with great difficulty! The application is supplied as an exe which has an embedded MSI. After extracting this MSI and trying to run it as a stand alone it says it requires the exe to be executed. I need to apply a transform for the customer and this is where the problems start! I can run the setup.exe with an (response)iss file however when I try and apply the transform aswell it seems to just bomb out, nothing happens. Has anyone packaged this application and overcome these issues?

Thanks in advance[:)]
0 Comments   [ + ] Show Comments

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.

Answers

0
Try adding the property ISSETUPDRIVEN=1 to the MSI and see if you are able to run the MSI.
Answered 06/22/2006 by: Lillude
Senior Purple Belt

Please log in to comment
0
This is regarding the same app (me and oReilly sit the same office).

We've added that property already, with no change.

The setup.exe can be installed with the iss file no problem, but as soon as the transform is added to the command line the problem starts.

The command line were using is:
setup.exe /s /f1setup.iss /v"/qb TRANSFORMS=MorelloModelOffice.Mst /l*v c:\install_MorelloLOG.log"

From what i can see in the log its extracting the vendor MSI and copying all relevant files to the windows directories, but not getting any further. It doesn't appear to actually get to the install phase at all.

When trying to execute the MSI directly it kindly explains that the EXE must be ran rather that the MSI directly, im wondering if this has anything to do with it?

Unfortunately I havn't been in this game for long, i have a good understanding for the software processes, but not these embedded MSIs with problems like this! I can paste the log file output in if it would help...?

Any further information would be greatly appreciated.

Many thanks

Daniel
Answered 06/22/2006 by: DeasD
Yellow Belt

Please log in to comment
0
This is because you're using the /qb switch.
Remove the OnCheckSilentInstall CA from the InstallExecuteSequence table, that should resolve your issue.
Answered 06/22/2006 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: AngelD

This is because you're using the /qb switch.
Remove the OnCheckSilentInstall CA from the InstallExecuteSequence table, that should resolve your issue.



Nice one AngelID :) rated 2 points
Answered 06/23/2006 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
There do also exist an CA called ISVerifyScriptingRuntime placed in the beginning of the User Interface sequence.
ISVerifyScriptingRuntime verifies that the InstallScript MSI installation was launched using Setup.exe.

So if you would like the package to execute in all sequences you would have to remove this also.


MSIMaker: thanks mate
Answered 06/27/2006 by: AngelD
Red Belt

Please log in to comment
0
To be honest, I went through the custom actions and removed all the ones I thought that were checking for the setup.exe This didn't really make much difference as the vast majority of the actions required the exe process to be running (I had to disable pretty much all of them, at which point files wern't being registered, I was getting un-fixable errors etc...).

In the end I re-captured the install and compiled that to a new MSI, it was the only way I could see it working. Im not sure whether it will of picked up everything, but im sure our testing team will flag me up if that is the case!

Thanks for your help though guys.
Answered 06/27/2006 by: DeasD
Yellow Belt

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