Because you don’t have an absolute path to the redline.exe executable, Deadline is checking its bin directory and all directories in the PATH environment variable to find it. If you use an absolute path, that should fix the error.
If the folder that redline.exe is in IS in your PATH environment variable, try restarting all the Deadline applications on the machine (including the Launcher). It’s possible that the Slave simply doesn’t have the new environment loaded yet.
I thought the point of the Startup Directory was that you could just specify the NAME.exe in the command lines. No? It even says “0: INFO: Executable found: REDline.exe” so isn’t it finding it?
It’s never worked that way, but I can see how that would be misleading. In v5 and earlier, the executable for the command script plugin had to be absolute. We added the ability to use relative paths in v6 in a general way, but didn’t think to handle this special case for the command script plugin. This should be a simple fix.
It means it’s finding it in the command file submitted with the job, so this is also misleading.