Hi All,
I'm trying to insert the following script as a custom action in INSTALLSHIELD 9.0, but the installer is throwing 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.

Dim OShell
strComputer = "."
Set OShell = CreateObject("WScript.Shell")
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colProcessList = objWMIService.ExecQuery _
("Select * from Win32_Process Where Name = 'dllhost.exe'")
For Each objProcess in colProcessList
OShell.Run "net stop Comsysapp",0,1
OShell.Run "net start Comsysapp",0,1

I think there is some format that needs to be followed for writting scripts in INSTALLSHIELD, plz let me know where to find the infor regarding the formats.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


does the script work as a standalone before inserting it into the package ?
in installshield you have an option to insert vbscripts in the custom action wizard.
when do you want the script to run ? before instalfinalise or at a perticular location.
Answered 04/28/2005 by: bheers
Second Degree Blue Belt

Please log in to comment
I have included it as a vbscipt inside custom action, it does work well as a standalone. There is some format that installshield vbscript follows, my code is a combination of vbscript and wmi. Is that a problem.....

Answered 04/28/2005 by: manikanta
Yellow Belt

Please log in to comment
You did add this as a vbscript custom action, right? And not an Installshield Script custom action?

If so, what is the target OS? Some OS's don't ship with WMI, so you'll have to download it and install it.

Aldo, if you do a verbose log file of your install, it should tell you which line of your vbscript code is causing an error, this is very handy for debugging.

Hope that helps.


Answered 04/28/2005 by: plangton
Second Degree Blue Belt

Please log in to comment
Yeah, if a script is failing it should be reported in the Application Event Log.
Answered 05/03/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment