REMOVE=feature1,feature2 will suninstall certain features. ... View more

Thanks that did the trick.:) ... View more

If you're using the standard support, and if the item you're running requires elevated privileges, and if setup.exe did not elevate (instead you see the UAC dialog after you click Install), then the problem is most likely that an underlying CreateProcess call failed because ShellExecute is necessary for elevation. ... View more

I have managed to find a solution to this problem after trawling the web. This is possibly not the best way to fix this but as no one has had any other suggestions. I moved the RemoveExistingProduct sequence to just before the costinitialize sequence. This seems to have fixed the above problem. ... View more

Below is an extract from the verbose log which runs the my app: Action start 09:14:11: RunHASPDriver. MSI (c) (E8:64) [09:14:14:878]: Note: 1: 1721 2: RunHASPDriver 3: C:\Program Files\HRH\Gravitas\Program\Remote Update\hinstall.exe 4: -i MSI (c) (E8:64) [09:14:21:753]: Product: Gravitas -- Error 1721.There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: RunHASPDriver, location: C:\Program Files\HRH\Gravitas\Program\Remote Update\hinstall.exe, command: -i Action ended 09:14:21: RunHASPDriver. Return value 3. Info 2896.Executing action RunHASPDriver failed. The custom action is set to run if the check box on the final screen is selected and the finish button is clicked. The in-script execution is immediate and the return processing is synchronous (check exit code). I have noticed that the vista UAC shield has disappeared from my setup.exe icon. All I wanted to do was compress the files to a cabinet so my CD image wouldn't be so big. Thanks in advance for any solutions. ... View more

mutchie wrote: I currently install a 3rd party tool which is then used in a custom action, at the moment this 3rd party tool stays installed, I was wondering if possible to remove the 3rd party tool once the custom action is completed? Any ideas how to do this or if it is possible? I am using installshield 2008 pro. Thanks in Advance Tracey Yes.. indeed it is possible.. you have following options. 1. if you call "3rd party" installer to install the application then you would need to find the Product code being used by 3rd party installer and call there setup.exe with PrductCode as an argument. 2. if you are using their binaries (DLL etc) then you could simply delete them using DeleteFile() function at the end of your installation (How.. this would depend on what type of installshield project you are using). HTH ... View more

Check your file table and see if the file size is displayed properly. It should not show 0 KB. If it does check whether you added the file from correct location. Some case due to long path the file will not be added during compile. try to build the install from a short location. ... View more

If the question is about how to convert a path to a UNC path, perhaps see www.installsite.org > InstallScript Samples > Network. ... View more

I have managed to fix the 1631 error I forgot to put the reg in the command line so my command line is now: reg add HKLM\system\currentcontrolset\services\gravitaswellmanager /v DependsOnService /t REG_MULTI_SZ /d WinHTTPAutoProxySvc "[SystemFolder]reg.exe" I still have the problem of the registry not being created please help ... View more

the user profile is set by setAllUsersProfile2K or SetAllUsersProfileNT, custom actions that run in the UI sequence. ... View more

Thanks that worked perfectly.:) ... View more

I managed to fix this problem. The component GUIDs were different from the previous versions. So updating these seems to have fixed the problem.:D ... View more

Directory-table properties always get a free backslash at the end, and there's no automatic way to prevent or remove it that I'm aware of. Common general practice seems to be to copy the directory property value into a Property-table property, and then use InstallScript's StrRemoveLastSlash or VBScript or something to remove the final backslash. ... View more

I have made some progress I have managed to stop the 1721 error the installer will run with no errors but the permissions are not added to the registry. Yet the same command line code done manually afterwards works perfectly? I have now a custom action which will launch setacl.exe (installed with product) Command line is: "[INSTALLDIR]setacl.exe" -on "HKLM\software\HRH" -ot reg -actn ace -ace "n:%COMPUTERNAME%\NT SERVICE\GravitasWellManager;p:full" Return processing is synchronous (ignores exit code) In script execution is Defered Execution in system context Install Exec sequence is after start services Condition not installed I have also attached the log that I get the custom action is called setgravitaswellmanagerpermission. ... View more

The existing product does contain InstallScript either because it is an InstallScript MSI project or because it contains at least one InstallScript custom action (other actions such as ISMsiServerStartup and OnMoving would otherwise not be present). The failure is occurring because the uninstall of the old package does not have sufficient privileges to successfully run the old InstallScript engine. This is one of the reasons the InstallScript engine architecture was changed starting with InstallShield 12, so that situations like this could be avoided and the engine would be more reliable. The cause of this behavior is the older InstallScript engine in the existing product, not the project that has been built in IS 2008. To be able to work around this issue, one of the following options could be used: - Manually remove the existing product through Add/Remove Programs. - Use the ShellExecute API (which can be done through an InstallScript custom action in IS 2008 with the LaunchApplication function) to launch the existing product uninstall elevated (on Vista/Server 2008 only) so that the InstallScript engine in the old product runs with sufficient privileges to complete successfully. - Mark the setup.exe in the project built with IS 2008 to require administrator privileges. Note that any of the above workarounds are only required for this particular upgrade. Once the old product built with IS 11.5 is gone, any new upgrades can be performed normally. ... View more