topic Re: Staging Failed when Sharing as Web Layer in ArcGIS Pro Questions

Staging Failed when Sharing as Web Layer

CarsonG — Tue, 12 Jul 2022 14:49:29 GMT

I am getting the staging error when attempting to share layers from ArcPro.

"ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds."

Nothing noted in the following link seems to be apparent in my map.

Error: Staging failed (esri.com)

I was trying to test sharing Layer Files (for symbology) produced in ArcMap as a Web Layer in Pro.

The Layer Files were brought into Pro, and tried to share as Web Layer. That is when the error popped up.

However, when I create a blank .mxd in ArcMap and bring in the layer files, I have no issue sharing them as a Service.

Sharing as a Service Definition in Pro results in the same error.

Bringing the feature classes into pro on their own and applying the symbology allows them to be shared as a web layer.

I cannot see why the process would work in ArcMap but not in Pro?

Re: Staging Failed when Sharing as Web Layer

RyanTucker — Tue, 12 Jul 2022 17:39:29 GMT

I was having this same issue last week with ArcGIS Pro. It turns out that I had my active python environment set to a clone. When I changed my python environment back to the default environment I had no issues publishing. This is a new issue with ArcGIS Pro 3.0.

The active python environment can be found under Project ---> Package Manager.

Re: Staging Failed when Sharing as Web Layer

CarsonG — Tue, 12 Jul 2022 17:55:41 GMT

The environment is still set to the default. I am also still on 2.8.1.

The issue occurs when I attempt to publish Layer files that were added to the map. The work around is to apply the symbology manually to the data but it would be beneficial to utilize Layer files like I have in the past when using ArcMap.

Re: Staging Failed when Sharing as Web Layer

AndyWells — Mon, 03 Oct 2022 14:18:27 GMT

I'm having the same issue. It overwrites fine in the default environment but not in the cloned environment.