On 12/14/2016 11:29 AM, Jason Marshall wrote:
On 13/12/2016 08:00, Yossi Zahn wrote:
AFAIK the windows scripting host does not require .net framework at all.
Do you get the same error when creating a text file containing the following
single line:
var fso = new ActiveXObject("Scripting.FileSystemObject");
and running it as such:
cscript /e:javascript path/to/file
I have created a text file test script in compliance with your instructions and
called 'cscript' by directly defining the script engine using the
'/e:javascript' parameter. The call and output are as follows, but it seems
that despite using the parameter, the same error arises as with the build:
Jason and Emma@JasonandEmma-PC ~
$ cscript /e:javascript scripttest.txt
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
C:\cygwin\home\Jason and Emma\scripttest.txt(1, 1) Microsoft JScript runtime
error: Automation server can't create object
I guess that this would imply an issue with my individual set-up, as it seems
that the use of the parameter that you and Thorsten have identified would work
in the majority of cases.
Would anybody know what may have prevented this from working?
http://stackoverflow.com/questions/25922368/activexobject-creation-error-automation-server-cant-create-object-on-windows
Note the comments for the question on the link. I have checked, and at least my
registry has this:
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{0D43FE01-F093-11CF-8940-00A0C9054228}\InprocServer32]
@="C:\\Windows\\SysWOW64\\scrrun.dll"
"ThreadingModel"="Both"
Checked with both 32-bit and 64-bit regedit (to make sure that path
substitution doesn't change values).
--
Best regards,
Mike Kaganski
_______________________________________________
LibreOffice mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
