Select to view content in your preferred language

Save Edit Error: 504 Proxy Server Bad Address - Timeout

2496
11
Jump to solution
07-14-2023 01:11 PM
GregReinecke
Frequent Contributor

Hello All,

I am running the latest build of ArcGIS Pro on a Windows 10, Dual Xeon CPU with 64GB of Ram. When I download my map from AGOL in ArcGIS Pro , select 48k points, delete them all looks fine. But when I then Save Edits after about 60 secs or so I get this error.

IMG_4821.JPG

If I delete small numbers of points and Save Edits I don't get this error. Could there be some config params I have overlooked or am I not working as locally as I think? I find it unlikely Pro doesn't all the deletions in bulk. 

Thanks in advance.

GR

1 Solution

Accepted Solutions
Robert_LeClair
Esri Esteemed Contributor

Thanks for the details Greg - this is helpful.  So in reviewing the internals of a similar case, I found the following items that may explain why you're seeing this error message.

1.  Small edits in one session work well (400-600) but not large edits (over 1000).
2.  Edits of more than 1000 cause a timeout error which means the service is not able to complete the entire task within the timeframe set on the hosting server.
3.  This has been seen in ArcGIS Pro 3.1
4.  Possible solutions are upgrading network speeds and checking the datastore utilization by your organization.
5.  Question for you - are you using the Standard data store?  One possibility is upgrading to a Premium datastore that allocates more resources for the org's functioning.

So I'm thinking this is more related to a Standard datastore configuration - can you confirm if you're using a Standard or Premium datastore.

View solution in original post

0 Kudos
11 Replies
Robert_LeClair
Esri Esteemed Contributor

Hi Greg!  What release of ArcGIS Pro are you using?  The reason I ask is because there was non-reproducible BUG-000149351 - In ArcGIS Pro, deleting features fails to delete all records with the ArcGIS Online based hosted feature services.  The bug was closed due to Improvements are made to the applyEdits operation in ArcGIS Pro 3.0 and this issue no longer occurs.  The team improved the AppyEdits limit functionlity in ArcGIS Pro 3.1 as well.

0 Kudos
GregReinecke
Frequent Contributor

Hello Robert,

I'm running ArcGIS Pro 3.1.2.  Could it be my process?  My process is to

1. open AGOL and select my webmap;

2. then choose to edit it with ArcGIS Pro by downloading the ArcGIS Pro Portal Item and then; 

3. delete the features from there in Pro.

I do this so I can overwrite the webmap back into AGOL and not have to reset a bunch of stuff in experience builder which uses the webmap. There are about 48K points with about 10 columns in the associated table.

Thanks so much.

0 Kudos
Robert_LeClair
Esri Esteemed Contributor

Maybe.  In ArcGIS Pro, can you access the web layer using the Catalog Pane, add it to a Map View in ArcGIS Pro and do your select/delete there IF you have editing capabilities enabled for the web layer vs. the download to ArcGIS Pro?

0 Kudos
GregReinecke
Frequent Contributor

Thanks Robert.

As I try to sort this out I don't want to wrap us around the axel but wouldn't that still put the pressure on the remote connection to the data and likely cause the original error?

I'll try to frame it another way and then lay it to rest 🙂.  I'd like to completely overwrite the feature layer without losing the formatting of the symbols or requiring me to reset things in ExB if a feature layer changes in the webmap driving my ExB dashboard. Thats why I ran ArcGIS Pro from the webmap using the ArcGIS Pro Portal Item, which does work for smaller edits and deletes.

I noticed when I reviewed the properties > source of the layer its source is https://services8.arcgis.com/m2qD********** vs a local address on my machine. If local I'm sure it would allow a 48k point deletion. If I got the data local and replaced the new features how could I then reset the source back to the original https://services8.arcgis.com/m2qD*********** as the layer to then overwrite the webmap? 

Sorry but I thought there might be a path for this and likely there is I just haven't figured it out.

GR

0 Kudos
Robert_LeClair
Esri Esteemed Contributor

Thanks for the details Greg - this is helpful.  So in reviewing the internals of a similar case, I found the following items that may explain why you're seeing this error message.

1.  Small edits in one session work well (400-600) but not large edits (over 1000).
2.  Edits of more than 1000 cause a timeout error which means the service is not able to complete the entire task within the timeframe set on the hosting server.
3.  This has been seen in ArcGIS Pro 3.1
4.  Possible solutions are upgrading network speeds and checking the datastore utilization by your organization.
5.  Question for you - are you using the Standard data store?  One possibility is upgrading to a Premium datastore that allocates more resources for the org's functioning.

So I'm thinking this is more related to a Standard datastore configuration - can you confirm if you're using a Standard or Premium datastore.

0 Kudos
TomKukitz
Deactivated User

TomKukitz_0-1690891610816.png

I am sorry, but those suggestion should not be categorized as a solutions. The issue should be fixed!!!! This software is very expensive and this should not be an issue! Upgrade the data store on AGO is: Standard Free, Premium - 1700$/month. Do you think we are made of money!

Please post real solutions not workarounds! You should remove your post!

Tom

Robert_LeClair
Esri Esteemed Contributor

Respectfully, my response is an explanation of the software issue/error message that Greg asked earlier and is not a bug in the software.  It's just the way it's written/developed by the Esri developers.  I work in Esri Training Services as a Principal Technical Lead/Senior Instructor teaching customers how to use the ArcGIS software and have zero say in development processes, cost of software development and more.  I do my best to answer customer questions and post explanations/solutions to questions asked on the Esri Community.  I'm sorry my post is not the solution you require.  My recommendation is you contact your Esri Sales Representative to have additional conversations with them regarding pricing structures for the varied software products. 

0 Kudos
TomKukitz
Deactivated User

Oh but it is a bug in the software. I had the same issue and just uninstalled 3.1 and reinstalled 3.0 and now I don't have this issue anymore!

0 Kudos
Robert_LeClair
Esri Esteemed Contributor

Hi Tom - so I'm reading your Esri Support Services case and see that yes, it is a BUG at 3.1 and uninstalling 3.1 and installing 3.0 does fix the problem you mentioned in your case.  I suspect once the BUG is logged with the team, then it will be reviewed and patched.