Skip to main content
  • EN
I'm trying to run a batch process using the cmd prompt and am stuck on an FME_EncodeText error for my input source shapefile.  The workspace just reads in a shapefile datasource then converts it to various formats and fanouts based on basename.  Any ideas

 

 

Y:\\web_processing\\Projects\\Teranet\\postgis_clipper>fme.exe shp_parcel2multi_2013_02_18.fmw --src_shp Y:\\web_processing\\Projects\\Teranet\\postgis_clipper\\parcel_tiles_2013_03\\parcels_1\\parcel174355474302013tera\\Label.shp --FEATURE_TYPES "" --kml_fanout_directory parcel_tiles_2013_03_fme_kml --dwg_fanout_directory parcel_tiles_2013_03_fme_dwg --dgn_fanout_directory parcel_tiles_2013_03_fme_dgn

 

            Feature Manipulation Engine 2009 (20090106 - Build 5658)

 

                       FME Professional (node locked-crc)

 

                               Permanent License.

 

                         Machine host name is: server17

 

                           Copyright (c) 1994 - 2009

 

                               Safe Software Inc.

 

 

 

INCLUDE -- failed to evaluate TCL expression `  set encodedVal  FME_EncodeText {

 

Y:\\web_processing\\Projects\\Teranet\\postgis_clipper\\parcel_tiles_2013_03\\parcels_1\\parcel174355474302013tera\\Label.shp}];        puts "MACRO src_shp__FMEENCODED__ $encodedVal" ;   ' -- invalid command name "FME_EncodeText"

 

    while executing

 

"FME_EncodeText {Y:\\web_processing\\Projects\\Teranet\\postgis_clipper\\parcel_tiles

 

_2013_03\\parcels_1\\parcel174355474302013tera\\Label.shp}"

 

    invoked from within

 

"set encodedVal \FME_EncodeText {Y:\\web_processing\\Projects\\Teranet\\postgis_clip

 

per\\parcel_tiles_2013_03\\parcels_1\\parcel174355474302013tera\\Label.shp}..."

 

Program Terminating

 

 

Translation FAILED.
Hi Travis,

 

 

you seem to be running FME 2009 here, are you sure that's your intention? I'm guessing you could get these kinds of strange errors if you were to run a newer workbench file with a very old version of FME.

 

 

Try specifying the complete path of fme.exe (remember to put double quotes around it if there are any spaces in it) and see what happens.

 

 

Example "c:/program files/fme2013/fme.exe" <the rest of your parameters here>

 

David
Hi, is the workspace you written with a later build of FME than build 5658 as that's the engine you are calling. This can happen with command line running when you have more than 1 build of FME installed. Either specify the full path to the later build FME.exe or edit your PATH environment variable to give priority to the newest install of FME.
Thanks for your help the translation now works!

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.