The Reader Online

0 views

Skip to first unread message

Colette

unread,

Aug 3, 2024, 4:29:32 PM8/3/24

to lunadodup

On this page you can find links to accessibility help articles that are written for people who use screen readers with SharePoint Online. To find information on how to create SharePoint sites that are accessible to people with disabilities, refer to Make your SharePoint site accessible to people with disabilities.

The best answer is to test in real screen readers, ideally by getting real users as they know how to use these tools. Consider contacting your local blind association and see if they offer testing services.

So we have some workbenches (FME 2018.1.1; 20181203 - Build 18578 - WIN64) that either read or write to AGOL after performing a bunch of operations on the data. These workbenches were working fine up until a week ago, when all of a sudden they started throwing a very generic 503 error message and failing completely.

We've been having issues with our organization's ArcGIS Online portal for the last couple of days (layers being randomly dropped from maps, apps refusing to load) and I'm starting to think that their December 2018 AGOL update messed some things up, including the way FME's readers/writers communicate with it. Is anyone else having trouble working with AGOL lately?

Though we were able to reach the portal through the browser, it kept dropping layers randomly from the maps and the apps. This is why I was wondering if some instability in ArcGIS Online was somehow affecting the way FME communicated with it.

Anyway, we haven't had too much trouble with it the last couple of days (we might get a 503 error the first time we try a workflow, but it'll work on a subsequent attempt right afterwards). It was just really bad when I posted this question, it must have failed like ten times before I decided to create a non-AGOL workflow.

I've been seeing similar issues with a customer over the last few days (they have been seeing it over January). We have been getting the same 503 errors when trying to do reads or inserts/updates and deletes into layers via the AGOL FME Reader/Writer. This has happened with both FME 2016 and FME 2018.1 (build 18578). It's also intermittent, a Workspace will fail, but restart it straight away and it will run fine.

Two things that "seemed" to help were reducing the number of features read/written so that the transactions were smaller, and also using the FeatureHolder transformer to force FME to completely read all the data on run, and then have all the data available available to write etc. There's a performance hit but reducing the number of simultaneous actions against the ESRI connection "seemed" to give better stability.

I've not had any issues with FME reading/writing to AGOL with other users in the last week so it doesn't appear to be an issue with the FME reader/writer and it does sound like there is an issue with the services3.arcgis.com end point.

And yes it has a higher chance of happening when you do several queries in a row, in our case it happens almost 100% of the time since we're gathering the attachments of a layer in batch, and you must do a separate attachment query for each feature.

I do believe it's an overload on the services3 machine, it's an old server that most sample layers from ESRI are hosted in, if you create a new AGOL account right now it will be at services9 (as of today), which will give you no errors.

I'm sorry to hear about all of this. It's actually puzzling how hard it is to find any resources on this specific issue. For a while back then when I made wrote my initial post it felt like we were the only ones having this problem.

I'm having slightly different errors when trying to write to AGOL using FME (504, Memory Pressure) but it sounds like my problem is similar to the ones described in this thread (see my other question for details). I only started working with FME and AGOL in December so I can't say if my workbench would have worked before.

In my case, the workbench usually works fine if I run it while in FME and hit the "Run Translation" button. If I try to use Windows Task Scheduler: sometimes the workbench successfully finishes but other times it fails and returns various errors.

Our map services are stored on the services3 AGOL instance. I've tried some suggestions from FME Support and others without success (reduce features written, FeatureHolder, reduced number of transformers, reauthenticate, etc).

Hi @bfausel, Do you have a support case open with us for this now? If you don't, can you please create one using this form: -a-problem/ We can help you dig into this some more and see if we can narrow down the source of the problem you're seeing.

Hi, we did the same and apparently it was due to "confluence of several factors which each independently push the hive slightly closer to these 503 errors" (they've not disclosed what these are). ESRI have been working to fix these factors and we have found Hive 3 to be much more stable since. So hopefully its related and you'll start to see the same stability!

Hi Laura, yes I do have a support case open and they have suggested a number of things to try. I have been working through the suggestions as time permits. There was a lot to digest though. I will post an update if one of the solutions work.

We started getting a 404 error that kept crashing our AGOL processes a few weeks ago. Sometimes they'd write fine while other times they'd just throw the error, claiming they couldn't find the URL they were trying to access.

We opened a ticket with ESRI and they gave us the usual, non-committal replies ('dashboard shows the systems are running fine', 'have you contacted SAFE instead?', etc)...but then they supposedly 'fixed a bug' (they haven't disclosed what the bug was, but I suspect it's related to the one you mentioned) and the problem went away (or seems like it has so far).

@gavinpark3 @rinfante Still working through these issues with esri support. We were able to reproduce 502 errors, but weren't ever able to reproduce the 503 errors as of yet. The weird thing is that we stopped seeing the bulk of the 503 errors on 2/20 (although we only saw 2 on the 26th). They did have me create an index on the service for a field that I query with my FME job, although that didn't work.

I have a sneaking suspicion that what ever "it" is, is related to the data store and/or indexes. We get another error (either a ConnectionResetError or ConnectionAbortedError) quite a bit which we found is resolved when we rebuild the spatial index.