sbensen Report post Posted 04/11/2005 08:43 PM Since upgrading to a newer version of VG (5.5.3072 Enterprise version) We have been having trouble with maintaining the line device configuation. Whenever the system has to be re-booted, we lose the line device configuations and get the message no script specified on our second device line. When we use the VG configuation wizzard, the correct path is visible there. We have to complete the wizzard, exit VG then re-launch to set the paths correctly again. Before upgrading this was never a problem. Is there a bug in this version? Or do you have any other suggestions on how to stop this from happening? Share this post Link to post
SupportTeam Report post Posted 04/11/2005 11:37 PM Please post the VG.INI file from your system. Share this post Link to post
sbensen Report post Posted 04/12/2005 02:28 PM The VG.ini file is attached. Steve Share this post Link to post
SupportTeam Report post Posted 04/12/2005 09:35 PM VG.INI did not get attached, can you please try posting it again? Share this post Link to post
sbensen Report post Posted 04/12/2005 09:40 PM Here is the VG.ini vg.ini Share this post Link to post
SupportTeam Report post Posted 04/12/2005 09:54 PM VG.INI shows the script paths defines as: [TapiDevice1] Name=Analog Line 1(dxxxB1C1) Script=C:\VoiceGuide\AAD\Scripts\ValidateAADOutbound.vgs [TapiDevice2] Name=Analog Line 2(dxxxB1C2) Script=J:\IVR\VoiceGuide\PreDiabetes\Scripts\IncomingInitCallValidateHRN.vgs [TapiDevice3] Name=Analog Line 3(dxxxB1C3) Script=J:\IVR\VoiceGuide\PreDiabetes\Scripts\TestAnsweringMachine.vgs [TapiDevice4] Name=Analog Line 4(dxxxB1C4) Script=C:\VoiceGuide\JonahTest\Scripts\TestScript.vgs I suspect that the network drive J is just not available immediately after the reboot. I'd try moving the script to a local C drive - that way you'll avoid all the problems associated with trying to run applications from drives not local on your machine. Share this post Link to post