# Running a VBScript action using CScript.exe
**URL:** https://www.finalbuilder.com/forums/t/running-a-vbscript-action-using-cscript-exe/2311
**Category:** Discussion
**Created:** [September 29, 2014, 12:37pm UTC](https://www.finalbuilder.com/forums/t/running-a-vbscript-action-using-cscript-exe/2311 "2014-09-29T12:37:37Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@lcoursey](https://www.finalbuilder.com/forums/u/lcoursey)
#### Post date: [September 29, 2014, 12:37pm UTC](https://www.finalbuilder.com/forums/t/running-a-vbscript-action-using-cscript-exe/2311/1 "2014-09-29T12:37:37Z")
We’re running some VBScript actions in FinalBuilder to build installers with InstallShield on a 64bit machine, but because the InstallShield automation process is 32bit only, the script needs to be run using a 32bit process (such as CScript.exe), else we run into errors.
(see [this info page](http://helpnet.flexerasoftware.com/installshield21helplib/helplibrary/AutomationInterface64Bit.htm#automatingbuildprocesses_1555737627_1031239))
Is there a way to make FinalBuilder run script actions using CScript.exe? I want to avoid having to run CScript using ‘execute program’ and a path to separate script file.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [September 29, 2014, 1:34am UTC](https://www.finalbuilder.com/forums/t/running-a-vbscript-action-using-cscript-exe/2311/2 "2014-09-29T01:34:39Z")
Hi Luke
FinalBuilder is still a 32bit process. In fact, compatibility with scripting is one of the main reasons we have not yet moved to 64bit. Did you try the Run Script action?
The only way to invoke CScript is via the execute program action with an external script file.
---
### Author:  [@lcoursey](https://www.finalbuilder.com/forums/u/lcoursey)
#### Post date: [September 29, 2014, 3:22am UTC](https://www.finalbuilder.com/forums/t/running-a-vbscript-action-using-cscript-exe/2311/3 "2014-09-29T03:22:53Z")
Hi Vincent,
Yes the ‘run script’ action is the one I’m using. I get this error at the script stage whenever I try to run the FB project on a 64bit machine:
Error Executing script : OnExecute
Microsoft VBScript runtime error
ActiveX component can’t create object: 'ISWiAuto16.ISWiProject\
Works fine on a 32bit machine. Example script below:
strPathToLocalIsm = [TEMP] & “” & [ISM\_Name]
Set oISM = CreateObject(“ISWiAuto16.ISWiProject”)
oISM.OpenProject strPathToLocalIsm , False
sFilePathAndName = [TEMP] & “\Exported\_from\_ISM.txt”
oISM.ExportStrings sFilePathAndName, 0, 1033
oISM.CloseProject
The issue I believe is with the InstallShield automation interface as described in that link in my previous post. Not sure if there’s a way around it at this point other than using execute program action, so just fishing for ideas really.
Regards,
---
### Author:  [@nevar](https://www.finalbuilder.com/forums/u/nevar)
#### Post date: [September 30, 2014, 1:22am UTC](https://www.finalbuilder.com/forums/t/running-a-vbscript-action-using-cscript-exe/2311/4 "2014-09-30T01:22:16Z")
Hi Luke,
A thought I had while looking into this. Possibly try to register the Install Shield dll in question using “C:\Windows\System32\regsrv32.exe” on the 64 bit machine. Everything I have read points to the dll simply not being registered in the correct namespace.
---
### Author:  [@lcoursey](https://www.finalbuilder.com/forums/u/lcoursey)
#### Post date: [September 30, 2014, 12:32pm UTC](https://www.finalbuilder.com/forums/t/running-a-vbscript-action-using-cscript-exe/2311/5 "2014-09-30T12:32:59Z")
Jason - thanks for the tip. The dll in question was actually missing (not sure why) so I copied it over from the installation on our old server machine and registered it, working now!