Software Deployment Question

Help with MSI 1720

04/28/2004 33204 views
Help with MSI (Microsoft Installer) 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. Custom action [2] script error [3], [4]: [5] Line [6], Column [7], [8]
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

The installer runs script custom actions directly and does not use the Windows Script Host. The WScript object cannot be used inside a script custom action because this object is provided by the Windows Script Host. Objects in the Windows Script Host object model can only be used in custom actions if Windows Script Host is installed on the computer by creating new instances of the object, with a call to CreateObject, and providing the ProgId of the object (for example "WScript.Shell"). Depending on the type of script custom action, access to some objects and methods of the Windows Script Host object model may be denied for security reasons.
If you see an error 1720 when you try to install Mobile Information Server (MIS) on Windows Server 2003, it is because MIS is not supported on Windows Server 2003. Microsoft recommends that you upgrade to Exchange 2003 which includes the functionality of MIS and it runs fine on Windows Server 2003.
Dealing with Web Interface 2.0? The solution found here is to remove and reinstall IIS.
Authoring your own MSI? An AppDeploy message thread about the error may be found here.
Answered 04/28/2004 by: AppDeploy.com
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