nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro 2.5 Fails to Overwrite Web Layer - Staging Failed

WalidAlmasri1

I have recently upgraded my ArcGIS Pro to 2.5, and it seems now that I am unable to overwrite layers I have published (we update publicly available data) only getting an area that staging failed. The log says ErrorMessage: ERROR 999999: Something unexpected caused the tool to fail. Is this something anyone else is experiencing? I was able to successfully overwrite layers on a co-workers PC who is still on 2.4.

Thanks!

Find more posts tagged with

Accepted answers

All comments

PowellGIS

I am now getting this error...first time. I am the owner of all data as well. Anyone else recently - or is continuing with those who originally posted?

WalidAlmasri1

No solution other than downloading local and overwriting it that way. I thought maybe an issue with the data, but that's not the case. It's random and sort of rare when it happens, but only happens on enterprise data.

MaryamPanji

Hi Walid,

I am getting the same error. Have you found a way to solve this issue without exporting them into a local geodatabase?

Maryam

WalidAlmasri1

Good morning all, I wanted to follow up on this error. The original issue was fixed, and it it is much appreciated! But, on a few sde layers (using views) when I go to overwrite AGOL layers, I get a staging error 000260. The only way I have been able to get my layer(s) to upload is to export them to my local machine then overwrite the existing web layer. I hoping there is a way to fix this. Any input is greatly appreciated!

The error code is posted below:

WalidAlmasri1

delete

WalidAlmasri1

It has been, but I am getting other errors where I try to overwrite a large dataset from an enterprise geodatabase to AGOL and it errors with 000260. It sucks because this is a layer that always changes (parcels) and I have to keep exporting the data to my local machine to overwrite the AGOL layer.

MichaelBuick

Has this been resolved by ESRI as i am also having an issue with staging failure when publishing from ArcGIS Pro 2.6.1 to ArcGIS Online?

Javier_AntonioEscudero

I had had the same error when publishing a postgres feature class to AGOL until i changed the geodatabase connection to the dataowner.

I mean, the error happend when the connection on ArcGIS Pro was made with a user that was not the Dataowner.

Anonymous User

Even when using the database owner connection, is anyone having issues UploadingService to Portal from Pro 2.5?

I've noticed while StagingService is successful there's an error saying failure to connect to server. And then Uploading the Service Definition fails, although the .sd file is on our Portal site it's unusable.

MelanieWawryk

It is also happening with oracle but not all the time. We have 122 Open data layers that we export daily through Pro/Python script run through a windows batch file. All but a handful of them work and previous to a week ago all have worked. We have run in to this before but could manually run overwrite the webservice out of ArcPro but now we get the fairly useless ERROR 999999: message even when manually trying to update the hosted features. The other 118 still work both manually and through the script. The log gives no extra information.

We are using:

Windows server 2012 R2

ArcPro 2.5

Oracle 12C

ArcGIS 10.7 geodatabase

We have done all the suggestions from all posts I could find (see below). Most suggestions also assume that it hasn't been working for months before suddenly getting this error.

Works fine on roughly 118 or 122 hosted services that are updated through same method/script
Has worked for months
all arcpro documents are in same folder location on the local machine
data all from same geodatabase, same db owner
Connected as database owner
same AGOL user and hosted folder, share setting etc
tried to a new hosted layer - no luck
have pro pointing to local directories for it's processing
rebooted machine
Lots of room on local comuter
tried coping layers to new map > no luck
deleted temp files
file path is not too long, working ones have longer names plus it worked previously
No analyze errors
Also checked geometry
checked symbology
No new domains
No relationship classes
feature class size, one
Display field in Pro is valid
using default python environment in Pro
Used fiddler while trying to publish. Nothing pops out
SDDraft is created in: C:\Users\<username>\AppData\Local\ESRI\ArcGISPro\Staging\My Hosted Services (NAME)
Possible problem with creating index (no log.txt in Maps>index>LAYER folder) > rebuilt indexes > no change
Missing publishingResults.json in C:\Users\<username>\AppData\Local\ESRI\ArcGISPro\Staging\SharingProcesses\<Job ID>\ and found missing the publishingResults.json Is it actually failing on Consolidate data?

Staging is set to E:\ArcGISPro\Staging\SharingProcess but it is putting it in C:\Users\adminsde\AppData\Local\ESRI\ArcGISPro\Staging\SharingProcesses

It would be nice if Esri would add all of these checks and what ever else is making it fail to the analyze tool so we can understand what the issue is or give better error messages when things don't work.

Any other suggestions of what to try are welcome.

mvolz47

The issue is also occurring with Oracle SDE databases.

ThomasColson

Ahh...I am publishing as DBO, and we haven't deployed 2.5 due to other new bugs so I don't have a non-DBO user to test with....

Anonymous User

I do not believe so. This bug only covers issues related to publishing.

PaigeLester12

