Skip to main content
Solved

batch deployment

  • November 8, 2021
  • 1 reply
  • 44 views

jofl

I have a problem after updating FME to 2021.2.

I use a txt file to get the workbench in a batch depoyment.

But after i have updated FME to version 2021.2 i get a notification that the file not exist. (name of the file txt.txt) I have this problem in all my workbenches who are running in a batch deployment. I have this problem after updating my FME.

 

Logfile:

Processing C:Gladheidsbestrijding      xt.txt (1 of 1)

 

Translation FAILED with 1 error(s) and 0 warning(s) (0 feature(s) output)

Text File Reader: Source dataset 'C:Gladheidsbestrijding       xt.txt' does not exist

 

An error occurred during the batch file execution of C:/Users/EJANSE~1/AppData/Local/Temp/FME_1636366013186_13572. 1 translation failed. The following error message was raised:

#1 : Text File Reader: Source dataset 'C:Gladheidsbestrijding  xt.txt' does not exist

Program Terminating

 

Translation FAILED.

child process exited abnormally

 

FME encountered an error. Please contact http://www.safe.com/support

 

 

CTL File

#!/usr/bin/env fme

 

set workspacename {C:/Gladheidsbestrijding/Gladheidsbestrijding.fmw}

 

lappend destMacroList {DestDataset_SHAPEFILE_1}

lappend suffixList {}

lappend destDirList {C:/Gladheidsbestrijding/Gladheidsbestrijding/}

lappend destMacroList {DestDataset_SHAPEFILE_2}

lappend suffixList {}

lappend destDirList {C:/Gladheidsbestrijding/Gladheidsbestrijding/}

lappend destMacroList {DestDataset_SHAPEFILE_3}

lappend suffixList {}

lappend destDirList {C:/Gladheidsbestrijding/Gladheidsbestrijding/}

set recreateSourceTree "no"

 

set superBatchFileName [FME_TempFilename]

 

set superBatchFile [open $superBatchFileName "w"]

 

lappend sourceDatasets {C:/Gladheidsbestrijding/txt.txt}

 

 

 

Best answer by jofl

The soulution to this problem is:

Put a txt file in the workbench and run the [Batch Deploy]

Throw the txt file out of the workbech and open the .ctl file.

Delete the /.txt in the path [lappend sourceDatasets {C:/Eikenprocessierups/.txt}] and save the file.

Now you kan run the workbench without a error message 😀

 

 

set superBatchFileName [FME_TempFilename]

set superBatchFile [open $superBatchFileName "w"]

lappend sourceDatasets {C:/Eikenprocessierups/.txt}

 

View original
Did this help you find an answer to your question?

1 reply

jofl
  • Author
  • Best Answer
  • November 8, 2021

The soulution to this problem is:

Put a txt file in the workbench and run the [Batch Deploy]

Throw the txt file out of the workbech and open the .ctl file.

Delete the /.txt in the path [lappend sourceDatasets {C:/Eikenprocessierups/.txt}] and save the file.

Now you kan run the workbench without a error message 😀

 

 

set superBatchFileName [FME_TempFilename]

set superBatchFile [open $superBatchFileName "w"]

lappend sourceDatasets {C:/Eikenprocessierups/.txt}

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings