Skip to main content

One of my workspaces recently broke because FME can't read in the features from AGOL. I'm running Win 7 x64 and FME Beta Build 18198. Has anyone else experienced this issue?

When trying to inspect the AGOL feature layer, this is the error I receive:

ArcGIS Online Feature Service Reader: Requesting portal information

Updating access token for 'Daniel.Matranga Esri ArcGIS Online'

JSON Message: {"error":{"code":498,"error":"invalid_request","error_description":"refresh_token expired","message":"refresh_token expired","details":t]}}

JSON Error: JSONObjecte"error"] not a string.

Unable to update access token for 'Daniel.Matranga Esri ArcGIS Online'

Updating access token for 'Daniel.Matranga Esri ArcGIS Online'

JSON Message: {"error":{"code":498,"error":"invalid_request","error_description":"refresh_token expired","message":"refresh_token expired","details":o]}}

JSON Error: JSONObjectd"error"] not a string.

Unable to update access token for 'Daniel.Matranga Esri ArcGIS Online'

Python Exception <HTTPError>: 401 Client Error: Unauthorized for url: https://www.arcgis.com/sharing/rest/portals/self?f=json&token;=mFrTCtBJ0dRkfmL1YoMsBK_PxQdQAY1qTADLSdkr_60oHGLclWOlWLbWfZnTRC4fHfunnCV2busZDdIVJTSQNa2wZ4-zI9r19Z_uAUpo2qhpX_PT2YsSu6fihbccgXq7eHkdw5sGA0c7Xrx8XlOrf3pIlQ26Ank2LuVmy2gDu2rDIGpEptDeERW0pGkv7eKzQkdMEZT02orXvk8Aq-tJEakmEW1wxiXLpm8K_LYWhx-Sy90tssJnEMm-4k2TZg9C

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

Failed to obtain any schemas from reader 'ARCGISONLINEFEATURES' from 1 datasets. This may be due to invalid datasets or format accessibility issues due to licensing, dependencies, or module loading. See logfile for more information

UniversalReader -- readSchema resulted in 0 schema features being returned

Still having this issue. Always having to right click the web connection and reauthenticate....then it works fine for a few weeks....but like others in this post said...the issue is then when you are doing this in scheduled tasks on servers...not very efficient ... and don't have access to prod! If anyone has some news on this let me know!

I think by default the max is set to -1 (which is basically forever). Our org has it set to that and we are running into the same issues (401 errors). We have been experiencing this on FME Server off and on again. Seems like FME should know when the refresh token expires and should re-authenticate it automagically. Have had it happen only once since we updated to 2019 and are waiting for it to happen again so we can determine if there's a pattern/persistent problem in the latest version. @carsonlam


I think by default the max is set to -1 (which is basically forever). Our org has it set to that and we are running into the same issues (401 errors). We have been experiencing this on FME Server off and on again. Seems like FME should know when the refresh token expires and should re-authenticate it automagically. Have had it happen only once since we updated to 2019 and are waiting for it to happen again so we can determine if there's a pattern/persistent problem in the latest version. @carsonlam

Hi runneals.

 

Can you tell me where did you see that your Org has it set to forever on ArcGIS online. I would like to check if we are the same....but have no clue where this setting is. Thanks

 


Hi runneals.

 

Can you tell me where did you see that your Org has it set to forever on ArcGIS online.  I would like to check if we are the same....but have no clue where this setting is.  Thanks

 

I was given this link and told to look under Authorization Endpoint for more inforation about the refresh tokens.

Looking at that I found that you'll have to generate your token and then use the self call to get your org settings:

- Generate token:

 

 http://www.arcgis.com" target="_blank">https://www.arcgis.com/sharing/generateToken?f=json&username=&password=&referer=http://www.arcgis.com

 

 - Self Call: http://www.arcgis.com/sharing/rest/portals/self?f=pjson&token=*

 

Which led me to find the setting:

  "maxTokenExpirationMinutes": -1,

I was given this link and told to look under Authorization Endpoint for more inforation about the refresh tokens.

Looking at that I found that you'll have to generate your token and then use the self call to get your org settings:

- Generate token:

 

 http://www.arcgis.com" target="_blank">https://www.arcgis.com/sharing/generateToken?f=json&username=&password=&referer=http://www.arcgis.com

 

 - Self Call: http://www.arcgis.com/sharing/rest/portals/self?f=pjson&token=*

 

Which led me to find the setting:

  "maxTokenExpirationMinutes": -1,

Hi runneals

 

SO I've tried the urls you gave me and the settings also tells me my tokens can be set to -1 (forever)....even if ESRI's techsupport (Canada) told me you could not set this thing...they just don't know about it.  But it remains that even if I asked for an non expiring refresh token...it still expires after a while...can't put my finger on the time interval BUT THE FACT IS THAT IT EXPIRES....and leaves my scripts broken!

 

I hope Safe finds a solution for this...real real issue for us.  I will submit another case!!!  AGAIN!

 

 


Hi runneals

 

SO I've tried the urls you gave me and the settings also tells me my tokens can be set to -1 (forever)....even if ESRI's techsupport (Canada) told me you could not set this thing...they just don't know about it. But it remains that even if I asked for an non expiring refresh token...it still expires after a while...can't put my finger on the time interval BUT THE FACT IS THAT IT EXPIRES....and leaves my scripts broken!

 

I hope Safe finds a solution for this...real real issue for us. I will submit another case!!! AGAIN!

 

 

Hi @douks851,

What version of FME are you using? We are now using FME Server 2019 and ArcGIS Enterprise 10.6.1 (mainly Portal for ArcGIS). By upgrading to FME 2019 the authentication issue was resolved for the Portal for ArcGIS readers/writers. We had tested with 2017 and 2018 without success. The 2019 beta did work and we have recently upgrade to FME Server 2019.

We still had authentication issues calling a service with the Geocoder transformer but we resolved this using a httpcaller transformer.


I encountered the same problem with ArcGISonline connection even through my username and password for the AGOL account remains the same and unchanged. I am using FMEserver 2018.1 and latest AGOL. I see that Safe and Esri are working together on this issue. Any more update on this issue ?


I encountered the same problem with ArcGISonline connection even through my username and password for the AGOL account remains the same and unchanged. I am using FMEserver 2018.1 and latest AGOL. I see that Safe and Esri are working together on this issue. Any more update on this issue ?

Did you try with FME 2019? This version fixed the issue for us.


Hi @douks851,

What version of FME are you using? We are now using FME Server 2019 and ArcGIS Enterprise 10.6.1 (mainly Portal for ArcGIS). By upgrading to FME 2019 the authentication issue was resolved for the Portal for ArcGIS readers/writers. We had tested with 2017 and 2018 without success. The 2019 beta did work and we have recently upgrade to FME Server 2019.

We still had authentication issues calling a service with the Geocoder transformer but we resolved this using a httpcaller transformer.

Think I may have noticed this issue pop up again (will be investigating next week). Also @annette2 I strongly suggest against using FME to geocode points, as it doesn't support bulk mode. It currently submits 1 record at a time which is much slower than using ArcGIS Desktop to geocode... and doesn't crash a geocoding server :P


Sounds like a fix was implemented in 2019.2 19731 for this.


Reply