Skip to main content
  • EN

Hellow fellow FME-users, 


I'm trying to run FMEFactoryPipeline repeatedly within a PythonCaller. 


After some iterations it stops running unexpectedly and FME is only providing me the unhelpful error message: "Error running translation".


I think the order of the function I'm calling on the pipeline factory is wrong.

This is the order I'm using right now:

# initialize pipeline
pipeline = fmeobjects.FMEFactoryPipeline()
# Add pipeline factory (spatialrelator in my case)
pipeline.addFactory()
# Push features through the pipeline
pipeline.processFeature()
# Execute the pipeline
pipeline.allDone()

Or I'm forgetting to call a certain function on the pipeline object.


Documentation on FMEFactoryPipeline can be found here: http://docs.safe.com/fme/html/FME_Objects_Python_A...



I attached an example workspace.

Has someone experience with this issue?


Thank you very much.

I have the same issue as you with 2015 and 2016. I'll try to find the source of the problem and come back to you later today or early next week.

Hello,

I played a bit with the factory code and it seems to be an issue with 2015 and 2016.

The attached workspace runs fine in 2014 but crashes 2015 and 2016.

I submitted the workspace to SAFE for investigation (case #C113361).

Regards,

Larry

Hello,

I played a bit with the factory code and it seems to be an issue with 2015 and 2016.

The attached workspace runs fine in 2014 but crashes 2015 and 2016.

I submitted the workspace to SAFE for investigation (case #C113361).

Regards,

Larry

@daleatsafe Can I add a reference to the SAFE case number here?

@daleatsafe Can I add a reference to the SAFE case number here?

Please do. We'll want to give this a look and will in any case, but no problem having a reference in here.

Please do. We'll want to give this a look and will in any case, but no problem having a reference in here.

Done, thanks.

Hello,

SAFE confirmed that there is a bug with 2014 SP5, 2015 and 2016.

They are expecting a fix in 2016.1.

Regards,

Larry

Hello,

SAFE confirmed that there is a bug with 2014 SP5, 2015 and 2016.

They are expecting a fix in 2016.1.

Regards,

Larry

Thank you very much Larry. I'm looking forward to the new release.

Hello,

SAFE confirmed that there is a bug with 2014 SP5, 2015 and 2016.

They are expecting a fix in 2016.1.

Regards,

Larry

Just tested FME Desktop 2016.1 Release Candidate (build 16489) and this is fixed.

Can be downloaded here:

https://www.safe.com/support/support-resources/fme-downloads/beta/

Reply


Community Stats

30,113
Posts
114,307
Replies
37,744
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.