Hi @mr_fme Did you forget the dash? It should be -LOG_FILENAME
- What result would be shown on the command prompt window, if you run the workfpace through cmd with the same command line?
- Have the log file "c:\\fme.log" been created?
There´s no log file created!
The CMD show me the message below
Expected an even number of command line arguments, instead got 3 for command line: >> `embargos.fmw' `-LOG_FILENAME' `C:\\fme.log' <<Program TerminatingTranslation FAILED.
If the actual workspace file path (C:\\...\\...fmw) contains spaces, you have to quote it by double quotations.
Also, I don't think the dash leading LOG_FILENAME is necessary.
- What result would be shown on the command prompt window, if you run the workfpace through cmd with the same command line?
- Have the log file "c:\\fme.log" been created?
If the actual workspace file path (C:\\...\\...fmw) contains spaces, you have to quote it by double quotations.
Also, I don't think the dash leading LOG_FILENAME is necessary.
If the actual workspace file path (C:\\...\\...fmw) contains spaces, you have to quote it by double quotations.
Also, I don't think the dash leading LOG_FILENAME is necessary.
@takashi
You help a lot. This command work properly, but when I paste in .bat file nothing happens.
C:\\FME_2017\\fme.exe "C:\\Users\\Smith\\Workspaces\\Fluxos\\down river.fmw" -LOG_FILENAME c:\\fme.log
If the actual workspace file path (C:\\...\\...fmw) contains spaces, you have to quote it by double quotations.
Also, I don't think the dash leading LOG_FILENAME is necessary.
Sounds strange. The bat file should work if its content is the command line which you were able to execute through command prompt successfully.
How did you run the bat file?
Sounds strange. The bat file should work if its content is the command line which you were able to execute through command prompt successfully.
How did you run the bat file?
Hi @Takashi,
I´m testing now in Windows 7, and work properly. The problem in bat file occur only in Windows 10

.
Thank´s
Sounds strange. The bat file should work if its content is the command line which you were able to execute through command prompt successfully.
How did you run the bat file?
Run the batch file from CMD in your Windows 10 machine, and check what message would appear.
Just type the batch file path (quote the path with double quotations if it contains spaces) on CMD window and press the Enter (Return) Key.
Run the batch file from CMD in your Windows 10 machine, and check what message would appear.
Just type the batch file path (quote the path with double quotations if it contains spaces) on CMD window and press the Enter (Return) Key.
My problem has been solved. I put a command line directly in the Windows 10 Task Scheduler and ran perfectly, it was what I needed. You do not need to create a batch file now. However, what is done based on execution rules for the process of running a mapping tool to run a program, for example, runs.But a usage resolution or task scheduler has already solved the problem for now.
Thank you very much for your attention.