Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy do I get a 1720 error when my InstallShield setup tries to run my VBS custom action?
    text
    copied!<p>The Custom Action is configured as follows:</p> <blockquote> <p><strong>Custom Action Name</strong>: MyCustomAction</p> <p><strong>VBScript Filename</strong>: <code>&lt;PathVar01</code>>\MyFolder\MyVBSfile.vbs</p> <p><strong>ScriptFunction</strong>: MyFunction</p> <p><strong>Return Processing</strong>: Synchronous (Check exit code)</p> <p><strong>In-Script Execution</strong>: Immediate Execution</p> </blockquote> <p>It is being executed via the following InstallScript code:</p> <pre><code>result = MsiDoAction(ISMSI_HANDLE,"MyCustomAction"); </code></pre> <p>When the setup reaches that line in InstallScript, the installer shows an error alert, stating:</p> <blockquote> <p>"Error 1720.There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor."</p> </blockquote> <p>The result code returned by MsiDoAction is that of '1603', which, <a href="http://msdn.microsoft.com/en-us/library/ms819773.aspx" rel="nofollow noreferrer">according to winerror.h</a>, is:</p> <pre><code>// // MessageId: ERROR_INSTALL_FAILURE // // MessageText: // // Fatal error during installation. // #define ERROR_INSTALL_FAILURE 1603L </code></pre> <p>Why is this happening? I was starting to doubt that the file was included properly. Yet, I am pointing to the correct file, and I've tried including the VBS via the InstallShield Support Files, thinking this would ensure the file was present with the setup, but same result.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload