Hello, I'm having a problem when trying to write records from an ESRI file geodatabase feature class to an ArcGIS Online hosted feature service. The error message in the log is as follows: ArcGIS Online Feature Service Writer: Encountered an unexpected error. The error code from the server was '504' and the message was: 'Your request has timed out.'. Details: '' Any ideas on how to resolve this issue? Thanks.
Solved
FGDB to AGOL Connection Times Out
Best answer by markatsafe
@firegis In 2019.1 and higher we've added (so not in Esri Data Interoperability Extension yet) we have added some smarter timeout re-try for AGOL based readers/writers upon encountering an HTTP 500/502/503/504 responses. Hopefully this will address you timeout issues.
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+18- Supporter
Hi, try reducing the features per request to 100-200 from the default 1000. Log a support call with Esri and provide the service URL so they can see the cluster being used. Provide a log file so they know the timestamp.
@firegis In 2019.1 and higher we've added (so not in Esri Data Interoperability Extension yet) we have added some smarter timeout re-try for AGOL based readers/writers upon encountering an HTTP 500/502/503/504 responses. Hopefully this will address you timeout issues.
markatsafe wrote:
@firegis In 2019.1 and higher we've added (so not in Esri Data Interoperability Extension yet) we have added some smarter timeout re-try for AGOL based readers/writers upon encountering an HTTP 500/502/503/504 responses. Hopefully this will address you timeout issues.
Hi markatsafe. I've been struggling all day with this issue. FME has been uploading features, timing out and 're-trying' which in turn has been adding to the feature hosted layer. The log shows no error and reports the incorrect number of written features on success when in fact it's duplicating data. To make matters worse, AGOL interprets these as new features and assigns a new obj Id instead of overwriting.
Reducing the features per request to 50 helped enormously.
I've been using FME for over 8 years and this has been my most frustrating day. Apologies for the rant, I've never posted on here, but thought this could help others experiencing the same problem
Cheers
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.