Solved

Run Workspace with Data, FME Cloud


I am trying to troubleshoot why a cloud workspace won't run with data and I am getting this response from the server.

"request": "\\"DataProcessing/FieldDataLineCreator/FieldDataLineCreator.fmw\\" -XML_PARAMETER {\\"remote-addr\\":\\"127.0.0.1\\",\\"host\\":\\"production-tgs.fmecloud.com\\",\\"user-agent\\":\\"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0\\"}C:\\\\fakepath\\\\1801116-012618RF(TGS_Export_v2).csvhttps://production-tgs.fmecloud.com/fmedatadownload/DataProcessing/FieldDataLineCreator.fmw?detail=high{\\"opt_responseformat\\":\\"json\\",\\"SourceDataset_CSV2\\":\\"C:\\\\\\\\fakepath\\\\\\\\1801116-012618RF(TGS_Export_v2).csv\\",\\"detail\\":\\"high\\",\\"opt_showresult\\":\\"true\\",\\"token\\":\\"\\"} --FME_SECURITY_USER \\"\\" --FME_SECURITY_ROLES \\"fmesuperuser user:superuser fmeadmin\\" --FME_SERVER_HOST \\"localhost\\" --FME_SERVER_PORT \\"7071\\" --FME_SERVER_WEB_URL \\"https://production-tgs.fmecloud.com\\" -ACAD_1_DATASET \\"!FME_AUTO_DIR_NAME!.zip/processed.dwg\\"",

This is the part of the request I believe to be wrong.

C:\\\\fakepath\\\\1801116-012618RF(TGS_Export_v2).csvhttps://production-tgs.fmecloud.com/fmedatadownload/DataProcessing/FieldDataLineCreator.fmw?

I get this failure message in the workspace on the server.

CSV reader: Failed to open file 'C:\\fakepath\\1801116-012618RF(TGS_Export_v2).csv' for reading. Please ensure that the file exists and you have sufficient privileges to read it.

icon

Best answer by gerhardatsafe 2 April 2018, 17:46

View original

2 replies

Badge

Hi @garydlester,

please take a look at my answer to your previous question:

 

https://knowledge.safe.com/questions/67206/fmeserver-jobsubmitter-not-able-to-open-csv-file.html

This path will never succeed on FME Cloud (FME Cloud runs on Linux, so file paths will look e.g. like this /fakepath/1801116-012618RF(TGS_Export_v2).csv). On FME Server the best practice is to use the FME Shared Resource Parameter to reference file locations, as described in the answer above. Here is also an exercise from our free training resources focusing on how to reference resources on FME Server.

Best regards,

Gerhard

Finally got it to work, the workspace was using a dynamic writer,swapping it out fixed the problem. Your previous answer did help us isolate the problem to the workspace, very complete answers thank you.

Reply