Script Is Not Loading

[Egor]

Version 6.0.3243 of VoiceGuide is installed. Unfortunately, scripts can not be loaded for some reason (see attachement). I tried not only my own script, but VoicceGuide scripts also. I reinstalled the program, error still appear. Do you have any suggestions?

[SupportTeam]

What is the error you are seeing?

 

Just tried with latest Script Designer released (v6.0.3003) and we could open the demo script files fine.

[Egor]

On the main screen if you choose View/Line Device Config, "No Script Specified" is appear and program does not allow to load any scripts.

[SupportTeam]

Looks like the script specified for VoiceGuide to use does not exist or could not be loaded.

 

Could you please post a copy of VoiceGuide's Trace Logs which captures the VG startup, this will allow us to see what is happening.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

Then restart VG.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces and the VoiceGuide script used.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[Egor]

Log file is 1230vgm_1_.zip and screen shot of the main screen with the "No Script Specified" is Script_Problem_1_.pdf. First part of log file dispalys log, when rotary switch on Dialogic Card was '2'. The second part is when rotary switch was set to '1'. I used VoiceGuide script "Credit Card Payment.vgs"

Script_Problem_1_.pdf

1230vgm_1_.zip

[SupportTeam]

There seems to be an issue with the Dialogic drivers which return an error in one of the initialisation steps. As a result of this error the scripts are not loaded.

124300.03 0 init InitHardware() => [gc_start failed]

Are you waiting until after the Dialogic drivers have been fully started before starting VG?

 

Which version of Dialogic drivers are you using?

 

Could you please post a copy of VoiceGuide's "tw" Trace Log.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

ktTel=10

Then restart VG.

 

Trace files will be created in VG's \log\ subdirectory.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[Egor]

The problem was solved, by unistaling VoiceGuide (originally it was installed on server on drive D) and reinstalling it on drive C. It is appears to be that drive C is hardcoded in the config file, even if it recognize that program installed on different drive than drive C.

[SupportTeam]

We have some test machines here running VoiceGuide on "D:\" and we have clients who setup VoiceGuide on "D:\" and run it with no problems.

 

The error which we pointed out was being returned by the Dialogic drivers was responsible for scripts not being loaded in this case:

124300.03 0 init InitHardware() => [gc_start failed]

 

There are no hardcoded paths in application which limit VG to be installed on "C:\" drive.