Activex Component Can't Create Object: 'vgservices.comman

[SupportTeam]

Customer report when using v7.5 :

 

vbs files created in "Temp" folders (for debugging purposes, we utilize this option) fail with the following error if run separately (as WScript):

"ActiveX component can't create object: 'vgServices.CommandLink"

We found that the component (vgServices) does not seem to have been registered properly (RegEdit shows "vgServices.CommandLink" in the list but no associated CLSID), yet the VBScript modules run fine as parts of our VoiceGuide scripts.

Without debugging functionality, we will not be able to provide upgrade to our customers production environments.

 

Did I install/configure something wrong? The environment is Windows Server 2008 R2.

 

Thanks.

[SupportTeam]

Please open a command prompt (may need to be an 'Administrator Command Prompt')

 

Then change directory to the VoiceGuide \temp\ sub-directory and run this command line:

 

C:\Windows\SysWow64\WScript.exe vbs_x_y.vbs

 

Where vbs_x_y.vbs is the filename of the .vbs file which you wish to run.

 

Does that work?

 

VoiceGuide is 32-bit software (as Dialogic drivers are all 32 bit) and the vgServices.dll which implements 'vgServices.CommandLink' is a 32 bit .NET Assembly DLL. So any VBScripts should be ran by the 32 bit version of VBScript interpreters (wscript.exe / cscript.exe)

 

The 32 bit version of VBScript interpreters (wscript.exe / cscript.exe) are in Windows' \SysWow64\ sub-directory.

 

On 64 bit versions of Windows the VBScript interpreters (wscript.exe / cscript.exe) that are in Windows' \System32\ sub-directory are actually 64-bit software. When those 64-bit interpreters are used they will run the VBScript in 64-bit mode and then that VBScript will not be able to instantiate objects that are only registered as 32-bit versions.

 

 

Apparently you can force vbscripts to run with 32 bit interpreter by changing "System32" to "sysWOW64" in default value of Registry key "Computer\HKLM\SOFTWARE]\Classes\VBSFile\Shell\Open\Command", but we would not want to make such changes as part of the VoiceGuide install.

 

If you want to use these optional temporary files for debugging purposes then any changes to system commands etc would need to be made manually after installing VoiceGuide on the 64 bit system.

[iTime]

Oh, I was dumb: I learned that 32-bit one is under "SysWow64" long time ago, and flipped the concept in my brain one more time, and ended up using one in "system32" folder.

Thanks for the help again.

 

Now I can renew our license for VG 7.5