I seem to have the same trouble;
"ActiveX component can't create object: homeseer2.application 800A01AD Microsoft VB script runtime error"
I'm on a Windows 7 64bit machine, is there any other way to register the homeseer2.dll so it becomes available in all contexts in the machine? I have turned UAC off to make these things go away, but it seems not related.
Edit;
Well, as so many times, just needed to talk to myself for a while and the solution becomes clear... It is a matter of getting the correct wscript to execute. If I point out the complete path to wscript to run my test.vbs "c:\windows\syswow64\wscript.exe test.vbs" it runs fine! Just starting the test.vbs seems to pull the "c:\windows\system32\wscript.exe" version instead.
Hope this helps!
"ActiveX component can't create object: homeseer2.application 800A01AD Microsoft VB script runtime error"
I'm on a Windows 7 64bit machine, is there any other way to register the homeseer2.dll so it becomes available in all contexts in the machine? I have turned UAC off to make these things go away, but it seems not related.
Edit;
Well, as so many times, just needed to talk to myself for a while and the solution becomes clear... It is a matter of getting the correct wscript to execute. If I point out the complete path to wscript to run my test.vbs "c:\windows\syswow64\wscript.exe test.vbs" it runs fine! Just starting the test.vbs seems to pull the "c:\windows\system32\wscript.exe" version instead.
Hope this helps!
Comment