1 reply to this topic

[harts]

My installation runs a VB executable at the end of the install after the product has been registered. The custom action needs to remove a different installation (using msiexec -x) and install another program by running its own .msi file.
When I run my VB exe as a stand alone program it works perfectly but when I run it from within the installation program, it errors with -2147467259 and -2147221504 errors. I presume this is because another instance of the Windows Installer is already running.
My custom program has to work out if the nested uninstall and re-install are required and determine from which server it must run the MSI script, so I am not able to simply have a custom action which runs the MSI file. Any ideas of how I can do this?

[Stefan Krueger]

Put the custom action the the UI sequence.