Your CustomAction needs to be defined differently. Instead of ExeCommand, use VBScriptCall='' (value = blank to just run the script, or put the name of the VBScript function). ExeCommand attribute tries to execute an EXE, not run VBScript.
Also I'm pretty sure that deferred custom actions have to be scheduled between InstallInitialize and InstallFinalize, which would mean you need to schedule yours earlier or make it an immediate action. (As found in Deferred CA description, http://msdn2.microsoft.com/en-us/library/aa368268.aspx) Daryn. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of chandan Koushik Sent: Friday, November 23, 2007 12:03 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problems in running vbscript during install <snip> I am unable to ... call a vbscript file <Binary Id="vbscript" SourceFile="SetDirectoryPermissions.vbs"/> <CustomAction Id="SetAnonPerm" BinaryKey="vbscript" Execute="deferred" ExeCommand=""C:\fonts"" Return="check" /> <!--Installexecutesequence --> <Custom Action="SetAnonPerm" After="InstallFinalize">NOT Installed</Custom> ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
