1 reply to this topic

[maverix]

Hi,
We need to install two applications from inside our Basic MSI script. We don't have control on these setups - we just have the setup files.

When we use custom action to launch these setups, at the end of the first setup error 1722 is thrown.

Clubbing both the setups inside one, and calling that application caused error 1607 to be thrown.

Launching the clubbed install application at the end of our install (using the 'Commit' action in the Custom Wizard) causes error 2762 - Internal Error.

Please note that installing the applications independent of the Basic-MSI script successfully installs the applications.

We are attempting this on Win2K and WinXP, using a project created by InstallShield DevStudio 9.x.

Any help will be greatly appreciated. Thanks in advance.

[Stefan Krueger]

1722: set the custom action to "ignore exit code" and try again.

1607: not sure what would be causing this. There are several different errors with that code. Is it a MSI error or an InstallShield error message? (can you post the text?)

2762: Commit actions must be inserted between InstallInitialize and InstallFinalize. You probably want an immediate action at the end of your install.