Skip to main content
Solved

FME Desktop Esri Edition with ArcGIS Desktop licensing requirements when running on a VM in a remote network

  • February 16, 2023
  • 2 replies
  • 56 views

ioan.pintilie
Contributor
Forum|alt.badge.img+2

Hi!

 

I’ve recently installed and licensed FME Desktop Esri Edition (on 32Bit) on a VM within an isolated network. I need to use the ArcSDE Geodb Reader of FME, to have access to Network and Relationship information, and as a pre-requisite I’ve also installed the ArcGIS Desktop (by default on 32Bit). I have not yet licensed the ArcGIS Desktop that I’ve installed along with the FME. Still, I can call and start to configure the ArcSDE Geodb Reader.

My goal is to connect to several ArcGIS VMs within the same isolated network. I’ve received a bunch of .sde database connection files that I’ve used in the configuration of the ArcSDE Geodb Reader. I do not know exactly if these VMs that I’m trying to connect to are running just a database or have ArcGIS software installed and licensed as well (like ArcGIS Desktop, ArcGIS Server). I have little knowledge about the ArcGIS architecture. I know that there are several ArcGIS models dispersed on a bunch of VMs.

My problem occurs in the set-up of the ArcSDE Reader when I’m trying to select the Tables that I want to read (the .sde connection file is alright). I get what seems to be a licensing error:

“Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147220952'. The error message from ArcObjects is: {The Product License has not been initialized.}”

 

My questions would be: Do I have to license the ArcGIS Desktop that I’ve installed locally along with FME Desktop? Can I license the ArcGIS Desktop on this VM independent of the others ArcGIS installations in the network? Will it work? Or should I check the licensing procedure of ArcGIS for the other VMs in the network (should I check for a licensing server, or ask for a floating license)?

 

For sure a licensed ArcGIS is required; is it for the local ArcGIS installed as pre-requisite? I’ve consulted the following material:

-         https://community.safe.com/s/article/required-arcgis-license-types-for-fme-geodatabase

-         https://community.safe.com/s/article/geodatabase-formats-missing-greyed-out-or-have-unm

-         https://community.safe.com/s/article/notes-on-fme-and-esri-versions-and-compatibility

-         https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/geodatabase/GEODATABASE_SDE_reader.htm

 

Thank you for your thoughts! 

Best answer by hkingsbury

The Esri Instance on the machine you're running FME on needs to be licensed. SDE reading/writing is a licensed operation opposed to a GDB where you can use either the API (free) or ArcObjects (licensed) based implementation

View original
Did this help you find an answer to your question?

2 replies

hkingsbury
Celebrity
Forum|alt.badge.img+51
  • Celebrity
  • Best Answer
  • February 16, 2023

The Esri Instance on the machine you're running FME on needs to be licensed. SDE reading/writing is a licensed operation opposed to a GDB where you can use either the API (free) or ArcObjects (licensed) based implementation


ioan.pintilie
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • March 17, 2023
hkingsbury wrote:

The Esri Instance on the machine you're running FME on needs to be licensed. SDE reading/writing is a licensed operation opposed to a GDB where you can use either the API (free) or ArcObjects (licensed) based implementation

Hi @hkingsbury​! Thank you for the feedback. Indeed, FME has to be installed (and licensed with the Esri Edition) over a licensed version of ArcGIS (in my case ArcGIS Desktop) installed locally. To be able to actually retrieve all the tables that I need with the geometries and Network and Relationship information, the locally installed ArcGIS solution should be the custom one distributed on all the machines.


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