Skip to main content
Solved

FME Desktop works fine but fails when published to FME Server

  • October 23, 2017
  • 1 reply
  • 9 views

dfresh
Forum|alt.badge.img

Hey Folks,

I created a working fmw on desktop, executes fine on desktop, fails on server.

notes

  • login to server, copy fmw and data, executes as expected

the fmw has the following logic

  • SQL executor (this runs succesfully)
  • Reader - Esri Geodatabase (File Geodb Open API)
  • Reader - Esri Geodatabase (File Geodb)

however in the log, it fails because of the following (image below).

my understanding is it only should use a BASIC/ARCVIEW license for the File Geodb format. however not sure what is happening here. perhaps it has to do with the user level running the engine? no clue.

Best answer by brianatsafe

Hi @dfresh,

 

I suspect that the user that is being used to run the FME Engine may not have permission to access the ArcGIS License. Here is a good article that explains this: https://knowledge.safe.com/articles/24153/using-fme-server-with-esri-software.html

 

 

Try what is suggested in the "FME Engine Service Account Requirements" section.

 

 

Also, ensure that you are using both 64bit FME/Esri or 32bit FME/Esri products as mixing these will not work. Hope that helps!
View original
Did this help you find an answer to your question?

1 reply

brianatsafe
Safer
Forum|alt.badge.img+11
  • Safer
  • Best Answer
  • October 23, 2017

Hi @dfresh,

 

I suspect that the user that is being used to run the FME Engine may not have permission to access the ArcGIS License. Here is a good article that explains this: https://knowledge.safe.com/articles/24153/using-fme-server-with-esri-software.html

 

 

Try what is suggested in the "FME Engine Service Account Requirements" section.

 

 

Also, ensure that you are using both 64bit FME/Esri or 32bit FME/Esri products as mixing these will not work. Hope that helps!

Reply


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