Errors In Communication

[Guest DiegoBellini]

The call is cut alone while the application is running. Thanks

Errores.zip

[SupportTeam]

To debug the VBScript while it is called from within VoiceGuide please place some calls to the Admin_TraceLogAdd COM function within the VBScript. You will then be able to identify on which line the error occurs by looking at which calls are adding log entries to vgEngine log and which do not.

[Guest DiegoBellini]

Traces show that the vb script:

 

To debug the vb script: []

143849.769 8 1 AfterHangup script not set.

143849.769 8 1 OnIDLE_CleanupAfterAllScritpsCompletedAndReleaseCall start

143849.769 8 1 WriteToLogFiles_CurrScriptOnly begin

143849.769 8 WriteToLogFiles_DoWrite begin : strLogFnameLessSuffix=C:\Program Files\VoiceGuide\Scripts\Roosevelt Roads\SelectFROMSavings

143849.769 8 WriteToLogFiles_DoWrite : log subdirectory does not exist: C:\Program Files\VoiceGuide\Scripts\Roosevelt Roads\log

143849.769 8 1 LineState_Reinit_AndReleaseCall: begin

143849.769 8 1 LineState_Reinit_CleanLineState : begin

143849.769 8 1 strThisCallIsInboundOrOutbound clear. (LineState_Reinit_CleanLineState)

143849.769 8 1 timer set 2 EV_TIMEOUT_AFTERIDLE_ALLOWOUT

[SupportTeam]

So using the Admin_TraceLogAdd COM functions were you able to establish to which line the VBScript in module [setVariables] gets to before it errors?

 

We would need to see the VoiceGuide script itself as well as the traces to be able to better comment on what is happening.

[Guest DiegoBellini]

So using the Admin_TraceLogAdd COM functions were you able to establish to which line the VBScript in module [setVariables] gets to before it errors?

 

We would need to see the VoiceGuide script itself as well as the traces to be able to better comment on what is happening.

I believe that they do not understand me. The script SetVariables does not have any problem since it he passes several times thereabouts and covers well other times. Please, see the script SetVariables, only set on variables. They sending the script VG

Script.zip

[SupportTeam]

Looking at trace it looks like a call to [setVariables] module at time 124055.812 never returns.

 

We see VoiceGuide waiting for it to return for about a minute.

 

We can see the RvSet DebitoCredito call, but not the RvSet TransactionDate or the Script_Goto call:

 

124055.968 17 1 cl RvSet DebitoCredito, Retiro

 

After RvSet DebitoCredito we see entries like this in the trace:

 

124202.531 4 1 timer fired EV_TIMEOUT_CHECKONSTATE

124202.531 4 1 ScriptEventCode EV_TIMEOUT_CHECKONSTATE, code=9007, state=1501

124202.531 4 1 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE lCode2Str=EV_TIMEOUT_CHECKONSTATE

124202.531 4 1 path {EV_TIMEOUT_CHECKONSTATE} not found

124202.531 4 1 Process.HasExited is false (awaiting COM function call from the started process) handle=5896, id=2984, StartTime=4/24/2008 12:40:55 PM

124202.531 4 1 .ExitTime returned error.

124202.531 4 1 process still running

 

If you think the problem is somewhere else then please explain in detail what is the problem that you are encountering.

[Guest DiegoBellini]

Looking at trace it looks like a call to [setVariables] module at time 124055.812 never returns.

 

We see VoiceGuide waiting for it to return for about a minute.

 

We can see the RvSet DebitoCredito call, but not the RvSet TransactionDate or the Script_Goto call:

 

124055.968 17 1 cl RvSet DebitoCredito, Retiro

 

After RvSet DebitoCredito we see entries like this in the trace:

 

124202.531 4 1 timer fired EV_TIMEOUT_CHECKONSTATE

124202.531 4 1 ScriptEventCode EV_TIMEOUT_CHECKONSTATE, code=9007, state=1501

124202.531 4 1 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE lCode2Str=EV_TIMEOUT_CHECKONSTATE

124202.531 4 1 path {EV_TIMEOUT_CHECKONSTATE} not found

124202.531 4 1 Process.HasExited is false (awaiting COM function call from the started process) handle=5896, id=2984, StartTime=4/24/2008 12:40:55 PM

124202.531 4 1 .ExitTime returned error.

124202.531 4 1 process still running

 

If you think the problem is somewhere else then please explain in detail what is the problem that you are encountering.

 

