Cannot Acquire Lock NAS Drive

[STIPP_GIS_Admin]

We have started having an issue with creating feature classes, running geoprocessing tools, and exporting data in the latest update. We work from a shared NAS drive and have not experienced this issue until a recent update.

We are running ArcGIS Pro 3.3.2

Windows 10

Buffalo NAS drive

I have tried this a couple of times and keep running into the same issue. Here are the steps:

1) Create a new project (using NAS folder)

2) create new feature class in project geodatabase

This is year I get a big red error box. When you close that you get a second message saying cannot acquire lock. Images attached.

However, if I refresh the file folder in the NAS drive and then refresh the geodatabase the created layer does show up and I can add it to the map.

Same issue with geoprocessing tools, for example "enable attachments" cannot acquire lock, but if I refresh the file folder then the geodatabase they are enabled.

Same with exporting the feature class. Incidentally I have also been getting an "001177: Attachments are not supported in this Geodatabase release." error but I think this is tied to the lock.

We have not experienced this before and have never seen this before using the same setup.

I read a post about it possibly being related to read-only access but we have read/write permissions. I have tested creating a new project on an external hard drive and do not have these issues.

From what I can tell this is either an internal network issue or a GIS issue. As this worked for us up until we installed ArcGIS Pro 3.3.2 I wanted to find out if this is an issue others are experiencing and if there is anyway to solve this.

[CodyPatterson]

Hey @STIPP_GIS_Admin 

You mention this started when you installed ArcGIS Pro 3.3.2, would it be possibly to temporarily downgrade version to test if it is still functioning? If this occurs to you and others with ArcGIS Pro 3.3.2, it may be a bug of some sort.

Cody

[STIPP_GIS_Admin]

That had not occurred to me. I just tried it on a different computer on the same network and using the same NAS drive but running ArcGIS 3.2.1 and everything worked. Creating new layers, running tools, exporting data.

Would that indicate that this is a bug in the new version?

[CodyPatterson]

Hey @STIPP_GIS_Admin 

Reading through your other comments, this definitely seems to be some bug of some sort.

To report the bug to ESRI, the easiest way is to open a ticket through My ESRI and then the ticket will be attached to a bug case, which you'd be able to track progress on.

Cody

[STIPP_GIS_Admin]

That had not occurred to me. I just tried it on a different computer on the same network and using the same NAS drive but running ArcGIS 3.2.1 and everything worked. Creating new layers, running tools, exporting data.

Would that indicate that this is a bug in the new version?

[STIPP_GIS_Admin]

Apologies for the multiple posts of my previous message.

I just had someone else in our office try the same steps who is running version 3.3.1 and they are not experiencing this issue either.

How can I report this to ESRI?

[STIPP_GIS_Admin]

I downgraded to ArcGIS Pro 3.3.0.

The same issue keeps happening, but I also found a workaround:

If I open the file geodatabase in windows explorer, I can see the LOCK files being created and then being removed. If I do not have the file location open, I get the Cannot acquire lock error.

I have tried this with creating layers, using geo tools, and exporting data, they all function correctly if I have the geodatabase open in windows explorer. Does anyone know why this might be happening?

At this point I don't know if this is a network issue or an ArcGIS issue, but hopefully if someone else is having this issue it helps them out.

[STIPP_GIS_Admin]

It might be related to this:

BUG-000164781 for ArcGIS Pro