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
- :
- Error 1720 in 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
‎Jun 17, 2013
06:46 PM
Error 1720 in custom action
I'm trying to use a VBScript custom action to alter the [INSTALLDIR] property.
I've got the script set to run 'After Initialization (before first dialog)'.
Even when I have the script with just 'MsgBox "Script is running"', I get the following error:
Error 1720. There is a problem with this Windows
Installer package. A script required for this install to
complete count not be run. Contact your support
personnel or package vendor. Custom action
NewCustomAction1 script error -2146827256, Micros...
Help!
I've got the script set to run 'After Initialization (before first dialog)'.
Even when I have the script with just 'MsgBox "Script is running"', I get the following error:
Error 1720. There is a problem with this Windows
Installer package. A script required for this install to
complete count not be run. Contact your support
personnel or package vendor. Custom action
NewCustomAction1 script error -2146827256, Micros...
Help!
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 17, 2013
07:03 PM
The problem was that I created the .vbs file in Visual Studio which uses UTF-8 for the encoding by default.
VBS DOES NOT LIKE THAT!
It worked fine when I changed the encoding to US-ASCII - Codepage 20127 in the Advanced Save Options for the .vbs file.
Would have been nice to have that noted in the documentation on VB Script custom actions!
VBS DOES NOT LIKE THAT!
It worked fine when I changed the encoding to US-ASCII - Codepage 20127 in the Advanced Save Options for the .vbs file.
Would have been nice to have that noted in the documentation on VB Script custom actions!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 24, 2013
03:09 AM
Hello,
Thank you for the valuable feedback.
We would be glad to include of the documentation on VB Script custom actions in respective kb articles in future updates.
Thanks
Chiranjeevi
Thank you for the valuable feedback.
We would be glad to include of the documentation on VB Script custom actions in respective kb articles in future updates.
Thanks
Chiranjeevi