wait until (un)install msi command has finished

[Ton_B]

I've got two setup packages both created with IA.

The first setup is a client setup.
The second a server setup.

But in some cases i need to include the client setup package inside my serversetup.
But when i use the (un)Install msi package command, the setup does not wait until that packes has completed installing.

I've look at this forum an found this topic:
http://www.installaware.com/forum/viewtopic.php?f=2&t=5652

Reading it, and also reading the tutorial did not came with an solution.

What am I doing wrong?
It is really necessary that the server setup waits until the client setup has finished!

this is the code I use, as you can see I've created some extra commandlines.
The variable $MOSOSSETUPPATH$ is already ser by the user. (eg: C:\Program Files\Mosos)

Code: Select all

Set Variable MOSOSSETUPRESULT to
Set Variable MOSOSETUPERROR to
Install/Remove MSI Package $TARGETDIR$\MososMenu\Setup\MososSetup.msi[ADDLOCAL=ALL CMDLINE="REBOOTOPTION=POSTPONE PATH=$MOSOSSETUPPATH$ /s"] (get result into variable MOSOSSETUPRESULT)
Apply Install


~InstallAware Clipboard Data~
~(Un)Install MSI Setup~
~{A38E92B1-9901-4EC8-9124-E232F7867963}~
~"ADDLOCAL=ALL CMDLINE=""REBOOTOPTION=POSTPONE PATH=$MOSOSSETUPPATH$ /s""",FALSE,,TRUE,$TARGETDIR$\MososMenu\Setup\MososSetup.msi,,MOSOSSETUPRESULT,MOSOSETUPERROR,TRUE~
~mMSI.dll\mMSIExec.dll~




[FrancescoT]

Dear Ton,

For what I know the "Install/Remove MSI Package" never returns before the MSI execution has been completed.
So it is very strange!

Are you sure that script code execution continues without waiting "Install/Remove MSI Package" ternination?

Regards

[Ton_B]

Yes, Then you get a situation in where you can see two setup progress windows.

[FrancescoT]

Dear Ton,

is it possible to have your MSI package that you are using?
I would like to test it.

Regards

[Ton_B]

Hello Fransesco,

Al thought I would like to do that, I don't think my boss will be very happy about me doing that,

I can however, remove all of the files to be installed and give you an "empty" setup.
or replace all of the files with dummy files.

On the other hand,
I have come up with an other solution, just using the run program function.
This function does wait until the setup has completed.

One difference however, The (un)install function requires an MSI, and the Run program an exe.
The difference between them is, that I had to convert the IA setup .exe with the Group policy wizard, to create an msi.
Don't know if that is why it does not work ?

[FrancescoT]

Dear Ton,

an msi package created with Group policy wizard, should works exactly as your setup exe works.

Then, you said:

Yes, Then you get a situation in where you can see two setup progress windows.

Just to clarify, you're saying that you have two setup processes that runs independently from each other, is it correct?

Regards

[Ton_B]

you're saying that you have two setup processes that runs independently from each other, is it correct?

Yes that is correct.

[FrancescoT]

Dear Ton,

a dummy project that replicate the issue would be perfect to test.

Regards

[Ton_B]

Hello Fransesco,

How can I sent it to you?
I've contacted my boss, regarding this issue, and he asked me if I could "fix" this within a minimum amount of time.
So I will replace all of our components with dummy files, but my boss asked me not to post this public.

Can I send it to you begin next week ?

Thanx

Ton.

[FrancescoT]

Dear Ton,

sure you can!

You can send your file to: support@installaware.com

Regards

[keefie]

I see exactly the same behavior in InstallAware 10 and InstallAware 2012. Has this issue been resolved for the case described above?

[FrancescoT]

Dear Keefie,

From the user that started the topic I haven't received any file yet.

If you want I can have a look at your case, just send me a sample project that replicate the issue or if you prefer, the MSI file that you're trying to use.

You can send your file to: support@installaware.com.

Regards

[keefie]

Hmmm. I seem to have got myself in a bit of a mess, posting the same info in two threads

"I suspect the async problem maybe related to the size of the msi installer being invoked by the plugin. The problem is not so obvious with our smaller installer, the problem is with the 250+MB installer which obviously cannot be sent via email.

As I see the same problem via both direct invocation of msiexec.exe and using the plugin this async behavior maybe directly related to the underlying msiexec.exe rather than the plugin itself."

[FrancescoT]

Dear Keefie,

Honestly, I haven't tested your MSI but I do not think that the problem could be related to msiexec ... but very probably to the MSI itself.

Anyway I am just supposing ... without having the file it is not so easy to find out what's going on.

By the way, I can assure you that I am used to call to exeternal MSI package from my script very often.

Just a question, have you personally developed the MSI package? Which tool have you used?

If you are able to find a way to give me acces to this file, I will be happy to test ... let me see if I'm able to give you an FTP access.

Regards

[keefie]

The msi package is created using the Group Policy Wizard in InstallAware on an installer created using InstallAware. Everything from start to finish is InstallAware.