Skip to main content
Question

Writing to file geodatabase is not working anymore after Windows update


maarten
Participant
Forum|alt.badge.img+3

I have been using a workbench for months which writes to a file geodatabase using the 'Esri Geodatabase (File Geodb ArcObjects)' writer. I am using FME 2016.1.3.1 64-bit (I was using a previous version of FME 2016.1 and was hoping that an update to this most recent version might solve my issue) on a computer where ArcGIS 10.4.1 with background geoprocessing and ArcGIS Pro 1.3 is installed. Coincidence or not, since the latest updates for Windows the workbench is not working anymore. In the image below you can see which updates have been installed.

0684Q00000ArFMyQAN.png

On my computer runs Windows 7 Enterprise Service Pack 1.

The error I get in FME is: 

Unable to perform any licensing related tasks.  This is a 64-bit version of FME which requires a 64-bit version of ArcGIS Server. Or download and install a 32 bit version of FME. Refer to this this article http://fme.ly/qua for more details 

Following the link in the error message I read that I need ArcGIS Pro or ArcGIS Desktop background processing, but that is already installed and working. I can still add a 'Esri Geodatabase (File Geodb ArcObjects)' writer. This writer is not greyed out.

Any help on solving this problem is welcome.

Kind regards, Maarten.

10 replies

david_r
Celebrity
  • December 16, 2016

itay
Supporter
Forum|alt.badge.img+17
  • Supporter
  • December 16, 2016

and in addition contact Safe support.


maarten
Participant
Forum|alt.badge.img+3
  • Author
  • Participant
  • December 16, 2016
david_r wrote:
Thanks david for your suggestion. I already had a look at it, but according to that infomation I have compatible versions of FME en ArcGIS.

 

 


maarten
Participant
Forum|alt.badge.img+3
  • Author
  • Participant
  • December 16, 2016
itay wrote:

and in addition contact Safe support.

Done! I hope they have some solution.

 

 


david_r
Celebrity
  • December 16, 2016

Also check the currently active ArcGIS license using the ArcGIS Administrator tool to verify that you have activated a 64-bit license.

Also consider setting the ESRI_SOFTWARE_CLASS environment variable, see here: http://resources.arcgis.com/en/help/install-guides/license-manager/10.1/index.html#/Using_the_License_Manager_with_WTS_Citrix/00790000001p000000/


maarten
Participant
Forum|alt.badge.img+3
  • Author
  • Participant
  • December 16, 2016
david_r wrote:

Also check the currently active ArcGIS license using the ArcGIS Administrator tool to verify that you have activated a 64-bit license.

Also consider setting the ESRI_SOFTWARE_CLASS environment variable, see here: http://resources.arcgis.com/en/help/install-guides/license-manager/10.1/index.html#/Using_the_License_Manager_with_WTS_Citrix/00790000001p000000/

When my workbench still worked, I could see in the logging that it used the ArcGIS Pro license (it said something like 'version = 1.3'. So, that would suggest that it would not matter what license is used for ArcGIS Desktop (which is actually using an Advanced (ArcInfo) Concurrent Use license and background geoprocessing is working).

 


maarten
Participant
Forum|alt.badge.img+3
  • Author
  • Participant
  • December 16, 2016
I just installed the 32-bit version of FME in which the workbench works well. But it seems to be a bit slower than in the 64-bit version, so I am still hoping for a solution.

 


  • December 19, 2016

This may be because,ArcGIS is on 32-bit.


Forum|alt.badge.img+4
  • January 12, 2017

I am having a similar issue, where FME either hangs or crashes at this point on the 64-bit version of FME:

The ArcObjects license 'Advanced' is being selected from the Windows registry

It never finishes executing my FME script and updating the table in SDE. It does however work in FME 32-bit, but is much slower because of the upfront processing I'm doing. With 72GB of RAM it's not real efficient for me to use the 32-bit version, but is a temporary workaround.

@maarten did you ever find a solution?


maarten
Participant
Forum|alt.badge.img+3
  • Author
  • Participant
  • January 13, 2017

Just as you, I am using 32-bit FME right now. I have asked FME support for help, but that did not lead to a solution yet. But that is also due to the fact that I still have to deliver them some extra information. If you contact FME support yourself, you might add a reference to my case: C122091.


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