Sounds like a fix was implemented in 2019.2 19731 for this.
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
Did you try with FME 2019? This version fixed the issue for us.
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 ?
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.
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!
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:
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.
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 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
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!
Must have been this fix... Still working with SAFE on ArcGIS Online issues that we've been having.
ARCGISPORTALFEATURES: Fix KeyError with ArcGIS 10.6.1; better handling of access token expiry.
Looks like it is fixed in the 2019 beta :)
Was this ever solved? We are having the same issue with Portal for ArcGIS Feature Service?
Happy to see that I'm not the only one getting invalid tokens from ArcGIS Online.
We've discovered recently that ArcGIS Online generates by himself new tokens for some Map Services after some weeks, making our FME scripts not operational.
So I think it's ESRI's fault, I can't imagine how FME could change the AGOL token, but it's a good thing they work both on this.
Thanks for the update and Merry Christmas to you!
Update: We have opened a ticket with ESRI and SAFE after getting lots of 401's and other random errors relating to invalid tokens with ArcGIS Online URLs. SAFE's developers are working with ESRI to determine what side this is occurring on and ultimately how this issue can be resolved. Hopefully we'll be able to figure out more soon! FYSA @philippeb @mapper99 @xilef @dmatranga
Do you have any insight into this? It appears like it's a bug with ArcGIS Online since it is able to get a token, and it happens randomly.
Maybe if you recreate the connection over there for the user isn't working it would work after that.
Even if the connection is published, because of ArcGIS Online security, it's not enough.
After publishing your AGOL connexion, in FME Server you'll have to go to Web Connections, click on the AGOL connection and authorize a second time the connection with your AGOL informations.
After that it should work indefinitely. Be aware that if you recreate your AGOL connection when republishing, you'll have to do this process once again.
It looks like it's working for me so far.
I'll let you know if I learn anything else.
I opened a case with my resaler about this, I'll post an answer when I'll have one.
We get something similar when we try to read, although we don't get a URL:
| Python Exception <HTTPError>: 401 Client Error: Unauthorized for url: ' |
| A fatal error has occurred. Check the logfile above for details |
Ideas on this one? Seemed kinda related.
Tried to re-upload the workspace and updated the credentials, and that seemed to help for maybe the first job after I uploaded it, but it's back to throwing this error.
May I ask you to please try creating a fresh web connection to AGOL (something other than the existing Daniel.Matranga Esri ArcGIS Online one that currently exists), and then try that in the reader to see if this makes a difference? Have you run into this issue before with the AGOL reader?