esriExclusiveSchemaLock Error on Hosted Featre Layer

[CodyPatterson]

Hey all,

Enterprise 11.3

Today, I'm attempting to add a field to a hosted feature layer, that was created when making a Workforce app, so I did not upload this from ArcGIS Pro. This is interacting with the datastore database itself. I received this error here when attempting to add it:

So far, the only documents I see are stating that I need to ensure that I am the only user attempting these changes, and that I need to ensure that the GDB it's stored on when uploading from Pro has its locks cleared, these fit neither of my situation.

What does this error mean? How can I resolve it? This only is affecting a single hosted feature layer, others are perfectly fine, this is a synced and offline mode feature layer that I have added additional fields to before, but not anymore.

Cody

[RPGIS]

Hi @CodyPatterson,

Try these options:

1. Close out of pro and reopen your project. Sometimes pro will randomly put locks on features for reasons unknown and that will impact some workflows.
2. Try publishing a new service and see if the copy allows for changes. If the copy allows for changes then it might have something to do with the service definition which will require it to be overwritten.
3. Try making a complete copy of the data and see if publishing it works. if that works then it might indicate that the service is probably corrupted.

[CodyPatterson]

Hey @RPGIS 

Unfortunately, I did not upload this from ArcPro and this is an attempt to add a field to a hosted feature layer  created by Enterprise Portal from the Workforce app.

Cody

[RyanUthoff]

I know I commonly have issues like these with SQL EGDB's and not hosted, but maybe other people are actively using that hosted feature service and therefore, Esri can't get a lock? That's my best guess.

One thing that you could try is to un-share the hosted feature service with everyone to ensure that no one is actively using it, then try and add the new field. And worst case scenario, possibly restart the ArcGIS Data Store to clear out any orphaned locks or anything like that that could be causing issues.

[CodyPatterson]

Hey @RyanUthoff 

Great point and idea! I hadn't thought about unsharing it, but maybe that could end up working. I could definitely see that the lock may fail due to the excessive amount of users on, but didn't consider at that moment. I normally restart all servers on Friday, but I may try today if this doesn't work at the moment.

Cody