Dear community. I need to be able to launch a setup.exe, which is installed from a MSI file. To sum up the problem: I have an MSI-file (created as a Basic-MSI project in InstallShield 2013), containing a setup.exe which deploys on the users computer. I need to launch this setup.exe after the MSI is done installing. It needs to happen automatically, and there is no UI avaliable (Either it is silent or with basic-UI) so binding an action to the Finish Button of the SetupCompleteSuccess dialogue is not an option. My guess is that this is somewhat possible with the use of a custom action, placed after the InstallFinalize-step in the exec-sequence. However, I have not succeded in getting this to work. I have, however managed to start NotePad, but not the setup.exe I am deploying myself. I can manually start the setup.exe after it has been deployed, so I know it works - I just can't get the installer to start it without any problems. Starting it before the InstallFinalize step, is unfortunately not an option either, since it will fail, due to multiple installation processes running. There are many more elegant ways to design this, than wrapping a setup.exe in a MSI, but unfortunately a Single MSI file containing the setup.exe is a hard requirement, so alternative solutions is unfortunately not an option. I have tried many things, but I have not gotten anything to work, so any help is much much appreciated. Best regards and thanks in advance C ... View more

Dear community. A Quick question: Making an application launch after finished installation is very easy, and there are several ways to accomplish it. However, it will (as it is now) always be launched with ADMINISTRATIVE rights (Like when you right click, and chose 'Run as Administrator'). I want it to start up with NORMAL rights - and I can't seem to find a way to do so. So therefore, dear community, do you know how to accomplish this? All the best ... View more

I have an interesting problem. Here is the long version - I have put the short version below: I have developed an application, which needs to be registered against another third party application during installation. I am developing the installation as a Basic MSI project. To solve the regiostration problem, I have created a custom action, which calls MyApplication.exe with /regserver. Since the exe I call is installed with the application, I have made the custom action's in-script execution 'Deferred in System Context'. It executes just before InstallFinalize. I cannot use any of the installshield build-in ways of registering assemblis, due to carious issue, which I won't trouble you with here - it is enough to state that I need to make it as a custom action. Besides deploying my files, my installation also includes several microsoft Merge modules (like Visual C++ 10.0 CRT etc.). Lastly, the MSI is part of a chained installation. The MSI is launced from a parent MSI. Now - to the problem itself. The Third party application, which I am registering against, is also using some of these Microsoft Merge Modules - but an older version of them. This means, that my installation wants to update the merge module, and therefore the restart manager pops up and wants to stop my thirdpart-applications service. If I chose to stop it, my installation fails, when I get to my custom action (the registration can't be made without the service. If I chose to just continiue, the installation completes just fine. On an XP however, I don't have the restart manager to detect that the file is in use, and therefore my installation just flat out fails. So - what to do? I have a few ideas, but I am in doubt what would be the smartest, and I hope you will be able to assist. I am thinking - if I in some way can postpone the custom action untill after a reboot, if I can detect that the merge modules will be in use (both with and without the restart manager). Bot how to accomplish that, I do not know. The short version, this is what I want: - Detect if any of the Merge Modules (or older versions), which I am about to install, are in use (without using the Restart manager, sicne I need to support Win XP) - If no, then just continiue, and do my registration at the end of the installation. - if yes, then schedule the registration to happen after a reboot, and put said reboot in the end of the installation (do note, that my MSI is part of a chain, and is therefore launched from a parent-msi) Any help to accomplishing this, is much appreciated Thanks in advance ... View more

Dear Flexera Short version: Is there direct support for minor and small upgrades for chained MSI installers in InstallShield 2012? If not – what are the exact steps I need to do, in order to get it working? The longer version: I have developed an installer, using the Chained MSI technology to componentize my installation. Installation and major upgrades works just fine, but it is another case when it comes to Small and Minor upgrades. For now, let’s focus on minor upgrades, since small upgrades are less relevant in my case. I get the following in my MSI log, whenever I try to do a minor upgrade. I have edited the version number of the main MSI and those of the chained MSI’s which has been edited. No product codes has been changed, as it should be when doing minor upgrades. However, after the installation, only the main MSI has been upgraded – no changes to the chained packages. In the MSI log, I can see the following: InstallShield 9:18:25: Skipping chained package Pkg1 installation because it is already installed InstallShield 9:18:25: Skipping chained package Pkg2 installation because it is already installed InstallShield 9:18:25: Skipping chained package Pkg3 installation because it is already installed InstallShield 9:18:25: Skipping chained package Pkg4 installation because it is already installed So, I start to google it, and I stumble upon this nicely written White Paper, concerning Chained MSI installations: http://www.danysoft.com/free/wp_is_UsingChainedMSIs.pdf There, it clearly states on page 6 in the bottom, that Small and Minor upgrades does not work by default. It does, however, mention a workaround, but not one I have had success with implementing. I can see from this post on (from the InstallShield 2010 forum), that the problem existed back then, and that there is an open Work-order# IOC-000079413 to implement this feature: http://community.flexerasoftware.com/archive/index.php?t-196335.html It does not seem, neither from the release-notes or my own experience with InstallShield 2012, that there is any support for it yet. When is this planned to become supported? Until then - what is the exact steps to get it to work right now? According to the previously mentioned White Paper, I should be able to get it to work, by adding 16 in the Options-column of the ISChainPackages. That I have tried, but it yielded a failed installation, with the following in the MSI-log: [FONT="Courier New"]MSI (s) (A8:88) [09:53:51:648]: Windows Installer reconfigured the product. Product Name: MyProductName. Product Version: 0.0.2.0. Product Language: 1033. Reconfiguration success or error status: 1638. MSI (s) (A8:88) [09:53:51:648]: MainEngineThread is returning 1638 Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.[/FONT] Do I need to pass some properties or install conditions to the chained packages in the release-view as well? Any help is much appreciated. Best regards Christian ... View more