This can be related to how you are running your script.
If you are on 64bit machine, by default your script will run with the 64 bit version of wscript.exe. But QC is a 32 bit app, so you need to consume it from a 32 bit version of wscript.exe which is located at c:\Windows\SysWOW64\wscript.exe.
use command line to run the script with c:\Windows\SysWOW64\wscript.exe and it should work.
You might want to check you have the necessary reference selected. I extract tests from QC to Excel OK. See attached for the references which can be accessed from the VBA code window by selecting Tools > Referneces.
Dim objQCConnection 'Return the TDConnection object 'Set objQCConnection = New TDApioleLib.TDConnection 'Set objQCConnection = New TDConnection Set objQCConnection = CreateObject("TDApiOle80.TDConnection")
C:\WINDOWS\SysWOW64>cscript.exe ".... .vbs" workaround works if it's a simple standalone Vbscript. We have a problem because we have a small front-end ASP/HTML app that uses pure VBScript to connect to our instance of ALM. Now that the server hosting this app is 64-bit and we're getting Active X cant createobject on the statement Set tdc = CreateObject("TDApiOle80.TDConnection") , is there any solution for this situation when VBscript is embedded in ASP?