Skip to main content
Question

Error reading large point file from ArcGIS Online or ArcGIS Enterprise.

  • November 17, 2025
  • 3 replies
  • 53 views

peterhearns
Contributor
Forum|alt.badge.img+7

I’ve been trying to read a layer that has 16.1 million points and 7 fields into FME Form.  After 10-12 minutes I get the following long-winded 504 error:

ArcGIS Online Feature Service Reader: Could not connect to server. Check that you are connected to the internet and that no firewall is blocking outbound connections. The error was 'HTTPSConnectionPool(host='services6.arcgis.com', port=443): Max retries exceeded with url: /PZSz9p6KxGzrnOUT/arcgis/rest/services/PHH_43_FullGeo/FeatureServer/0/query?f=json&token=3NKHt6i2urmWtqOuugvr9TpluUwD-K0TsTS8M3vWY6dKMXWdi_tH3WBIMlCuSgEpXHlYlhwKYwGuuQlZCRtBPNkiJDV5CIz_E4rWysxVYMtf2LCRDhJuovK2hsyIHZ78x99hsJVaIrIbEUFTrqdJzb_qpnp_vjly88FyTaaYsMGr8ItOJpumuJhFox3VA6NXh9o64ZVluadt9ApVCcvpmElqPgAf1TPFnSerF1uG4nnxdUFYdsd3QRvQmGuNsAYYh7s2BHXFM6Rh9P7H5jTyxQ.. (Caused by ResponseError('too many 504 error responses'))'

 

Python Exception <FMEException>: FMEException: 926856: ArcGIS Online Feature Service Reader: Could not connect to server. Check that you are connected to the internet and that no firewall is blocking outbound connections. The error was 'HTTPSConnectionPool(host='services6.arcgis.com', port=443): Max retries exceeded with url: /PZSz9p6KxGzrnOUT/arcgis/rest/services/PHH_43_FullGeo/FeatureServer/0/query?f=json&token=3NKHt6i2urmWtqOuugvr9TpluUwD-K0TsTS8M3vWY6dKMXWdi_tH3WBIMlCuSgEpXHlYlhwKYwGuuQlZCRtBPNkiJDV5CIz_E4rWysxVYMtf2LCRDhJuovK2hsyIHZ78x99hsJVaIrIbEUFTrqdJzb_qpnp_vjly88FyTaaYsMGr8ItOJpumuJhFox3VA6NXh9o64ZVluadt9ApVCcvpmElqPgAf1TPFnSerF1uG4nnxdUFYdsd3QRvQmGuNsAYYh7s2BHXFM6Rh9P7H5jTyxQ.. (Caused by ResponseError('too many 504 error responses'))'

I published the layer using ArcGIS Pro and can read the Feature Layer using Pro as well.  I tested my FME connection using other layers in AGE and AGOL and also used the new reader and the older reader and they all work fine.  I did the same test in AGE and AGOL.  In AGE the ArcGIS Server cpu goes to 100% and stays there or I get this error: 

In AGOL I get the long winded error above.

 

Any possible issues that I might need to investigate?  As noted, I can read the layer again using ArcGIS Pro without any issues and I can even view it in the webmap.

Thank you,

Peter

Using: AWS EC2 - r7i.2xlarge - Windows Server 2022

FME Form 2025.1.2, ArcGIS Pro 3.5.4 and AGE 11.5

Note: I’ve tried the test from this post 

and the first two fail and the third does work.

3 replies

crystalwang
Safer
Forum|alt.badge.img+14
  • Safer
  • November 18, 2025

Hi ​@peterhearns,

Thanks for posting your question on the FME Community!

When working with large layers from ArcGIS Online, timeout errors usually happen because the service is being asked to return more data than it can handle in a single request. Here are a couple of things to check:

On the FME side, reduce the Features Per Request parameter to a smaller number to improve connection stability. You can find this in the Advanced settings in the reader. Somewhere around 1,000 features per request usually works well. If you can share a screenshot of your reader parameters, that could help as well.

If you have access to the ArcGIS service properties, you can also increase the “Maximum number of records returned by the server” setting (maxRecordCount). Setting it higher can help the service handle larger queries, but may incur performance hits.

Please let me know if this information helps!


peterhearns
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • November 18, 2025

Hi ​@peterhearns,

Thanks for posting your question on the FME Community!

When working with large layers from ArcGIS Online, timeout errors usually happen because the service is being asked to return more data than it can handle in a single request. Here are a couple of things to check:

On the FME side, reduce the Features Per Request parameter to a smaller number to improve connection stability. You can find this in the Advanced settings in the reader. Somewhere around 1,000 features per request usually works well. If you can share a screenshot of your reader parameters, that could help as well.

If you have access to the ArcGIS service properties, you can also increase the “Maximum number of records returned by the server” setting (maxRecordCount). Setting it higher can help the service handle larger queries, but may incur performance hits.

Please let me know if this information helps!

 

 

Thanks for your suggestion Crystal.  Unfortunately we have our ArcGIS Server set to have Maximum records returned by server = 2000 (We also tried 1000 and 4000) and I tried the FME readers using 2000, 1000, 100 and 20 and always received the same results.  In AGOL the reader fails after 10-12 mins and in AGE the Server CPU goes to 100% and stays there and then fails after 30 minutes (1800 second timeout).


crystalwang
Safer
Forum|alt.badge.img+14
  • Safer
  • November 18, 2025

Hi ​@peterhearns,

Thanks for the additional context. I’ve reached out to a knowledgeable colleague and based on this information, perhaps the process may be unable to complete within the timeout duration set on the hosting server. 

To address this, please consider increasing the timeout duration by accessing the ArcGIS Server Manager. The settings can be found by clicking on the Manage Services, Map Service, Select Pooling, and the Specify Service Timeouts Section. You can find more information here: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/tuning-and-configuring-services.htm.

(Location of the service timeout settings for an example Feature Service)

After increasing the timeouts, you might also want to adjust the Features to Read parameters in your FME reader to control the Start Feature and Max Features to Read. This lets you read the layer in smaller chunks rather than all at once, which can help avoid timeouts and reduce load on the server.

Let me know if this helps!