Re: ActiveX component can't create object: 'dmcScripting.Converter'
[QUOTE=mville;177664]Could it be a permissions issue i.e. user does not have FULL administrator privileges?[/QUOTE]
i am local administrator on both systems.
[QUOTE=Jailhouse;177658]ActiveX has in the past been used as an exploit by malware writers. I wonder if it's being blocked for security reasons. I would check Windows and/or antivirus settings.[/QUOTE]
Antivirus is disabled.
If ActiveX is blocked for security reasons. Were would I check Windows settings for that.
I would not think windows is capable of blocking individual ActiveX object.
It does not block other objects from being created, the objects bellow are working just fine.
Scripting.Dictionary
Scripting.FileSystemObject
WScript.Shell
Re: ActiveX component can't create object: 'dmcScripting.Converter'
In our company we have seen problems with some ActiveX components (registration) in dependency if you install the ActiveX component as 'admin' or 'administrator'.
Dat Ei
Re: ActiveX component can't create object: 'dmcScripting.Converter'
Take a look at this [URL="https://stackoverflow.com/questions/2429477/cannot-use-createobject-from-vb-scripts-on-windows-7-x64"]Stack Overflow thread[/URL].
Re: ActiveX component can't create object: 'dmcScripting.Converter'
[QUOTE=Jailhouse;177672]Take a look at this [URL="https://stackoverflow.com/questions/2429477/cannot-use-createobject-from-vb-scripts-on-windows-7-x64"]Stack Overflow thread[/URL].[/QUOTE]
Thanks a lot for this pointer.
turned out that both syswow64\wscript.exe and system32\wscript.exe are 32-bit engines on my system. they both about 138kB
when i explicitly call them
>>syswow64\wscript.exe tester.vbs
or
>>system32\wscript.exe tester.vbs
in the task manager they show up as *32 process - so they are both 32-bit
I searched and found wscript.exe about 165kB elsewhere. so that is 64-bit version.
and when i call that explicitly
>>blah\wscript.exe tester.vbs
it shows up w-o *32 - 64 bit process
and then it works.
so dMCScripting.dll from 16.2 release that is being called when 'dmcScripting.Converter' gets created is obviously 64-bit.
and needs 64-bit wscript.exe engine to be recognized.
So I am good now. it works.
thanks
Re: ActiveX component can't create object: 'dmcScripting.Converter'
If you were double clicking the .vbs file, how was it running the 32 bit version of wscript?
Re: ActiveX component can't create object: 'dmcScripting.Converter'
[QUOTE=aabra1;177676]turned out that both syswow64\wscript.exe and system32\wscript.exe are 32-bit engines on my system. they both about 138kB
when i explicitly call them
>>syswow64\wscript.exe tester.vbs
or
>>system32\wscript.exe tester.vbs
in the task manager they show up as *32 process - so they are both 32-bit
I searched and found wscript.exe about 165kB elsewhere. so that is 64-bit version.[/QUOTE]
To help other windows 7 64-bit users, can you post exactly where the 64-bit wscript.exe resides?