Launch attached setup.exe - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

CaP
Posts: 14
Joined: Thu May 10, 2012 6:23 pm

Launch attached setup.exe

Hi again,

I have also read http://www.advancedinstaller.com/forums ... f=2&t=8835, but have not gained any further insight to what I want to know.

I have been asked to enable the user of my setup to install foreign products (for convenience, not as prerequisites).
Thus I have added two buttons that are intended to launch attached setup.exe files.
I have also setup two custom actions to launch attached files, asynchronously not waiting for any return-codes.
For testing purposes I have added a third button that simply launches cmd.exe (not attached).
The last one is the only feature that works.

When I execute the install and press the designated buttons, this is what happens:

[...]

Aktion 14:46:58: ForeignProductsDlg. Dialog created
MSI (c) (28:18) [14:46:59:482]: Doing action: Test_CMD
Aktion 14:46:59: Test_CMD.
Aktion gestartet um 14:46:59: Test_CMD.
MSI (c) (28:18) [14:46:59:482]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:18) [14:46:59:485]: Transforming table CustomAction.

MSI (c) (28:18) [14:46:59:488]: Transforming table CustomAction.

MSI (c) (28:18) [14:46:59:488]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:18) [14:46:59:488]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (28:18) [14:46:59:492]: Transforming table Binary.

MSI (c) (28:18) [14:46:59:494]: Transforming table Binary.

MSI (c) (28:18) [14:46:59:494]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (28:18) [14:47:02:442]: Doing action: setup_this.exe
Aktion 14:47:02: setup_this.exe
Aktion gestartet um 14:47:02: setup_this.exe
MSI (c) (28:18) [14:47:02:442]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:18) [14:47:02:446]: Transforming table CustomAction.

MSI (c) (28:18) [14:47:02:448]: Transforming table CustomAction.

MSI (c) (28:18) [14:47:02:448]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:18) [14:47:02:448]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (28:18) [14:47:02:452]: Transforming table Binary.

MSI (c) (28:18) [14:47:02:454]: Transforming table Binary.

MSI (c) (28:18) [14:47:02:454]: Note: 1: 2262 2: Binary 3: -2147287038

[...]

MSI (c) (28:18) [14:47:03:498]: Doing action: setup_that.exe
Aktion 14:47:03: setup_that.exe
Aktion gestartet um 14:47:03: setup_that.exe
MSI (c) (28:18) [14:47:03:498]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:18) [14:47:03:502]: Transforming table CustomAction.

MSI (c) (28:18) [14:47:03:504]: Transforming table CustomAction.

MSI (c) (28:18) [14:47:03:504]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:18) [14:47:03:505]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (28:18) [14:47:03:508]: Transforming table Binary.

MSI (c) (28:18) [14:47:03:510]: Transforming table Binary.

MSI (c) (28:18) [14:47:03:510]: Note: 1: 2262 2: Binary 3: -2147287038

Aktion 14:47:56: CancelDlg. Dialog created
Aktion beendet um 14:47:58: WelcomeDlg. R³ckgabewert 2.
MSI (c) (28:88) [14:47:58:072]: Doing action: UserExit
Aktion 14:47:58: UserExit.
Aktion gestartet um 14:47:58: UserExit.
MSI (c) (28:88) [14:47:58:072]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:88) [14:47:58:076]: Transforming table CustomAction.

MSI (c) (28:88) [14:47:58:078]: Transforming table CustomAction.

MSI (c) (28:88) [14:47:58:078]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (28:18) [14:47:58:095]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (28:18) [14:47:58:097]: Transforming table Binary.

MSI (c) (28:18) [14:47:58:098]: Transforming table Binary.

MSI (c) (28:18) [14:47:58:098]: Note: 1: 2262 2: Binary 3: -2147287038
Aktion 14:47:58: UserExit. Dialog created
Aktion beendet um 14:47:59: UserExit. R³ckgabewert 2.
Aktion beendet um 14:47:59: INSTALL. R³ckgabewert 2.
Aktion beendet um 14:47:04: setup_that.exe. R³ckgabewert 1631.
Aktion beendet um 14:47:05: Test_CMD. R³ckgabewert 0.
Aktion beendet um 14:47:43: setup_this.exe. R³ckgabewert 1631.

[...]

MSI (c) (28:88) [14:47:59:621]: Destroying RemoteAPI object.
MSI (c) (28:D8) [14:47:59:624]: Custom Action Manager thread ending.

[...]

================================================

I'm basically clueless as to what's going wrong.
Thanks for any help!
Regards,
CaP.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Launch attached setup.exe

Hello,

I'm not sure why you are encountering this behavior. Can you please tell us if your attached setup.exe files are MSI based?

Also, can you please send us your .AIP (project file) and a verbose log of the main installation to support at advancedinstaller dot com so we can investigate them? Please use the /L*V command in order to generate a verbose log.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
CaP
Posts: 14
Joined: Thu May 10, 2012 6:23 pm

Re: Launch attached setup.exe

Dear Daniel,

>>> Can you please tell us if your attached setup.exe files are MSI based?

Well, they might very well be. I don't know how to tell. Going to file-properties->details doesn't give any hints.
Both of them are public software available on the internet. First one the current JRE install, second one apache Tomcat installation.

I'll post the requested files ASAP.

Regards,
CaP.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Launch attached setup.exe

Hi,

There are two very important problems with the package. The first, the one that causes the custom action to fail launching, is that they require elevation, i.e. as you would launch the EXE with "Run as administrator" command. The easiest method to solve this problem is to require this from the begging, i.e. in the main package. Just go to Install Parameters page and tick the option "Run as administrator".

The second problem, also very important, is that you have set them to asynchronous execution, which is not good because all of them are MSI based packages, the EXE that contain them are just some wrappers that most likely provide additional features. Windows Installer does not allow multiple MSI packages to install at the same time, so the solution is to set them to synchronous execution, otherwise you will get conflicts during the install.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
CaP
Posts: 14
Joined: Thu May 10, 2012 6:23 pm

Re: Launch attached setup.exe

Thank you very much!
Your support is highly appreciated.

CaP.

Return to “Common Problems”