Vg 7 Com Interface Not Working

[timwoolley]

I have tried everything to get the com interface to work with VG 7.

 

I have a VB.NET 2003 project I previously used with VG 5 and 6. I got VG 7 and so I changed the

 

Dim vg = CreateObject("VoiceGuide.CommandLink") to Dim vg = CreateObject("vgServices.CommandLink")

 

one would think this would work, one woud be wrong. I keep getting the Cannot Create Active X Control error. I tries to reference the vgServices.dll file but it tells me it is not a valid dll..

 

I am in a really bad spot here and under a real time crunch. Any help will be appreciated.

 

 

 

[SupportTeam]

Please post the vgEngine trace showing system startup and attempted connection form your app.

 

We can then see which version of VG v7 you are using and if there are any errors listed in the vgEngine trace.

 

Can you post the app itself?

[timwoolley]

Please post the vgEngine trace showing system startup and attempted connection form your app.

 

We can then see which version of VG v7 you are using and if there are any errors listed in the vgEngine trace.

 

Can you post the app itself?

 

 

Attached is the log and a VERY simple vb application

0220_1642_vgEngine.zip

vg7test.zip

[SupportTeam]

I think the problem would be in your VB.NET code itself, we modified it a little bit to make it look like this:

 

 

Module Module1

 

Sub Main()

Dim vg As Object

vg = CreateObject("vgServices.CommandLink")

vg.Admin_TraceLogAdd(0, 0, "This trace was printed from an external VB Script")

vg = Nothing

End Sub

 

End Module

 

and compiled it and it ran fine. The changed lines are in bold.

 

Also, you do not need to include a reference to the vgServices.dll file. The code does 'late binding' by specifying the "vgServices.CommandLink" COM interface by name, so there is no need to reference the vgServices.dll in the VB.NET project.

 

Does the VBScript sample, that you included in your uploaded source code work OK on your system? If the VBScript sample works then all other programs would be able to access the COM interface as well. If the VBScript does not work then there would be something wrong with the VG v7 install and you'll need to re-install VG v7 again.

 

Here is the trace from our test system showing the .exe we compiled working and adding trace lines to vgEngine trace. I just ran the compiled .exe a few times.

 

 

121847.798 1 ------------------------------------------------------------------------------------------------------

121847.798 1 vgEngine Startup completed

121847.798 1 ------------------------------------------------------------------------------------------------------

121849.626 10 3 timer fired EV_TIMEOUT_AFTERIDLE_ALLOWOUT

121849.626 10 7 timer fired EV_TIMEOUT_AFTERIDLE_ALLOWOUT

121849.626 10 10 timer fired EV_TIMEOUT_AFTERIDLE_ALLOWOUT

121849.626 10 13 timer fired EV_TIMEOUT_AFTERIDLE_ALLOWOUT

121855.251 14 remoting link constructor activated: vgServices_CommandLink

121855.266 14 0 comlg This trace was printed from an external VB Script

121856.876 14 remoting link constructor activated: vgServices_CommandLink

121856.876 14 0 comlg This trace was printed from an external VB Script

121857.751 14 remoting link constructor activated: vgServices_CommandLink

121857.751 14 0 comlg This trace was printed from an external VB Script

121858.454 14 remoting link constructor activated: vgServices_CommandLink

121858.454 14 0 comlg This trace was printed from an external VB Script

121859.079 14 remoting link constructor activated: vgServices_CommandLink

121859.079 14 0 comlg This trace was printed from an external VB Script

121859.610 14 remoting link constructor activated: vgServices_CommandLink

121859.610 14 0 comlg This trace was printed from an external VB Script

 

I also attach the altered project, but it is built in VS2005, not VS2003, so you may not be able to open it.

vg7test.zip

[timwoolley]

Thanks for helping me here. It seems that when I opened the same project in VB.net 2005 it worked fine.... No clue why. But it works.