Fixed: Event- Variable does not work

Fixed: Event- Variable does not work

avatar

Hi There,
i try to start a event "before connection".
It worked without variables, but if i want to push a variable to the VBS Script i get an error.
The script:
c:\TEST.vbs $SESSION_ID$
When i start the rdp session i get the following error:
Unable to execute the script file [c:\TEST.vbs f6170165-7f6d-4ace-9010-4d806643d9da]
It looks like the variable worked correct (it was changed into the id), but then it cannot start the vbs.
Any hints, tips?
Thanks!
Blindfox
edited by Blindfox on 7/7/2010

All Comments (13)

avatar

Hi,
Can you try to put the variable between quote. Also can you try to execute the same thing in command line and see if you get the error ?

David Hervieux

avatar

Hi,
thanks for the quick response!
if tried the quotas, same error, now with quotas:
Unable to execute the script file [c:\TEST.vbs "f6170165-7f6d-4ace-9010-4d806643d9da"]
When i start a cmd with:
c:\TEST.vbs f6170165-7f6d-4ace-9010-4d806643d9da
my script works.
??
Blindfox

avatar

Hi,
What OS do you have ? Is it a 64 bits version ?

David Hervieux

avatar

CAn you check also the application log, it's in the menu Help, maybe there is more details of the error ?

David Hervieux

avatar

Hi,


yes its 64 Bit, Windows 7 Professional.
Here´s the log: (Translation from German, the first line says: "The system couldn´t find the specified file")
[23.06.2010 18:20]INFO System.ComponentModel.Win32Exception:Das System kann die angegebene Datei nicht finden
  beiSystem.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
  beiSystem.Diagnostics.Process.Start()
  beiSystem.Diagnostics.Process.Start(ProcessStartInfo startInfo)
  beiDevolutions.RemoteDesktopManager.ConnectionEvents.RunScriptFile(String script,Boolean waitForExit, Int32 timeout, Boolean runAsAdmin, Int32 pause)

I try to run it as Administrator: same error.
I try to run it with a path without blanks (h:\test.vbs): same error.
Has anybody this working with Windows 7 Pro 64 Bit?
THANKS!
Blindfox

avatar

I might know what is the problem, the application is 32bits and I think that because the the Windows folder virtualization, the process is unable to find windows scripting host application. I have a solution for that, I will add it to the next beta

David Hervieux

avatar

I might know what is the problem, the application is 32bits and I think that because the the Windows folder virtualization, the process is unable to find windows scripting host application. I have a solution for that, I will add it to the next beta

David Hervieux

avatar

Hi,


that would be great!
Thanks, David!
Blindfox

avatar

Hi David,
i tried the new beta, but unfortunately it doesn´t work.
Then i tried to check it out on a Windows XP 32 Bit System: it do not work, too.
You can try it for yourself: generate a test.vbs file with the following lines:

set WshShell = CreateObject("WScript.Shell")
for i = 0 to WScript.Arguments.Unnamed.Count -1
WScript.Echo WScript.Arguments.Unnamed(i)
next




You can try the functionality if you start the test.vbs from a cmd with some parameters:
test.vbs hhh
the vbs starts a msgbox with: hhh
If you start it from the event it doesnt start. It creates an error:
Unable to execute the script file [v:\test.vbs "Mydomain"]
Exactly the same is on the XP 32 Bit and on the Win 7 64 Bit System.
Could you test the script?
Thanks,
Blindfox

avatar

Hi,
I will retry it today and come back to you.

David Hervieux

avatar

Hi,
You're right, the application was not handling correctly the parameters, I updated the binaries, but not the version. Can you give it a try ?

http://remotedesktopmanager.com/download/Devolutions.RemoteDesktopManager.Bin.5.8.0.10.zip

David Hervieux

avatar

Hi David,
THANK YOU!!!!! :)
With this Version it works! (Tried on Windows 7, 64 Bit).
Thanks a lot,
Blindfox

avatar

Hi,
I must say, thanks to you. Your were very helpful with this bug.

David Hervieux