Question

FME Server not able to access ArcPro

mark_zl 
2021-7-8 08:39:28 | Unable to perform any licensing related tasks. Please check your Esri ArcGIS Compatibility setting. This 64-bit version of FME requires 64-bit Background Geoprocessing, ArcGIS Pro or ArcGIS Server. Refer to this this article http://fme.ly/qua for more details
2021-7-8 08:39:28 | A fatal error has occurred. Check the logfile above for details
 

When I run a workspace on FME server I get the error above. When It is run locally on FME Desktop it works.

 

I Read the help on: https://community.safe.com/s/article/geodatabase-formats-missing-greyed-out-or-have-unm

 

And have installed ArcPro, but now we are getting an error

 

48	2021-7-8 10:44:59 | Opening the Esri Geodatabase reader
49	2021-7-8 10:45:00 | The ArcObjects license 'Advanced' is being selected from the ESRILicenseInfo ArcObjects call
50	2021-7-8 10:45:00 | The Esri Product license used by this machine does not include licenses for the 'Advanced' licensing level
51	2021-7-8 10:45:00 | Unable to perform any licensing related tasks. Please check your Esri ArcGIS Compatibility setting. This 64-bit version of FME requires 64-bit Background Geoprocessing, ArcGIS Pro or ArcGIS Server. Refer to this this article http://fme.ly/qua for more details
52	2021-7-8 10:45:00 | A fatal error has occurred. Check the logfile above for details

 I checked the ESRI compatibility

 

We are running ArcPro 2.7 with FME Server 2021.0.1

 

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

ArcGIS Pro 2.7.x    FME 2020.2.2 or higher 64 bit only

 

2 replies

gazza
Badge +5

Are the FME Server engines running under the same user account that ArcPro was installed by and licensed for? See https://community.safe.com/s/article/Using-ArcGIS-Pro-with-FME-Server#useracount

mark_zl

Thanks gazza,

 

What we did, was add a new user and and gave the user an arcpro licence, plus the steps below:

 

To Run the FME Server System Services Under Different Accounts

  1. (FME Server Engines service only) If your FME Engines are installed separately from the FME Server Core (Adding FME Engines on a Separate Machine), you may need to update the user account that runs the FME Engines to provide read/write access to the FME Server System Share and FME Server installation directory. Ensure that account has the necessary permissions on the FME Server Core and FME Server Database machines. For more information, see Running the FME Engines Under a Different Account.
  2. Open the Windows Services:

Select Start > Control Panel > Administrative Tools > Services.

Or

Run services.msc.

  1. In the Services list, right-click FME Server Application Server, FME Server Core, or FME Server Engines, and select Properties.

Note: The FME Server Core service is dependent on the FME Server Database service, which must remain under the Local System account.

  1. In the Properties dialog, click the Log On tab.
  2. Select This account, and specify a user account and password that provides permissions to the FME Server System Share and FME Server installation directory. If you are updating the FME Server Engines account, make sure the account corresponds to the user you specified in Step 1.
  3. If Cross-Origin Resource Sharing settings have been updated, and you are updating the FME Server Engines account, grant Write permissions on file cors.properties to the user you specified in Step 1. This file is located in the \\localization\\clients folder of the FME Server System Share. For more information, see Directory and Account Permissions. (You must have direct access to this file; it is not available from the Resources page of the Web User Interface.)
  4. Click OK.
  5. Restart the FME Server System Services you updated.

 

 

Reply


Community Stats

28,670
Posts
109,365
Replies
36,531
Members
Terms & ConditionsCookie 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.