topic Re: Overwrite Web Layer - Error in ArcGIS Pro Questions

Overwrite Web Layer - Error

Bryan_krg — Fri, 12 Sep 2025 04:06:12 GMT

So this continues to be a problem for us. We publish a web layer to our Portal and then when we try to republish our layer we receive the follow error: Web Layer does not have a valid server connection and cannot be overwritten.

The problem appears to be that when the data source link to ArcGIS Server is first created in portal for the service it uses the following format:

https://<arcgis-server>/arcgis/rest/services/<name-of-service>/MapServer

In order for this service to be overwritten the port for the service needs to be included e.g.

https://<arcgis-server>:6443/arcgis/rest/services/<name-of-service>/MapServer

Does anyone know if this problem with our web adaptor setup or something else we have configured that is causing this issue? Thanks.

Re: Overwrite Web Layer - Error

CalvinHarmin — Fri, 12 Sep 2025 12:51:58 GMT

Just curious: for the publisher using ArcGIS Pro, are they using the web adaptor url for signing into your Portal, or the fully qualified machine name:port?

And just to confirm, is your Server federated with Portal?

Re: Overwrite Web Layer - Error

RClavero — Sat, 13 Sep 2025 13:31:34 GMT

Hello @Bryan_krg, have you checked this article? https://support.esri.com/en-us/knowledge-base/error-arcgis-enterprise-overwrite-web-layer-the-web-lay-000025470

The suggested steps in the solution/workaround section are worth reviewing; maybe together with your GIS admin or IT staff who have configured the ArcGIS Enterprise.

Re: Overwrite Web Layer - Error

Bryan_krg — Mon, 15 Sep 2025 02:35:23 GMT

Thanks Calvin and rcGIS, for your suggestions.

In ArcPro we sign into portal using the web adaptor url (no port used). Our ArcGIS server is federated with our Portal.

From the article/workaround the serverUrl in the Portal properties text box is the same as the Server URL for the relevant Server. To be extra sure we reinstalled the web adaptor and configure it again. But unfortunately for us the problem still persists. We will create a ticket with ESRI.