I don't understand the log file, and i have a new error again

 

What it say here?

032948.750 4 13 LsSayNbrPlay waiting for SayNumbers script. iRunWait=0, processHandle=7144, pid=3592)

032948.750 4 13 Process.HasExited is false (awaiting COM function call from the started process) handle=7144, id=3592, StartTime=25/04/2008 03:29:47 a.m.

032948.750 4 13 .ExitTime returned error.

032948.750 4 13 LsSayNbrPlay task still running (processHandle=7144)

 

I did not more to do

 

[SupportTeam]

This trace excerpt says that the Say Number module is waiting for the VBScript to finish. If you are seeing this trace excerpt repeated over and over this means that the VBScript is not completing.

 

Maybe there is something wrong with the VBScript interpreter on this machine.

 

What version of Windows are you using?

 

Maybe try restarting the system to see if this fixes the VBScript execution.

[Guest DiegoBellini]

This trace excerpt says that the Say Number module is waiting for the VBScript to finish. If you are seeing this trace excerpt repeated over and over this means that the VBScript is not completing.

 

Maybe there is something wrong with the VBScript interpreter on this machine.

 

What version of Windows are you using?

 

Maybe try restarting the system to see if this fixes the VBScript execution.

 

hmmm, it's very stranger. My windows is Windows XP Professional Service Pack 2 Spanish. Version 5.1.2600

It's existing any upgrade of the Windows script host?

You recommend to me some statements to close or to finish each VBscripts?

 

Thanks

Diego B.

[SupportTeam]

You could use the command

 

WScript.Quit

 

to explicitly end the VBScript interpreter, but usually the VBScripts complete properly without the need for this command.

 

It is strange that you are not seeing the VBScript (or the WScript interpreter?) exit properly sometimes. Can you reliably reproduce this situation, or is it random every time a Run VBScript (or Say Number) module is ran?

[Guest DiegoBellini]

You could use the command

 

WScript.Quit

 

to explicitly end the VBScript interpreter, but usually the VBScripts complete properly without the need for this command.

 

It is strange that you are not seeing the VBScript (or the WScript interpreter?) exit properly sometimes. Can yo reliably reproduce this situation, or is it random every time a Run VBScript (or Say Number) module is ran?

Sometimes it he finishes OK and sometimes not. Now it happens to me slightly newly. I installed the system in another application and it he runs perfectly, but in the new third server it he returns to trump another VBscript, which is different from the previous one. The only difference between these servers is that one has Windows in English and other one in spanish. All the VBscripts are programmed in a PC with Windows in spanish.

[SupportTeam]

Not sure what you mean by:

 

"but in the new third server it he returns to trump another VBscript, which is different from the previous one. "

 

Can you please explain in more detail what is happening.

[Guest DiegoBellini]

Not sure what you mean by:

 

"but in the new third server it he returns to trump another VBscript, which is different from the previous one. "

 

Can you please explain in more detail what is happening.

I have 3 servers in 3 differents clients.

The scripts installed in the clients are the same.

So, in the client A they fail some scripts that in the client B work well, and in the client B they fail some scripts that in the client A work well.

The scripts that fail are alone the Visual Basic scripts of the modules VBS.

Those of other VG modules work well.

[SupportTeam]

Can you reliably reproduce this VBScript problem, or is it random? How often do these problems occur?

[Guest DiegoBellini]

Can you reliably reproduce this VBScript problem, or is it random? How often do these problems occur?

It's no random, occurs always.

The problem is that the VBscript does not end.

I don't understand. This one is one of that fails. it' very simple.

I use it only for set the connection string to a RV Variable, to use in all Database query modules.

----------------------------------------------------------------------------------------

set vg = CreateObject("VoiceGuide.CommandLink")

SQLConnSTR = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=custmast_po_prueba;Data Source=server-po"

 

vg.RvSet $RV_LINEID,"SQLConnStr",SQLConnSTR

vg.RvSet $RV_LINEID,"DB",DB

 

vg.Script_Goto $RV_LINEID,"","GetCustID",""

Set vg = Nothing

----------------------------------------------------------------------------------------

 

When the system is running, this script not end, and after some seconds they hang up the call.

[SupportTeam]

Have you tried manually running the VBScript using the .VBS file which VG creates before running the script? See in VG's \data\ subdirectory. The .VBS file is created just before it is ran.

 

Double click on it to see if there are any error messages that Windows Scripting Host reports, and confirm the VBScript is completing properly when started manually like that.

 

