cmcma Report post Posted 07/19/2004 05:37 PM Getting this run time error a couple of times a day causing downtime. Please advise as to what is causing this. Attached is the vgm log in case that you need it. Thanks, Cary 0719vgm.txt Share this post Link to post
SupportTeam Report post Posted 07/20/2004 08:30 AM I take it that the trace stops when the error occurred? Which version of VoiceGuide are you using? Share this post Link to post
cmcma Report post Posted 07/20/2004 01:44 PM Version 5.2.2000 Professional, VG Dialer, Single line Share this post Link to post
Guest cary Report post Posted 07/20/2004 10:42 PM yes the trace stops but here is the screen shot of another one. runtime.doc Share this post Link to post
SupportTeam Report post Posted 07/21/2004 12:57 AM Could you please try with v5.2.3 and confirm if this error still occurs in this version.Download from here:[old link removed] Share this post Link to post
Guest Guest_cmcma Report post Posted 07/27/2004 10:31 PM Upgraded and it started doing it again today. Share this post Link to post
cmcma Report post Posted 07/27/2004 11:28 PM Here is the log 0727vgm.txt Share this post Link to post
SupportTeam Report post Posted 07/28/2004 01:02 PM We can see in trace that the last line shows that a new dial entry was found and was about to be dialed: 102147.20 1 dial found entry: tel[17136626218] ann[NONE] vgs[C:\Program Files\VoiceGuide\Scripts\CallMe\CallMe.vgs] am[C:\Program Files\VoiceGuide\Scripts\CallMe\CallMe.vgs] I assume that the trace .zip'd just after this "Run-time Error '70'" occurred on your system? 'Error 70' usually means 'Permission Denied', this could be happening because some other process has locked the OutDial database for exclusive use, or has locked one of the output files (eg: OutDial_Dialed.txt) preventing VoiceGuide from writing into it. Attached .exe will ignore such errors - please update your v5.2.3 installation with attached .exe VgMulti_5.2.3022.zip Share this post Link to post
cmcma Report post Posted 07/28/2004 05:54 PM Is VG unable to write entries into the log when this occurs? So far so good on the update. Share this post Link to post
SupportTeam Report post Posted 07/28/2004 09:27 PM If the output file is exclusively locked by another process then VG would not be able to write to it - the operating system prevents it from doing so. If you have written some external program which continually checks contents of OutDial_Dialed.txt then I'd recommend you try copying OutDial_Dialed.txt to your own temporary file and then open and check contents that temp file instead - that should allow VG to write to OutDial_Dialed.txt file at any time... Share this post Link to post