Error Casuing Vg To Crash

[LTympanick]

Got the following error message with logging off. Doubt you can tell what's going on, I've turned logging on to 10 for now to see if I can capture more info. Here's hoping the additional logging doesn't prevent the error from showing up again, unless you can figure it out without it.

 

What's somewhat disconcerting is that VG for Dialogic 3320 crashed with this error. This is not good. I will die a lot younger if I have to worry about VG staying up & running when I'm not around. I'll respond to this post if I can reproduce the error with logging set to 10.

 

 

161735.42 2 comlg Successful connection to HotLineSystem database on server HOTLINE4

161847.56 2 comlg Successful connection to HotLineSystem database on server HOTLINE4

162102.16 4 comlg Successful connection to HotLineSystem database on server HOTLINE4

162103.41 2 ERROR 6.0.3320 PlaySoundStart line=480, -2147417848:Automation error

The object invoked has disconnected from its clients. :VoiceGuide

162103.42 2 ERROR 6.0.3320 in PrepareAndPlayWavAndTts Module ScriptRunsLib on line 1290, 13:Type mismatch

162104.20 2 comlg Successful connection to HotLineSystem database on server HOTLINE4

162124.53 2 comlg Successful connection to HotLineSystem database on server HOTLINE4

162141.06 2 ERROR 6.0.3320 PlaySoundStart line=480, -2147417848:Automation error

The object invoked has disconnected from its clients. :VoiceGuide

162141.72 2 comlg Successful connection to HotLineSystem database on server HOTLINE4

[SupportTeam]

Got the following error message with logging off.

By "logging off" do you mean when exiting VoiceGuide or exiting Windows or something else?

 

The log does not show the application crashing... It only shows that VoiceGuide could not play what it was being asked to play.

 

Did the application actaully crash or did the call just end (because VoiceGuide could not play a particular file)?

 

The log excerpt starts at 16:17:35 and the last message placed at 4 minutes later at 16:21:41 shows calls are still taken by the system and processed.

 

Did the application error you are referring to happened right after the "162103.42 2 ERROR 6.0.3320 in PrepareAndPlayWavAndTts Module ScriptRunsLib on line 1290, 13:Type mismatch" line in log?

 

There is a line in log placed there one second later (16:21:04) and following lines which shows the system is still functioning.

 

We'd need to see both the "vgm" and the ktTel's "tw" logs (with logging level set to 10) to see why the playing of the sound files had problems at some stage - maybe the play was attempted after the call was ended(?).

 

Can you post the script which you are using along with the "vgm" and "tw" logs?

[LTympanick]

By logging off I meant I had logging set to 0, so I realized the log I gave you didn't have much info in it.

 

This was VG for Dialogic v6.0.3320 and it actually did crash, i.e. went into the debugger for post mortem analysis.

 

I tracked down the problem further and it was due to playing back of a small wav file that basically had nothing in it.

 

Playing back that file is what I believe appeared to be the main thing that caused the system to crash.

 

The reason it still appeared to be running is that it took a few more cycles I guess before it would go belly up after the playback failed. Not sure why this happened, but that was the behavior.

 

The detailed error log is attached for one of the many crashes I experienced on a very busy system.

 

When the end of the day finally arrived and usage slowed down again, I upgraded to v3335 and the system has been working very well since. I did not get the sense that there was anything new in this regard between your unofficial version 3320 from wav to vox conversion issues post 21369 (couldn't figure out how to do a link). wav <--> vox conversion issues

But the latest version appears to have fixed the problem quite nicely.

0609vgm_saved.txt

[SupportTeam]

But the latest version appears to have fixed the problem quite nicely.

Maybe it was this bug fix in v6.0.3335 that resolved things:

 

FIX : Fixed bug which was causing errors if zero length .WAV fies were played.

[LTympanick]

Possibly.

 

v3220 specifically fixed a case where one would see a wav file converted to a 0 length vox file and would eventually cause vgmulti v3210 to crash. I was able to verify that v3220 fixed this specific case that v3210 was crashing & burning on.

 

In this current case however, I didn't have a 0 length wav file but one of 1k or so with only silence but even v3220 was crashing on this case.

 

When I saw the release notes, I wasn't sure if they were referring to the fix as implemented in v3220 (since it wasn't an official release, only one done especially for me), which didn't address this latest problem. However, v3335 eliminating 100% of the wav to vox file conversions which may have helped to address this once and for all.

 

My system has been running reliably ever since. Any issues I have now at least are not bringing down the entire system.

 

Thanks.