Vb Script

[Guest ryan]

I have based a script on your demo script, and have found that with VG 4.9.0 the script fails at various points and occasionaly completes. The log file shows..

 

03500 6 Eval Expr result:[True]

03531 6 [send activation] Running VB Script...

05156 6 VBScript Run waiting...

06156 6 Terminating process (timeout reached).

06156 6 [Play 1] Playing

 

which has me concerend that VG is purposely terminating the VB Script due to a VG timeout. Can this timeout be changed?

 

Furthermore, the script is based on your demo script, but it fails in the initial code that is exactly what you have provided...

Dim IE, readWwwHtml, readWwwText

Dim SerialNumber, DeviceID

 

SerialNumber = $RV[Get Serial Number]

DeviceID = $RV[Get Device ID]

 

Set IE = CreateObject("InternetExplorer.Application")

 

CONST URL_TO_HIT = "http://www.trafficgauge.com/activation/ActivationForm.asp"

WriteResultFile("IE Created. Hitting URL: " & URL_TO_HIT)

With IE

.RegisterAsDropTarget = False

.Visible = False

.Silent = True

.Navigate(URL_TO_HIT)

While .Busy

WScript.Sleep 10

Wend

 

set coll = .Document.body.getElementsByTagName("INPUT")

...

 

We have instrumented this code with some debug logging and have found that at all different points of this script the execution fails - mostly in between the steps shown in the code snippet above. It is not a repeatable failure at a repeatable point of the script. Therefore, this further supports the idea that the VG timeout is prematurely terminating the script. Occasionaly, the script will complete, but most of the time it does not. The PC that this is running on is Windows XP Home, with IE 6.0 and Celereon 1.3GHz.

 

Please HELP!

[SupportTeam]

Looks like the VoiceGuide module from which the VB Script is ran has a timeout path of 1 second leaving from it....

 

That timeout is calculated from the time the script starts, so if your script takes sometimes longer then 1 second to complete then VoiceGuide's timeout will kick in and abort the VB Script....

 

Just change the timeout path in that module to be a bit longer (say 5 seconds...)

 

If you don't think that the timeout path is the problem please post a copy of the VoiceGuide script (just the .VGS file) here and I can see what it can be...

 

Are you using the latest version of VocieGuide ? (v4.9.0)