Skip to main content
Question

FME Server 2017 not picking up ArcMap 10.5.1 license - FME Desktop works ok


annette2
Contributor
Forum|alt.badge.img+10

Hi,

We upgraded from 2015 Server to 2017 on our test server. Desktop picks up the ArcMap 10.5.1 license. I can open ArcMap on the machine.

But FME Server 2017 does not recognise the license. I test with a simple write to a local file geodatabase and I get the following below.

Any ideas how to get Server 2017 to recognise the ArcMap license?

Thanks,

Annette

Writer `GEODATABASE_FILE_1' of type `GEODATABASE_FILE' using group definition keyword `GEODATABASE_FILE_1_DEF'

FME API version of module 'GEODATABASE_FILE' matches current internal version (3.8 20170315)

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

The Esri Product license used by this machine does not include licenses for the 'Basic' licensing level

Unable to perform licensing related tasks. Please ensure that ArcGIS is correctly installed

A fatal error has occurred. Check the logfile above for details

A fatal error has occurred. Check the logfile above for details

Closing the Geodatabase writer

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Feature output statistics for `GEODATABASE_FILE' writer using keyword `GEODATABASE_FILE_1':

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Features Written

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

==============================================================================

Total Features Written 0

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

A fatal error has occurred. Check the logfile above for details

3 replies

david_r
Celebrity
  • February 1, 2018

We've seen something similar with one of our clients. After much back and forth, including Safe support, we were able to pin the error to a recent Windows 10 security update.

You may want to run the system information batch file provided by Safe and forward it to your FME reseller so they can work with Safe and see if it's the same issue: https://knowledge.safe.com/articles/714/general-troubleshooting-gathering-system-informati.html


annette2
Contributor
Forum|alt.badge.img+10
  • Author
  • Contributor
  • February 1, 2018
david_r wrote:

We've seen something similar with one of our clients. After much back and forth, including Safe support, we were able to pin the error to a recent Windows 10 security update.

You may want to run the system information batch file provided by Safe and forward it to your FME reseller so they can work with Safe and see if it's the same issue: https://knowledge.safe.com/articles/714/general-troubleshooting-gathering-system-informati.html

Good idea. It is in fact a Windows 8 test machine. We will run this and send to Safe. We are setting up a proper test server but the machine isn't ready yet.

 


annette2
Contributor
Forum|alt.badge.img+10
  • Author
  • Contributor
  • February 1, 2018
david_r wrote:

We've seen something similar with one of our clients. After much back and forth, including Safe support, we were able to pin the error to a recent Windows 10 security update.

You may want to run the system information batch file provided by Safe and forward it to your FME reseller so they can work with Safe and see if it's the same issue: https://knowledge.safe.com/articles/714/general-troubleshooting-gathering-system-informati.html

Tried another virtual machine with the same OS and it is working :)

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