SupportTeam Report post Posted 02/22/2018 02:40 AM I have problem with start script from network disc.Disk V is mapped and connected (I can call script V:\manager_start.vgs from windows explorer and open in script designer)but VG not start this script.We have several servers and I want to have script library on network disk to update once and make available for everyone server.How to reach script from remote folder? 153137.590 10 14 4 201256 path {22} found (at offset 220) 153137.590 10 14 4 201256 FindNextVgmTitleInPathList: next module title is=[V:\manager_start.vgs|id_create] 153137.591 10 14 4 201256 script and module specified 153137.591 10 14 4 201256 NewVgsVgm_Goto_Setup dest=V:\manager_start.vgs|id_create, return=|, lSaveSourceOnCallStack=0 153137.591 10 14 4 201256 rv add ScriptEnd_Time|2018-02-21 15:31:37 153137.591 10 14 4 201256 rv add ScriptEnd_Goto_Script|V:\manager_start.vgs 153137.591 10 14 4 201256 rv add ScriptEnd_Goto_Module|id_create 153137.591 10 14 4 201256 WriteToLogFiles_CurrScriptOnly begin 153137.591 10 14 4 201256 WriteToLogFiles_QueWrite 153137.591 10 14 4 201256 rv add ScriptStart_Time|2018-02-21 15:31:37 153137.591 9 14 4 201256 WriteToLogFiles_DoWrite : LogNames=C:\Program Files (x86)\VoiceGuide\Scripts\manager\manager_main 153137.591 10 14 4 201256 rv add ScriptStart_CalledFrom_Script|C:\Program Files (x86)\VoiceGuide\Scripts\manager\manager_main.vgs 153137.591 9 14 4 201256 WriteToLogFiles_DoWrite : log subdirectory does not exist: C:\Program Files (x86)\VoiceGuide\Scripts\manager\log 153137.591 10 14 4 201256 rv add ScriptStart_CalledFrom_Module|set_calling_number 153137.591 9 14 4 201256 WriteToLogFiles_DoWrite completed 153137.591 10 14 4 201256 FindFullPathToScript_VgsOrVgp start [V:\manager_start.vgs] 153137.591 10 14 4 201256 WARN cannot find any of these scripts [V:\manager_start.vgs] or [V:\manager_start.vgp] or [C:\Program Files (x86)\VoiceGuide\Scripts\manager\manager_start.vgs] or [C:\Program Files (x86)\VoiceGuide\Scripts\manager\manager_start.vgp] 153137.591 10 14 4 201256 WARN NewVgsVgm_SetVgsVgm could not find [V:\manager_start.vgs] 153137.591 10 14 4 201256 state ERROR NewVgsVgm_SetVgsVgm could not find [V:\manager_start.vgs] 153137.591 10 14 4 201256 matching path not found [22], try boolean paths. 153137.591 10 14 4 201256 ex: ScriptIo.VGMTYPE_EVALEXPR [22] could not be converted to boolean. Take Success path as string non-empty. 153137.591 10 14 4 201256 FindNextVgmTitleInPathList: next module title is=[id_create] Share this post Link to post
SupportTeam Report post Posted 02/22/2018 02:55 AM A Windows Service should use “UNC paths“ to access network drives (ie: "\\ServerNameOrIP\Path")Windows Services should not use drive mappings. Drive mappings are user-specific shortcuts which are active only when the user that created those mappings is logged into Windows and the process is running under that user.VoiceGuide service runs under the LocalSystem account (by default). Windows Services running as NetworkService or LocalSystem use machine account credentials.In a Domain environment, you can grant access rights to computer/machine accounts; this applies to processes running on those computers as LocalSystem or NetworkService when they connect to remote systems.So if the server that is hosting the script files is part of same Domain as the VoiceGuide servers you can just give all the VoiceGuide servers permissions to access that directory.If the machines involved are not part of the same Domain then you may need to give 'Everybody' permission to read that directory. Another approach is to have a batch file/process that copies updated scripts/files to all the target systems. That way each VoiceGuide server has all the files it needs to function locally, and if there were any problems with a VoiceGuide server being reached over the network then you would be alerted of it immediately at file copy time. Share this post Link to post