|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Failed to instantiate script engine 'VBScript': Invalid class string
I get this error every time I try to run a VBScript step on a particular machine.
I have the VBPro project running on several other machines with no issues, but on this one machine I get the above error. It is a Windows 7 x64 machine running VBPro 7.6. Even if I create a new project that does nothing but execute a single VBScript with nothing but comments in it, I get the error. Any ideas? |
#2
|
|||
|
|||
#3
|
|||
|
|||
Unfortunately none of those search results helped. I have a seemingly fine vbscript.dll and it is properly registered. Additionally, I am able to run VBScripts on the command-line via cscript without any issues. I am only seeing problems when trying to run them from within VBPro.
|
#4
|
|||
|
|||
What happens when you unzip and save the attached file, open a Command Prompt to the folder it was saved to, and run it like so:
C:\Windows\SysWOW64\cscript.exe test.vbs (which is similar to what Visual Build does to instantiate the script engine)? |
#5
|
|||
|
|||
When I run that command-line I get the same error from VBPro.
It looks like running cscript from C:\Windows\system32 it works, but not from C:\Windows\SysWOW64 |
#6
|
|||
|
|||
Did you try
regsvr32 %systemroot%\SysWow64\vbscript.dll from an elevated Command Prompt? http://answers.microsoft.com/en-us/w...e-520a04891073 |
#7
|
|||
|
|||
I did. It did not appear to fix it.
|
#8
|
|||
|
|||
You might try repairing Windows or formatting and reinstalling Windows. Beyond that, you would need to contact Microsoft (use test.vbs to demonstrate the problem).
|
|
|