+2I download the example from the article "
Batch Processing Using the WorkspaceRunner"
When i run it an the fme2018 and don't change anything it works well. When i update the workspace runner to fme2018 ,it can not work any more. I don't know why. It troubles me a lot.
This is the ordinary one?
Then i update the workspacerunner
Best answer by mark2atsafe
Hi folks. I recreated the problem (thanks Takashi) and have filed a high-priority issue with the developers. I am hoping we're in time for a fix to go into 2018.1. I will keep you posted.
+2MY FME IS FME2018 X64. And I tried it on fme2017 X86 ,it works well. So the problem must be in the fme2018 X64
+21Hi @liujisheng
I think the MIF reader is not reading any features as you have not specified a value in the Feature Types to Read parameter. Can you try removing the Feature Types to Read parameter from your polygonbuilder workspace?
+2Hi @liujisheng
I think the MIF reader is not reading any features as you have not specified a value in the Feature Types to Read parameter. Can you try removing the Feature Types to Read parameter from your polygonbuilder workspace?
+2It will be great for me to find a case from fme2018 x64, but unfortunately I can not find it in the knowledge center.
+12Yes, I too faced strange behaviour of workspace runner transformer when I installed 2018 version. Workspace is working fine when I worked individually, but the same workspace is not working when I used workspace runner. It showed as successful but the output files will not be present in the directory as desired. I thought, FME was not installed properly until now and I continued working in 2017 rather than taking risk :).
Workspace runner is one of the backbone transformer of FME when we are working in batches/more workspaces.
+2Yes, I too faced strange behaviour of workspace runner transformer when I installed 2018 version. Workspace is working fine when I worked individually, but the same workspace is not working when I used workspace runner. It showed as successful but the output files will not be present in the directory as desired. I thought, FME was not installed properly until now and I continued working in 2017 rather than taking risk :).
Workspace runner is one of the backbone transformer of FME when we are working in batches/more workspaces.
Hi @liujisheng
I think the MIF reader is not reading any features as you have not specified a value in the Feature Types to Read parameter. Can you try removing the Feature Types to Read parameter from your polygonbuilder workspace?
Check this repro: fme2018-workspacerunner-defect.zip (FME 2018.0.1.1 build 18312)
The symptom will be clearly logged if you set Yes to the Wait for Job to Complete parameter in the WorksaceRunner and run.
Expected an even number of command line arguments, instead got 1 for command line: >> `--PARAM' <<An error occurred during the batch file execution, 1 translation failed. The following error message was raised: #2 : Expected an even number of command line arguments, instead got 1 for command line: >> `--PARAM' <<Program TerminatingTranslation FAILED.
+56Check this repro: fme2018-workspacerunner-defect.zip (FME 2018.0.1.1 build 18312)
The symptom will be clearly logged if you set Yes to the Wait for Job to Complete parameter in the WorksaceRunner and run.
Expected an even number of command line arguments, instead got 1 for command line: >> `--PARAM' <<An error occurred during the batch file execution, 1 translation failed. The following error message was raised: #2 : Expected an even number of command line arguments, instead got 1 for command line: >> `--PARAM' <<Program TerminatingTranslation FAILED.Yes, this is what I am finding too. In the example of the user the command is:
C:/Users/imark/Documents/Testing/polygonbuilder_2018.fmw --SourceDataset_MIF C:\Users\imark\Documents\Testing\BatchProcessingData\Data\parcel_L24.mif --FEATURE_TYPES --DestDataset_ESRISHAPE C:\Users\imark\Documents\Testing/BatchProcessingData\Output
Without a value for FEATURE_TYPES, FME fails. I'll file something with our developers immediately.
+56Hi folks. I recreated the problem (thanks Takashi) and have filed a high-priority issue with the developers. I am hoping we're in time for a fix to go into 2018.1. I will keep you posted.
+12Hi folks. I recreated the problem (thanks Takashi) and have filed a high-priority issue with the developers. I am hoping we're in time for a fix to go into 2018.1. I will keep you posted.
+2Hi folks. I recreated the problem (thanks Takashi) and have filed a high-priority issue with the developers. I am hoping we're in time for a fix to go into 2018.1. I will keep you posted.
+56
+12
Hi folks. I recreated the problem (thanks Takashi) and have filed a high-priority issue with the developers. I am hoping we're in time for a fix to go into 2018.1. I will keep you posted.