Select to view content in your preferred language

Unable to publish and host a raster layer to AGOL anymore

379
2
Jump to solution
03-11-2025 06:15 AM
MillionMap
Regular Contributor

Two things happening that is preventing what once worked.  I'm unable to publish a hosted tile package anymore.  Its a simple raster image within an ArcPro map that I'm attempting to publish to AGOL, something I've done several times before.  The last time was two months ago.  I'm using the same ArcPro project, the same inputs, and the same method.  But I get an error when I run 'Share Package' (see attached).  If I add the tile package to AGOL using the 'New Item' method, the file isn't hosted.  Both of these use to work but for some reason they don't anymore.  Is this due to the recent update?  Have I lost a privilege somehow?

0 Kudos
1 Solution

Accepted Solutions
DanielFox1
Esri Regular Contributor

Hi @MillionMap 

What usertype and role do you have if it is not an admin role, can someone that is an admin attempt the same workflow?

Documentation on the error 

https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/001001-010000/tool-...

Can you add the data into a new ArcGIS Pro project?

Maybe worth looking at a soft profile reset to?

https://support.esri.com/en-us/knowledge-base/how-to-perform-an-arcgis-pro-soft-reset-000027631#:~:t....

 

View solution in original post

0 Kudos
2 Replies
DanielFox1
Esri Regular Contributor

Hi @MillionMap 

What usertype and role do you have if it is not an admin role, can someone that is an admin attempt the same workflow?

Documentation on the error 

https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/001001-010000/tool-...

Can you add the data into a new ArcGIS Pro project?

Maybe worth looking at a soft profile reset to?

https://support.esri.com/en-us/knowledge-base/how-to-perform-an-arcgis-pro-soft-reset-000027631#:~:t....

 

0 Kudos
MillionMap
Regular Contributor

I reached out to the admin and she made a change.  Not sure what happened but it was a simple privilege setting change.  

0 Kudos