I have a PRE-LAUNCH script which calls a vbs file located on the content share. But an error pops up when the machine has been disconnected from the network 'unable to load script...'. Although this error does not pop up when you put the SoftGrid client in "Work Offline" mode.

I don't want to use DOS commands to check the UNC path exists or copy the vbs locally because I don't want the DOS prompt popping up every launch, and it's possible the vbs will change on a regular basis.

Is there a work around to this error when a machine has been taken off the network? I was thinking of just using wscript.exe /B to suppress error output.

<HREF>wscript.exe \\%SFT_SOFTGRIDSERVER%\Example.vbs PRE_LAUNCH</HREF>

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Off the top of my head I don't think you can. How are you calling the scripts? Using <SCRIPTBODY> or <HREF>.
Answered 12/17/2007 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Using <HREF>
Answered 12/18/2007 by: supergrid
Yellow Belt

Please log in to comment
Yeah it looks like you are stuck with the DOS box because the <SCRIPTBODY> method doesn't take care of that either.
Answered 12/19/2007 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment