You've probably got an error in a script. You generally cannot run
scripts as if you were running them from the command prompt because the
command line run uses the Windows Script Host engine and MSI does not.
A typical error in a custom action is to call Wscript.Echo or
WScript.CreateObject or other WScript methods. 

 

Phil Wilson 

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chandra
mohan
Sent: Thursday, October 18, 2007 10:13 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to run wsf/vbscript files as Custom actions?

 

Hi All,

 

I am able to set all the IIS Settings via the IISExtension for Wix 3.0.
Now, I need to set a few more settings which the extension doesn't
provide and hence would like to invoke a WSF file called iis.wsf which
sets additional settings of the website. When I include the file as a
Binary and invoke it in a custom action, I get the below error: 

 

MSI (s) (14:DC) [19:00:54:212]: Product: MS.ESPS.WebApps.Marketplace --
Error 1721. There is a problem with this Windows Installer package. A
program required for this install to complete could not be run. Contact
your support personnel or package vendor. Action: UpdateIISSettings,
location: C:\winnt\Installer\MSI33AB.tmp, command: cmohan-dev
C:\Depots\ESPS\mls\private\Deployment\iis\EdComWeb-dev.xml

 

<CustomAction

            Id='UpdateIISSettings'

            BinaryKey=d.wsf'

            Execute='deferred'

            ExeCommand='param1 ComWeb-dev.xml'

            Return='check'/>

 

The binary files are defined as :

 

<!-- xml2iis files -->

            <Binary Id="setaccess.vbs"
SourceFile="$(var.IIS_DIR)\setaccess.vbs" />

            <Binary Id="a.vbs" SourceFile="$(var.IIS_DIR)\a.vbs" />

            <Binary Id="b.vbs" SourceFile="$(var.IIS_DIR)\b.vbs" />

            <Binary Id="v.vbs" SourceFile="$(var.IIS_DIR)\c.vbs" />

            <Binary Id="d.wsf" SourceFile="$(var.IIS_DIR)\d.wsf" />

 

In the similar lines, when I include a VBscript file, say
updateConfig.vbs, and include it in a customAction, it gives the same
error. If I change the VBScript to call a function then the sample
works, but I would like to run the script as if its run from command
prompt.

 

Any help on how to invoke the wsf and vbscript files would be highly
helpful. 

 

Thanks,

 

________________________________

Peek-a-boo FREE Tricks & Treats for You! Get 'em!
<http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to