The log entry is "
FACTORY_NAME Router and Unexpected Input Remover COMMAND_PARM_EVALUATION SINGLE_PASS MULTI_READER_KEYWORD SDE30_1 ..." Which looks like a call to the reader but I have no idea why the parameters generated by the task scheduler would be different than those built by the workbench
Best answer by erik_jan
The idea that you are using FME server might not be right.
If you use a batch script to run the FME workspace in a Windows scheduler the issue can be in multiple installations of FME on the machine. If that is the case, you should insert the path to the fme.exe file in front of the executable in the batch file (as the FME 2016 executable might not be the first fme.exe that is found by the OS.
+22The idea that you are using FME server might not be right.
If you use a batch script to run the FME workspace in a Windows scheduler the issue can be in multiple installations of FME on the machine. If that is the case, you should insert the path to the fme.exe file in front of the executable in the batch file (as the FME 2016 executable might not be the first fme.exe that is found by the OS.
The idea that you are using FME server might not be right.
If you use a batch script to run the FME workspace in a Windows scheduler the issue can be in multiple installations of FME on the machine. If that is the case, you should insert the path to the fme.exe file in front of the executable in the batch file (as the FME 2016 executable might not be the first fme.exe that is found by the OS.
As you said the batch script found FME 2015 first and it would not run a 2016 workbench. I couldn't get it to work by putting the full path in the batch script but changing the path order in the Envermental Variables solved the problem. Thanks much!!
+22If the FME home directory contains spaces you will need to use double quotes, like this:
"c:\\program files\\FME 2016\\fme.exe" my_workspace.fmw --param1 value1
