Executor: Eingabeumleitung wird nicht unterstützt

vvvv gamma question
1

hi all,

“FEHLER: Die Eingabeumleitung wird nicht untersttzt. Prozess wird unverzglich beendet.”

did something change in exexutor behaviour? why am I getting this error.
starting my watchdog from commandline works as expected. when starting with executor it seems to close with the application.

2

you need to copy the executor definition into your patch and enable this flag:

image
image1495×871 29.6 KB

These should all be inputs of the node, though…
Create no window should be true, in that case, I guess.

3

thanks!

still, would be great if this was a pin option.

4

I copied the entire executor patch to my own and set the flag, but now it tells me I have to disable the flag. Any suggestions?

image
image545×305 7.8 KB

5

can you tell us exactly what you do to get this error?

are you saying this has worked before? if so, which version of vvvv is this working with and which does fail you?

6

I copied the entire content of the executor patch into my own one and set the flag that Tebjan mentioned to true. Then, when I try to execute my bat file it throws this error.

TBH IDK if this ever worked. I build this watchdog functionality as fallback with gamma 2021.4.7 but never actually used it. I tested the bat file 2021 but I think I did not check if it runs when started from gamma.

7

ok, so any chance you can share the batch file and .vl doc where you execute it so we can reproduce the error?

8

here you go

executorError.zip (17.5 KB)

9

hm… i don’t believe this is an issue of the Executor which has “UseShellExecute” off exactly because it does redirect the streams. the error message you get seems to come from the “timeout” command you’re using, see: PowerShell batch script Timeout ERROR: Input redirection is not supported, exiting the process immediately - Stack Overflow

10

thank you kindly.

if you read this and also hate batch script, give this post a like!

2 Likes
11

hi all,

I revisited this problem, but could not make it work yet.

The BAT file works for me as intended, when launched from CMD ( throws no error and reboots the machine)
I tried executing it with executor; With and Without the “SetShellExecute” enabled.
In both cases it runs, the messages I get are the same as fromwithin CMD.
But when I close Gamma, the BAT process seems to close with it - no reboot.

image
image1069×870 19.7 KB

image
image1077×785 24.6 KB

generatedDog.zip (903 Bytes)

any pointers why this is not working?

12

ok seems to run with gamma 7.0 when I toggle on “run as admin”, but I am getting some errors:

  • Unexpected exception during Update: Process with an Id of -1 is not running.
  • Unexpected exception during Update: StandardOut has not been redirected or the process hasn’t started yet.

erros.zip (1.1 KB)

13

just checking: would it also be an option to not use Executor at all for this? would something like these be helpful?

image
image421×637 4.72 KB

but generally: indeed, when running-as-admin output redirection is not possible. that is a limitation of the underlying api.

14

thx, but I mainly want to check if vvvv is running, so it must not run in vvvv.

15

i don’t understand. your Executor is also running in vvvv, a separate instance?

16

I think he starts a watchdog when vvvv first starts, from within vvvv (which checks if vvvv is running from then on). And then it needs to keep running, while being detached from the lifetime of vvvv.

17

Yes, I use gamma for generating a custom watchdog, then start it with executor. I fixed it by starting a new instance of the same batch file from within my script:

@echo off
setlocal EnableExtensions EnableDelayedExpansion

if “%~1”==“min” goto :BEGIN
start “” /min “%~f0” min
exit /b

this works for me, also when vvvv is started from task scheduler