Skip to main content
Question

Missing output files when publishing to FME Server (works locally and in old workbench on server )


fmegrinder
Contributor
Forum|alt.badge.img+2

Hi,

I’m running into an issue with FME Workbench 2021. When I run the workspace locally, all expected files are generated correctly. The same workspace also works when published to our older FME Server (same version, 2021.0).

However, after publishing it to a new FME Server environment (also 2021.0), some of the output files are missing. No errors are reported in the log, but certain files simply don't get written. The log even says they have created the files.

Nothing has changed in terms of file paths or logic – they still use dynamic paths (e.g., FME_SHAREDRESOURCE_TEMP). The only major change is that we replaced FeatureReader with HTTPCaller to avoid a bug with esri_OID in high availability setups.

I’m running the exakt same job but still I get this issue. 

 

I’ve already:

Verified that the paths are correct

Checked resource locations

Tried republishing and updating the “download data” edit.

Still, the problem remains in the new server setup.

What could be causing this? 

6 replies

david_r
Celebrity
  • May 28, 2025

Could it be that the new server is low on disk space and that the FME Flow cleanup task is in aggressive clean up mode?

https://support.safe.com/hc/en-us/articles/25407763387277-FME-Flow-Troubleshooting-Cleanup-Tasks


fmegrinder
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • May 28, 2025

Thanks for the tip ​@david_r but that should not be the issue.

The old workspace that does the same thing works 100% of the times.

But the new one that I’ve done some alternations with does not include the files(most often pictures).

 


hkingsbury
Celebrity
Forum|alt.badge.img+54
  • Celebrity
  • May 29, 2025

One debugging step i’d consider would be to write to a defined location such as c:\temp. This will help narrow down if it is a ‘writing the file’ issue or a ‘location where the file is written’ issue


fmegrinder
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • May 30, 2025

Thanks for the tip, @hkingsbury.

I’ve tried this now, but unfortunately it doesn’t work.
I think it's a strange bug in the Workbench.

It works when I activate the “old path” inside the embedded transformer — even though that path doesn’t lead to any output port.
If the part is active, everything works perfectly.
But if I deactivate it, it stops working.

So it seems like some kind of bug.
Any suggestions on how to solve it?



 


hkingsbury
Celebrity
Forum|alt.badge.img+54
  • Celebrity
  • June 4, 2025

An approach that i’m not sure if it will work, but worth trying…..

Open a brand new, fresh workspace and copy the entire contents of the existing process into the new one. Save, publish to Flow and test


virtualcitymatt
Celebrity
Forum|alt.badge.img+35

Are you using the data download service? Are the files missing from the ZIP?

I’ve seen some situations where is seems like the zip gets created before all data are actually available to be zipped. 

Perhaps enabling this “old path” changes the order in which things are processed.


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