This content has been marked as final. Show 5 replies
If you want to run a script using 32bit com components in a 64bit environment, you need to use the correct cscript.exe to run the script. Try using %WINDOWS%\SysWOW64\cscript.exe for backwards compatibility.
Also note, HFM versions 11.x have 64 bit libraries now.
thanks for the info.
We were using this code from a FDM script.
I don't know if I understood well, but do you mean to include this code in a wsf file and then run it by executing cscript from the fdm script?
That's one way of doing it.1 person found this helpful
You could also try enabling 32 bit in IIS:
1. Open a command prompt and navigate to %systemdrive%\Inetpub\AdminScripts.
2. Enter this command:cscript.exe adsutil.vbs get W3SVC/AppPools/Enable32BitAppOnWin64
3. If the command returns "false", run this command; setting it to "true":
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 "true"
4. Restart your computer.
The WSF file works (connect to the HFM application, etc..) but when we execute this wsf from fdm script using Shell object, then we get the same error as executing the code directly from the fdm script.
we need to run this script form FDM.
any work around?
regarding IIS, IIS 7 is already running in 32-bits for FDM to work.
forgot to say that the wsf script is running fine from CMD if we execute it with cscript on WINDOWS\System32,
if we use the WINDOWS\SysWoW64 fails because it cannot create the object.
If we execute both options from FDM Script, both fail.