The Create Watershed Polygon tool when published as a geoprocessing service fails to execute with custom rasters (flow accumulation, flow direction) and could be due to the size of these rasters.

Información adicional

Solución alternativa

When consuming a geoprocessing service through ArcGIS Desktop, if the task contains input parameters that require datasets to be provided or files uploaded, there is a size limitation. The limitation depends on the uploaded data type.

If the input data type is raster or file, the upload size limit is 64 MB, which is the default heap size. If the size of the upload data or file is larger than 64 MB, error messages are returned from the Result window and service crash information from ArcGIS Server logs after uploading.

Changing the heap size at the service level provides better performance than changing the heap size from the Server level. From ArcGIS Server 10.7 onwards, the heap size can be set at the service level. The default size for each service is 64 MB. The actual heap size needed for the geoprocessing service would depend on the size of the raster being used as an input to the geoprocessing service. Also, it is recommended to increase the heap size in the progression of powers for the number two. For example, 64,128,256,512,1024 and onwards.

http://desktop.arcgis.com/en/arcmap/latest/analyze/sharing-workflows/geoprocessing-service-settings-advanced.htm#GUID-17815A98-2756-486F-AC2D-22672E0FCA28

http://desktop.arcgis.com/en/arcmap/latest/analyze/sharing-workflows/large-dataset-upload-and-download-considerations.htm#ESRI_SECTION1_610C13B4184E4C7EB0C689B86AEFBDC0

Pasos para reproducir