If the script is finishing OK with no error messages then please provide the following information:

 

- Which version of Windows are you using.

- What are the system specs (CPU/Memory etc)

- Is anything apart from Dialogic drivers and VoiceGuide installed on this system.

 

Also please update to the latest version of VG v7.

 

If the problems still persists it may be good idea to let us have a quick look at the system. Please setup a login using www.logmein.com and forward login details along with a link to this thread to support@voiceguide.com

 

[SupportTeam]

Some Antivirus software (esp. Norton) may be responsible for creating such VBScript problems. If you have any Anti-virus software installed please uninstall it.

[Guest DiegoBellini]

Some Antivirus software3 (esp. Norton) may be responsible for creating such VBScript problems. If you have any Anti-virus software installed please uninstall it.

Not antivirus installed.

Look at this example,

This script is the second one that runs, (first there is a welcome, and then it he goes on to this VBscript).

The script never ends and the communication is cut abrupt.

 

It is impossible to give them the control of the server, my client is a bank and has a strict policy of safety. Sorry

Errors.zip

[SupportTeam]

The provided trace shows that the VBScript runs fine, but it does take a long time to start. After calling the two RvSet functions the script then exits.

VoiceGuide then hangs up as the script did not make any Run_ResultReturn or Script_Goto (or similar) calls.

You should add a Run_ResultReturn or Script_Goto (or similar) call to the script to make the VG script progress to next module.

 

It is puzzling why the VBScript takes so long to run. Does every VBScript take so long, or just the first one after system restart?

 

How fast is this machine and how much memory does it have? Which version of Windows do you use and is there anything else installed on this system apart for VG?

Ie. Is this a clean install of Windows with nothing else but Dialogic drivers and VoiceGuide or was anything else installed on this machine after Windows was installed?

 

 

 

143029.984 9 4 state [ConnectDB] type: VB Script, iRunWait=1

 

143033.390 15 4 cl RvSet SQLConnStr, Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CustMast_PO_Prueba;Data Source=SERVER-PO

143033.390 15 4 rv add [sqlConnStr]{Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CustMast_PO_Prueba;Data Source=SERVER-PO}

143033.703 15 4 cl RvSet DB, CustMast_PO_Prueba

[Guest DiegoBellini]

The provided trace shows that the VBScript runs fine, but it does take a long time to start. After calling the two RvSet functions the script then exits.

VoiceGuide then hangs up as the script did not make any Run_ResultReturn or Script_Goto (or similar) calls.

You should add a Run_ResultReturn or Script_Goto (or similar) call to the script to make the VG script progress to next module.

 

It is puzzling why the VBScript takes so long to run. Does every VBScript take so long, or just the first one after system restart?

 

How fast is this machine and how much memory does it have? Which version of Windows do you use and is there anything else installed on this system apart for VG?

Ie. Is this a clean install of Windows with nothing else but Dialogic drivers and VoiceGuide or was anything else installed on this machine after Windows was installed?

 

 

 

143029.984 9 4 state [ConnectDB] type: VB Script, iRunWait=1

 

143033.390 15 4 cl RvSet SQLConnStr, Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CustMast_PO_Prueba;Data Source=SERVER-PO

143033.390 15 4 rv add [sqlConnStr]{Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CustMast_PO_Prueba;Data Source=SERVER-PO}

143033.703 15 4 cl RvSet DB, CustMast_PO_Prueba

 

But the script have "on {success} goto [GetCustID]" in a path section? Is not this sufficient to indicate him to where continuing?

 

All the VBScript take so long to start or end.

The system is a powerful server with PIV 3.0GHZ, 800MHZ FSB, 2GB RAM DDR2 667, Win XP SP2

It's a clean installation only for Voiceguide and Dialogic.

[SupportTeam]

But the script have "on {success} goto [GetCustID]" in a path section? Is not this sufficient to indicate him to where continuing?

It is if the VBScript returns "Success". You must use Run_ResultReturn from the VBScript to return "Success".

 

It's very had to comment on the speed of VBScript execution without seeing the machine. We'd like to first run some test on it starting VBScripts from outside VG to see if this problems is Windows Scripting Host related or if it's something to do with VG. The we'd better know what to look at. We have not seen this happen on any of our test machines and we're keen to find out what is causing this.

Is there any way that you can give us access to this machine? Can you remove it temporarily from the bank premises and connect it up to www.logmein.com from another premises?