This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- VMWare and custom action
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 12, 2008
11:37 AM
VMWare and custom action
I've got an installer that works fine on regular machines. This installer calls a custom action executable on both install and uninstall that messes with the ODBC databases.
My problem is that the install/uninstall works fine on regular machines and vm's through remote desktop, but when I run in the vmware console the custom action fails with error 1721 on uninstall only. Does anyone know what could be different about the vmware console? Thanks.
My problem is that the install/uninstall works fine on regular machines and vm's through remote desktop, but when I run in the vmware console the custom action fails with error 1721 on uninstall only. Does anyone know what could be different about the vmware console? Thanks.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 13, 2008
12:03 PM
Error 1721 indicates an executable custom action failed to launch. Typically this is due to missing dependencies required for the executable to launch correctly. Does the EXE launch outside of the MSI package in the same environment where it is failing? If it still fails to launch even on its own, you may try using Dependency Walker to determine if there are any missing dependencies in that environment.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 13, 2008
01:58 PM
Sorry, I guess I forgot to say that before. The executable can be run outside of the installer in the command line but fails when it's called from the installer.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 15, 2008
01:59 PM
You may want to try using the SysInternals Process Monitor utility for further troubleshooting. For an EXE custom action, Windows Installer is launching the executable with the CreateProcess API, so I'm not really sure what the issue would be if the file launches in the same environment as a standalone file. Process Monitor may yield some addition information.