- Revenera Community
- :
- InstallShield
- :
- InstallShield Knowledge Base
- :
- Windows Installer Error 1721
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Windows Installer Error 1721
Windows Installer Error 1721
Summary
Information about windows installer errors.Symptoms
Error 1721 is a Windows error displayed in the following format:
There is a problem with this Windows Installer packager. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: [2]. location: [3], command: [4].
Error 1721 will not always display the Action: [2], location: [3], or command: [4] portions of the error message.
Cause
Resolution
Verify that all custom actions included within the InstallUI or InstallExecute sequence have been sequenced properly. (See Additional Information for ways to verify that actions are sequenced correctly.) You can get to the sequence by following these steps:
- Select the Sequences view.
- Find the sequence into which the custom action has been inserted. (This is usually the Installation sequence.)
- Check both the User Interface and Execute sequences for the custom action.
B. Custom Action is Trying Access a File
- Select the Custom Actions view.
- Click the custom action so it is highlighted.
- Right-click the custom action and choose Custom Action Wizard.
- The Custom Action Wizard launches. Follow the wizard instructions until the Action Type panel is displayed. If the Location field says "Installed with the Product", proceed to the next step. If not, go to the next Resolution. If there is no location field or if the "Installed with the Product" option is not available, go to the next Resolution.
- Continue to step through the Custom Action Wizard to the Additional Options panel. Verify that the In-Script Execution field is set to Deferred, Commit, or Deferred Execution in System Content. If so, then this is not the cause of the issue. If not, then change the In-Script Execution to one of these options.
C. A Condition on the Custom Action Cause it To Launch at the Wrong Time
- Select the Sequences view.
- Find the sequence into which the custom action has been inserted. (Normally it will be the Installation sequence.)
- Check both the User Interface and Execute sequences for the custom action.
- Once the custom action is found, click it and find the condition field in the property grid.
- Verify that the condition is valid and is resolving to the expecting value.
D. A setup that was downloaded has been corrupted.
If your installation contains a custom action that is installed with the product and is set to be invoked during uninstallation time, this error may occur while attempting to uninstall the product. A combination of the following custom action attributes cause this error message:
- Source Location: Installed with the Product
- Invoke: After Setup Progress Dialog
- Execute: During Uninstallation
This error occurs because the custom action is being invoked after the application it is trying to execute has been uninstalled. To avoid this error message, make sure to invoke the custom action Before System Changes. The custom action attributes should be set as follows:
- Source Location: Installed with the Product
- Invoke: Before System Changes
-
Execute: During Uninstallation
- Source Location: File Exists on Target Computer
- File Location: [WindowsFolder]
- File Name and Command Line: Notepad.exe
Additional Information
Sometimes a setup may be installed on the machine that can not be uninstalled because error 1721 occurs every time during the uninstallation. The cached MSI found in the \Installer folder can be modified with Orca so that the setup can be uninstalled.
Logging the installation can help narrow down which custom action is causing the error.
Note: This article applies to MSI-based installations.Error 1721 is documented in the Windows Installer Help Library topic Windows Installer Error Messages.
The Installed property is documented in the Windows Installer Help Library topic Installed Property.
Deferred custom actions are documented in the Windows Installer Help Library topic Deferred Execution Custom Actions.