topic Re: Publishing Issues ERROR 001369 & 001487 & 001488 in Geodatabase Questions

Publishing Issues ERROR 001369 & 001487 & 001488

DarylHochhalter — Thu, 15 Dec 2016 19:10:32 GMT

ArcGIS 10.4, ArcServer 10.4, Federated Portal 10.4, SQL Server 2014 Geodatabase

All these errors give the message Packaging Succeeded, but publishing failed. Yesterday I was getting 001488, and eventually solved the problem by creating a new MXD and copying the layers into it, I was able to publish. This morning I noticed one layer in an already published service wasn't drawing in the web map I added it to. I tried to re-publish the Service and got Errors 001487 & 001369, same error message I was getting yesterday with the other number. I tried a number of things again including creating a new MXD. Nothing worked until I removed the server account privileges from a particular Dataset and then gave the same privileges back to it again. I was then able to re-publish the service.

So my question is what could cause a layer in a service to quit drawing, finally requiring the action I took to remove privileges and reinstate them? Is it possible that if I had renamed one of the Feature layers in the Dataset after initially publishing, this it what it took to fix it?

Re: Publishing Issues ERROR 001369 & 001487 & 001488

DarylHochhalter — Thu, 22 Jun 2017 21:40:14 GMT

I looks as though some the publishing errors and sometimes working issues were permissions for the ArcGIS serer account on some of the installation directories. Not sure why the installation would grant needed permissions on folders it creates, but guess it didn't.

Re: Publishing Issues ERROR 001369 & 001487 & 001488

AnibalMmartinez — Wed, 28 Aug 2019 14:36:59 GMT

Estoy teniendo el mismo problema, con Portal 10.5 Onpremise intentando cargar una capa, voy a revisar lo que comentas @Daryl Hochhalter, y les digo.

Re: Publishing Issues ERROR 001369 & 001487 & 001488

AnibalMmartinez — Mon, 09 Sep 2019 13:12:10 GMT

En mi caso se soluciono con esto https://support.esri.com/en/technical-article/000012592 , finalmente era que cuando armamos el ambiente productivo olvidamos activar el almacenamiento de datos de los servicios.