Skip to main content
  • EN

I have some FME translation files (4 or 5 of them) that I use regularly on different datasets. These have worked without issue for some time, and are still working now except for one strange thing that's changed.

 

The process runs, ends with "Translation was Successful" in the log as normal, then about 5 seconds later "Translation Failed" appears in red.

 

As far as I can tell everything has worked fine, there are no errors in the rest of the log (usually if it fails I get good detailed error messages to help me fix my data problem). I think my data is good to go. But I'm not sure why I'm getting this delayed "Translation Failed" message in the log.

 

One of the blue warning type messages (so not an error) says that my ArcGIS Pro v3.2 isn't supported, but this isn't shown as an error and my data appears to be translating fine. I think this ArcGIS Pro update is the only recent change that might affect FME though, so is that the culprit?

 

Current installed ArcGISPro version '3.2.0' is unsupported. Minimum supported version is '2.3.0', and maximum supported version is '3.1.0'

 

What could be causing the problem - is it ArcGIS Pro or something else? And how do I fix it?

Current installed ArcGISPro version '3.2.0' is unsupported. Minimum supported version is '2.3.0', and maximum supported version is '3.1.0'

 

i think you answered you same question ;-)

Is there any python in the workspace? Perhaps a shutdown script?

 

I do suspect that the ArcGIS version is probably what is causing the issue but it would be nice to know where exactly -

 

Something else to look at (if you have no python in the worksapce) is to turn on DEBUG logging and see if there is anything else in there - Just take it with a grain of salt - it's very common to see a lot of BADNEWS messages in the log which can usually be ignored. But in this case it miiiight give you a few more clues

Is there any python in the workspace? Perhaps a shutdown script?

 

I do suspect that the ArcGIS version is probably what is causing the issue but it would be nice to know where exactly -

 

Something else to look at (if you have no python in the worksapce) is to turn on DEBUG logging and see if there is anything else in there - Just take it with a grain of salt - it's very common to see a lot of BADNEWS messages in the log which can usually be ignored. But in this case it miiiight give you a few more clues

Thanks for your suggestion of turning on DEBUG logging. No additional errors logged, and nothing strange in the warnings. Still just that one error, right at the end 5 seconds after "Translation was Successful"

 

It may well be the ArcGIS Pro version, however it seems strange to be sending a Failed error when there are no other errors in the log (even the notice about the ArcGIS Pro version is just a warning level message)

 

There is no python in the workspace

Is there any python in the workspace? Perhaps a shutdown script?

 

I do suspect that the ArcGIS version is probably what is causing the issue but it would be nice to know where exactly -

 

Something else to look at (if you have no python in the worksapce) is to turn on DEBUG logging and see if there is anything else in there - Just take it with a grain of salt - it's very common to see a lot of BADNEWS messages in the log which can usually be ignored. But in this case it miiiight give you a few more clues

EDIT: I may have spoken too soon after my test below. I remembered I could change the Esri setting in FME, so updated it to ArcMap to test. I no longer get the ArcGIS Pro version compatibility warning (which I thought was the cause), but still get the error Translation Failed at the end.

 

I've just done a test - created a new FME file, added a reader to a new feature class, one transformer (copied an attribute) and a writer.

 

First test was File GDB to File GDB - no error...

 

Second test was Personal GDB to File GDB (which is what my original FME files are working with) - get the same Translation Failed error at the end. I can confirm it completed successfully though (the feature class was written correctly, with the copied attribute), which makes me feel a little more confident my other data is being written correctly too.

 

I'm guessing now this confirms it is probably just a compatibility issue with ArcGIS Pro 3.2 and the fact that Personal Geodatabase MDB files are pretty much deprecated now.

Reply


Community Stats

30,162
Posts
114,480
Replies
37,808
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.