Skip to main content
Question

Error 395013 when calling fmeobjects.FMEWorkspaceRunner()

C

I am trying to create an instance of the FMEWorkspaceRunner in python so I can kick off a workspace. I am able to import fmeobjects, but when I try to create an instance of the FMEWorkspaceRunner I get the following error:

FMEException: FMEException: 395013: OEM License failure.

I'm not sure how to fix this. If i start a command line terminal from within my FME installation folder, I can create an instance of fmeobjects.FMEWorkspaceRunner(). It's only when I try to create it in a script that I'm having a problem. I am also using arcpy within the same script, so could it be something to do with Python paths that I can't figure out? Any help would be appreciated.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • April 18, 2019

Hi @calvinmccoy,

FMEObjects will search the system path for the first fme.dll it can find to connect to. However, an OEM version of FME is included with some versions of ArcGIS. If your ArcGIS is ahead of FME in the system path, then this OEM FME is being invoked by FMEObjects, but has a license that locks its usage to ArcGIS.

Please use your Windows Control Panel to edit System Properties - Advanced - Environment Variables - System Variables - Path. Move the FME folder above the ArcGIS folder(s).

This should allow FMEObjects to connect to the correct fme.dll.

C
daveatsafe wrote:

Hi @calvinmccoy,

FMEObjects will search the system path for the first fme.dll it can find to connect to. However, an OEM version of FME is included with some versions of ArcGIS. If your ArcGIS is ahead of FME in the system path, then this OEM FME is being invoked by FMEObjects, but has a license that locks its usage to ArcGIS.

Please use your Windows Control Panel to edit System Properties - Advanced - Environment Variables - System Variables - Path. Move the FME folder above the ArcGIS folder(s).

This should allow FMEObjects to connect to the correct fme.dll.

That's great thanks for your help!

Helpful Members This Week

Community Stats

32,055
Posts
121,717
Replies
39,681
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

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
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.