So how to get clear on that (tricky bug)
Running Modo 601_SP5 on Windows 7 x64 :
Launching modo from recent programs shortcut, submit script works
Launching modo from somewhere else, submit script is not found
I attach a screenshot showing both launched at the same time; left one from the recent programs, right one manually found in the “All Programs” menu
Weird!
Can you show us the exact error? Also, can you let us know which version of Deadline 6 you are running? Finally, can you send us a copy of the perl script you’re trying to run from Modo (I seem to recall you modifying it before).
Thanks1
Deadline Repo & Client : 6.0b11 (clean install from last week-end)
The error is as shown in the screenshot : monitor 3
Original 6.0b11 perl script deployed to the modo Workgroup
Works fine when launching from recent programs shortcut
And I admit it’s the 1st time I see that
when launched from somewhere else, it does find the ENV because it is able to chdir
the error occurs on line 94 I think because in modo event log I can see “$script” is define, but without “$root”
Ah, I didn’t realize how wide that screen shot was. 
I can’t seem to reproduce this problem here on Windows 7. I’ve tested from the recent programs list, I tested pinning modo to the start menu and the task bar, and in all cases it ran the script just fine.
Have you tried restarting your machine to see if that helps?
Try when running the default shortcut on the desktop
this one seems not to work
maybe it’s due to some miconfiguration here but I wouldn’t know where
Rebooting is not the answer as it happens from all workstations here
(confirmed, I just recreated the shortcut on my desktop, it does not detect the script)
attached are both master log from desktop (failed) and recent programs (success)
I can confirm it also works when pinned to the taskbar
modosuccess.TXT (696 Bytes)
modofailed.TXT (521 Bytes)
Thanks! I was able to reproduce this. The problem is that when we call deadlinecommand.exe, we don’t get any stdout back. So I wrote a test script that tries calling another application (in this case, python with the -h argument), and when I launched modo from the shortcut, I didn’t get any output from “python.exe -h” as well. When I launched modo from the Start menu, I did get output from “python.exe -h”.
So what this tells me is that either modo or perl is having issues launching a process this way, and it’s nothing specific to Deadline. So I’m not sure we can do anything about this. 
I followed up with Luxology support …