I also am unable to publish or overwrite in 2.5. "Staging failed" every time. I don't want to downgrade, but I can't get my work done if this persists...

ThomasColson

Interesting, that is my exact environment, and I'm not getting that error, but I do have several cases open on that same environment, could BUG-000129031 be the root cause of those as well?

Anonymous User

Hi all,

The issue you are encountering appears to be a bug with the new release of ArcGIS Pro 2.5. The issue occurs when using an enterprise geodatabase hosted on SQL Server with OS authentication. When trying to publish, you will receive a staging error. The work around for this issue is to connect to the SQL server database as the DBO or system admin. If you are experiencing this issue please call Esri Support Services and we can add you to BUG-000129031. Once you are attached to the bug you can track its progress

Update on the Bug.

This issue appears to be more wide spread than just SQL Server databases.
The updated bug title is as follows:

When connecting to an enterprise geodatabase with any user other than the data owner, the user will receive a staging error when publishing from ArcGIS Pro 2.5 to ArcGIS Online, Portal or ArcGIS Server.

This issue has been tested and reproduced with the following:

SQL Server
Oracle
Postgres SQL

If you are experiencing this issue please call Esri Support Services and we can add you to BUG-000129031. Once you are attached to the bug you can track its progress

KAnderson

With consultation to ESRI, it turns out there was something off with existing our server database. Not resolved, so we're sticking to v2.4 until they can figure out a fix or we hear we need to re-create the database.

rozekc_washtenaw

My normal script for overwriting hosted layers on AGO is failing. Windows 10, Pro 2.5.0, data on SQL Server 2017. My staging service line does have a warning of "Cannot connect to server" which is weird since it's just AGO. Anyone make any progress on this issue or is everyone just downgrading for now? Is there a ticket in yet?

Edit: My script fails without letting me know, each part seems to complete, I can just see that the data isn't updated. Running Overwrite Map Layer in Pro has just a generic failure to publish error.

Update: downgrading didn't help, still trying to get it to work

MalcolmMeyer2

I foolishly attempted to add a layer to my service, no knowing that the feature service #s are based on layer order, which of course changed when I added a layer. Thus the feature services were not corrupted, they were pointing to the wrong layer. This does not really answer why the service upload failed, but now I know something I didnt before.

ThomasColson

2012 is not supported

Microsoft SQL Server database requirements for ArcGIS 10.8 and ArcGIS Pro 2.5—System Requirements | Documentation

MichaelPrior

Im having the same issue with ArcGIS Pro 2.5 and have had to downgrade to 2.4. I believe this is due to our 2012 SQL Server. It seems ESRI have dropped support for 2012 SQL.

Can anyone confirm if they are experiencing this issue with newer versions of SQL?

Windows 10

SQL Server 2012

ArcGIS Pro 2.5

KAnderson

My colleague is having the same issue.

It turns out that I can publish from file geodatabase (as opposed to SDE). And it only occurs when we're copying data (as opposed to referencing SDE).

KAnderson

Windows 10 Pro for Workstations.

MalcolmMeyer2

Failure with no error code and corrupts data on AGOL (one hour before a presentation on how we are going to start using AGOL for field inspections).

"Publishing tool execution failed"

ArcGIS Pro 2.4.2

WalidAlmasri1

What version of Windows are you on?

KAnderson

I'm having the same issue. I've had the error in the past, but it was accompanied by other database connection issues. That time is was fixed by updating the ODBC Driver, but that doesn't seem to be the case now.

ThomasColson

Are you able to get the person in your organization that does have right to call to open a case for you? This would be the person that administers your license, etc....

mvolz47

Do you have access to any Windows 10 machines at your org?

WalidAlmasri1

Thomas Colson my account(s) don't have privileges to open cases with ESRI. But, I would be curious to know if Nathan Renn‌ is using Windows 7 too. I noticed ESRI dropped support on 7 with v.2.5 of ArcGIS Pro.

That's the only thing that stands out to me.

ThomasColson

Walid Almasri‌ and Nathan Renn‌ are you able to open a case with tech support? I'm not seeing this issue on several different installs, and I'm using the GUI and scripts. There may be a software conflict that is affecting many ESRI customers, but we'll never know what it is.

NateRenn

I am experiencing the same issue as well. I have a script that will update services and it is now failing, tried manually overwriting service and same problem...

WalidAlmasri1

I have not tried to open a case, but it might be something worth doing if others are experiencing it too.. It's interesting you don't have the same experience.

But clearly for me, everything is fine in 2.4, 2.5 nope...

ThomasColson

Are you able to open a case with TS on this? I am not seeing the same issue with 2.5

WalidAlmasri1

I did some more testing with 2.5. I was actually unable to publish any layers using 2.5 to our Portal or to our AGOL account. This included trying to overwrite the layers. I must have published all our layers prior to me updating.

I downgraded to 2.4 and it appears to be working fine again.

So far, 2.5 will be a no go for us.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.