Skip to main content
We've started having problems with a number of existing fme workspaces that have worked fine for a number of years.

 

 

The workspaces run, however looking at the log file there are several warnings titled "Unexpected end of file". The end result is mapinfo tab files written out with geometry missing from a varying number of features.

 

 

Sometimes rerunning the script produces the same errors but with slightly different numbers of features written without geometry, sometimes rerunning gives no warnings and everything is processed fine.

 

 

I have already split the workspace into two separate workspaces in case it was a memory issue. This worked fine for 5 days (it runs overnight) before one failed again.

 

 

Any ideas on where to start?

 

 

Hi,

 

 

Basically FME has the compatibility with earlier version, so I think the cause possibly is in the source data rather than the difference in FME versions. How about starting from inspecting the source data?

 

 

Takashi
I'm not sure where you're reading anything about different FME versions?

 

 

The 'unexpected end of file' warning (and resulting error in tables written) occurs intermittently in both FME 2012 / FME 2013.

 

 

It has been running daily since the beginning of the year with FME 2013 without issue until last week.

 

 


Ah, I jumped to a conclusion just reading "existing fme workspaces that have worked fine for a number of years", sorry.
Turned out to be a lack of memory issue.

 

 

Would be helpful if it decided it was out of memory rather than writing out mapinfo files that contain no geometry.

Reply