After 3.3 Upgrade, FeatureLayerCollectionManager.overwrite (using a zipped GDB) fails

[MichaelSnook]

Hi all,

Having another issue with the 3.3 update.  This was working fine (and still is) on 3.2 Pro machines.  Using the FeatureLayerCollectionManager.overwrite() method fails on 3.3 machines.  I am simply passing in a path to a zipped file GDB as I have always done, no schema changes etc have been made. 

The error result is 'The data file provided does not exist or could not be accessed. -- <class 'ValueError'>'

Again this exact script works fine on a 3.2 machine.

Any ideas would be great!

Thanks - Mike

[MichaelSnook]

It appears to be a file size issue as I faked a 1k zip folder with the same name.  The script found the file and attempted to validate the file and obviously fails so at least there's progress.  Does anyone have any idea how to up the file size limitation?  The geodatabase in question is only about 65megs.

Thanks!

[TorrinHultgren2]

Getting the same behavior publishing from a service definition file. After the upgrade to 3.3, a 46MB .sd file publishes fine using FeatureLayerCollectionManager.overwrite(), but a 450MB .sd file throws that error. Never had similar issues with 3.2.

[MichaelSnook]

Does anyone at ESRI have any ideas? 

[EricKriener]

just ran into this....did you open a ticket? It's clearly a bug...

[Nils-ErikDahlsten]

I got the same problem using the arcgis python module in a script. It works with arcgis module version 2.2.0.4, but after that large zipped file geodatabases can't be used to overwrite a feature layer in AGOL.

/Nisse

[Jordi-Monk-Developer]

Today, I have encountered the same issue when running the "FeatureLayerCollectionManager.overwrite()" method with a 90 MB zipped file geodatabase. I was using Pro's Python (ArcGIS Pro 3.3.1, and arcgis.__version__ = 2.3.0).

When I ran the same script in a virtual environment where I had installed the 'arcgis' module v2.4.0, it ran without issues. From the image below, it seems that they wanted to prevent large files to be used, but not a single reference to this in the documentation.

If you are using Pro, I would suggest cloning the default virtual environment and updating the 'arcgis' module there. 

An alternative would be to install the latest version of the 'arcgis' module in a standalone, virtual environment (completely decoupled from the Pro installation).