Data Download success, empty zip file

Not anything to do with this?

 

 

http://fmepedia.safe.com/articles/Error_Unexpected_Behavior/Dataset-Fanout-doesn-t-work-for-Services

 

I don't think so. I'm not using a fanout. And it finishes successfully and creates a zip file, but the file file doesn't contain the output files that were written.

Sure I had this before. I'll rack my brain to see if I can remember :-)

Hi Michael!

 

 

Remember having a similar issue when I defined the output filename as for instance output.kml. Then it would not write the file to the temp-catalogue, however somewhere else on the disk (I think somewhere on the FMEServer Resources directory). Can you examine the log and see where the file was written (not the zip-file). 

Sounds like this issue: http://fmepedia.safe.com/articles/Error_Unexpected_Behavior/Data-Download-Zip-File-Empty   Sometimes when publishing a workspace we don't automatically assign a writer to the Data Download Service.  When you publish your workspace look at the Edit settings for the Data Download Service and make sure there is ""Desired Output Writer" set

That was it Ken! Thanks for finding that article.

Ken,

 

 

I am having the same problem at the moment, and I could really do with some help!

 

 

My data download service has 3 possible output formats, and all three are ticked as the 'Desired Output Writer' with the Data Download Service:

 

 

1. ASCII grid

 

2. csv

 

3. File Geodatabase Raster

 

 

All three formats output correctly when using the Job Submitter.

 

 

With the Data Download Service, I get empty zip files for the csv and geodatabase output (but is written to the output folder).

 

 

HOWEVER the ASCII output is properly zipped up, but not written to the output folder! Is written here instead-

 

 

Esri ASCII Grid Plugin: Closing the Esri Ascii Grid writer for file 'E:\\repo\\DefaultResults\\FME_747F090A_1363630510132_2668\\20130318181510_OP3'

 

 

Any ideas?!?

 

 

All three have a dataset and or file fanout.

 

 

Many thanks,

 

 

Owen

Hi Owen,

 

I think your issue is more likely related to the article Mark@SAUK pointed out:

 

 

http://fmepedia.safe.com/articles/Error_Unexpected_Behavior/Dataset-Fanout-doesn-t-work-for-Services

 

 

The key point is at the end:

 

In the workspace publish the Fanout Directory parameter on the writer and give the parameter the name FME_SERVER_DEST_DIR.

 

 

When the workspace is run on FME Server this macro is replaced by the destination directory for the service and the data can be fanned out and still accessible to the service.

Thanks Ken, that was exactly the information I needed and google pointed me to this thread :)