I would like to know if does FMEServerJobSubmitter recognize the path_windows? or is there any other parameter value that I should use that help me to write my information?

Hi Cecy,

You could try changing the "Wait for Jobs to Complete" parameter to Yes. That way the transformer will wait for the translation results and if anything, like for example an unrecognized path, causes the child jobs to fail, you will get this information in the parent workspace through the Failed output port of the transformer

Best regards,

Francisco

Hi Francisco!

Thank you for your answer! 

I implemented the best practice. I changed the parameter 'Wait for Jobs to Complete' to yes, but it still failing.

Regards,

Cecy 😊

To be honest it looks like the helper workspace is being passed filenames that don't exist. So it "fails" but runs to completion because there isn't really an error.

Are you using the Path/Directory reader? I just tried that and it does work on Server, so that part should be OK. For example in the log I get:

===========================================================================
191	2022-1-27 15:31:06 | Logger: Feature is:
192	2022-1-27 15:31:06 | +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
193	2022-1-27 15:31:06 | Feature Type: `Logger_LOGGED'
194	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `fme_feature_type' has value `PATH'
195	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `fme_geometry' has value `fme_undefined'
196	2022-1-27 15:31:06 | Attribute(entangled: string: UTF-8): `fme_type' has value `fme_no_geom'
197	2022-1-27 15:31:06 |           entangled to path_geom
198	2022-1-27 15:31:06 | Attribute(32 bit integer)          : `multi_reader_full_id' has value `0'
199	2022-1-27 15:31:06 | Attribute(32 bit integer)          : `multi_reader_id' has value `0'
200	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `multi_reader_keyword' has value `PATH_1'
201	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `multi_reader_type' has value `PATH'
202	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_directory_unix' has value `/data/fmeserver/resources/data/iMark/'
203	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_directory_windows' has value `\data\fmeserver\resources\data\iMark\'
204	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_extension' has value `txt'
205	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_filename' has value `ATextFileTest.txt'
206	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_geom' has value `path_none'
207	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_rootname' has value `ATextFileTest'
208	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_type' has value `file'
209	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_unix' has value `/data/fmeserver/resources/data/iMark/ATextFileTest.txt'
210	2022-1-27 15:31:06 | Attribute(string: UTF-8)           : `path_windows' has value `\data\fmeserver\resources\data\iMark\ATextFileTest.txt'
211	2022-1-27 15:31:06 | Coordinate System: `'
212	2022-1-27 15:31:06 | Geometry Type: IFMENull
213	2022-1-27 15:31:06 | Coordinate Dimension: 2

It looks odd, but that's because this is on FME Cloud, which is a Linux platform, so the paths won't look like Windows paths. Still, I would add a Logger to the control workspace to log what it thinks are the file paths, just so you can be sure they are correct.

Then look at the log files for each helper workspace. Does it say that it can't find the file?

I hope this helps.