We are facing a crisis as we are unable to successfully publish hosted imagery layers on a consistent basis since the new release of ArcGIS Online last night. Are there any fixes coming to this? We keep getting "Generic Server Error". It was publishing fine before the updates.
Solved! Go to Solution.
Hi Jose,
The problem mentioned previously:
using arcgis.raster.analytics.copy_raster. Since the update last night, publishing is failing with "Generic Server Error". Publishing from grib2 through the ArcGIS Image GUI is also failing with a generic "An error has occurred".
should be fixed now. would you like to try again?
Chiming in as the developer working with @JohnLucotch2 on this. We've been successfully publishing several grib2 files twice per day as hosted tiled imagery layers for months, using arcgis.raster.analytics.copy_raster. Since the update last night, publishing is failing with "Generic Server Error". Publishing from grib2 through the ArcGIS Image GUI is also failing with a generic "An error has occurred".
Hi Jose,
Thanks for reporting the issue. We have identified that the publishing problem you encountered is specific to the combination of scientific data type and the hosted tiled imagery layer type.
A fix is in progress and will be roll out soon. I will send an update to let this thread know.
Hi John,
Could you share more details on the publishing case where you encountered the "Generic Server Error"? Are you trying to create hosted imagery layer with the scientific data type as well?
Thanks
We are trying to publish from crf rasters derived from the grib2 scientific data using arcpy.md.subsetMultidimensionalRaster (subsetting to individual vairables from the grib2).
Hi Jose,
The problem mentioned previously:
using arcgis.raster.analytics.copy_raster. Since the update last night, publishing is failing with "Generic Server Error". Publishing from grib2 through the ArcGIS Image GUI is also failing with a generic "An error has occurred".
should be fixed now. would you like to try again?
@jiezhang_imagery This is fixed. Thanks