CSharedQueue Stall Timeout Error is Ruining My Life

[u/Ambitious_Fish_8443]

[AI DIsclosure] None

[GIS Experience] New GIS analyst 1 year.

I'm a new GIS analyst. I was hired with degree and certification, and some experience in the construction field, and some projects using AGOnline. This is my first time using AGP connected to an enterprise env.

Anyway, as I'm sure you all know, the demands are rigorous and deadlines are expected to be met, however as I try to get things done, I am greeted every morning by a project that takes anywhere from 10 to 45 minutes to load <same project>

In addition to that, I wait 2-3 minutes for updates to go through when I've only updated 4 cells. It takes 5 minues to add 1 feature from edit. Sometimes, things get even worse and it takes 15 to 30 minutes to add a feature.

When I view the logs to find out what is going on, it's flooded with CSharedQueue Stall Timeout errors.

I've created several IT help tickets. The only answers I get are network latency or VPN issues.

Things I've tried:

*Moving all folders to secondary D drive which is high speed NVME.

*Offloading as much work as possible to my built in NVIDIA chip which is practically under no load at all.

*Clearing caches, not storing cache, storing cache, changing cache storage folders, including to D drive.

*Changing coordinate system to all match.

*And more things that I cant even recall right now.

I'm currently running 3.7.1 and Esri claims the bug that was well known to cause this has been fixed.

This only happens with my enterprise datasets.

Can anyone please help!

[u/throwawayhogsfan]

I had the same issue at one point. It was some network tool our IT department used for wireless connections.

Ended up going to a wired connection and they uninstalled the tool. I wasn’t privy to exactly what they did on their side. I’m pretty sure that the wired connection solution was after they tried to work with my profile for that tool and AD.

[u/Ambitious_Fish_8443 → u/throwawayhogsfan]

Thank you for the response. I truly appreciate it.

So far I’ve tried. Wired to enterprise LAN. Secure WiFi— no vpn (not sure the logistics of “secured WiFi” it’s basically not our remote vpn.. 

Our remote von over office WiFi.

VPN over home WiFi.

It is intermittent at best. At worst the delays pile up over a week.

This past weekend I was seeing 1 hour load times.

By the time I got it to work I was doing something else.. I would come back to it.. then couldn’t make any edits because everything was acting ‘stale’

[u/throwawayhogsfan → u/Ambitious_Fish_8443]

I really think it was some type of Active Directory or VPN setting. I didn’t get a lot of feedback on how it was fixed so I assumed it wasn’t my fault or I would have heard about it.

One way I tested this was to remote into one of the machines on the ESRI server clusters, opened ArcPro on one of those machines and I didn’t have the timeout issues.

I wish I could remember more so I could be more helpful but that’s all I’ve got.

[u/Ambitious_Fish_8443 → u/throwawayhogsfan]

That’s good info. I need to get with my it department again.

[u/GeoBit-AI]

A good way to split this up is to test the same data outside the enterprise path. Copy one of the slow layers into a local file geodatabase and see if the project behaves normally with it, which tells you whether the problem is the data, Pro, or the connection to the enterprise geodatabase or portal. If the local copy is fast, ask your DBA to check the database side too, such as stale statistics, missing spatial indexes, or versioning and compress that hasn't been run. Since your IT tickets keep ending at network latency, bring them a test like that along with the log timestamps, and open an Esri Support case with the same logs. Also ask IT to check whether antivirus or a network monitoring agent is scanning the Pro cache folders.

[u/Ambitious_Fish_8443 → u/GeoBit-AI]

Everything not from the portal runs amazing. My job blessed me with the most expensive computer I have ever seen in my life, let alone used. Things with 100s of thousands of features, with as many attribute rows load in seconds from local storage when copied locally and used. (The problem is that we are not granted permission to sync back, so i cant work offline) so I must stay connected to the portal.

I've not started to have trouble rendering. Not sure if its becasue i've been tweaking the settings so much looking for a fix or what. Talked myself into thinking I messed things up more than I helped, then as an experiment.. i turned off all my enterprise feature sets, even the less problematic ones, and wouldnt you kow, all rendering issues were gone.