workspace suddenly becomes read-only

[MatthewFoster]

Hi Everyone,
This is driving me crazy.  I will be working on editing a point shapefile (or feature class in a file geodatabase), adding points and an attribute for the ID as I go along.  I can save the edits as I go (and I do), but after a few saves, the shapefile or feature class suddenly becomes read-only - or at least, that is what ArcGIS tells me, "Unable to save edits. Workspace or data source is read only".  I never set anything to read only, and after successfully saving my file 3 times (in the latest case) it decides to give me this error on the fourth time!  I have tried putting the geodatabase in a different directory, I've tried as a shapefile... Any ideas?  This has happened repeatedly with different projects lately.  Very frustrating

Thanks in advance,

Matt

[Streltzer_Tracie]

Disabling anti-virus on access scan of all FOLDERS with *.gdb resolved the issue for us

[Anonymous User]

Running 10.5.0.6491 on windows 10, saving to a network drive and I get this error. If I close down and re-open the same project there are no issues for while.  any more recent solutions? 

[MariahKelly1]

SOLUTION:

In my case I was using arc pro, on a server network. Would used a FC to FC. Would then become read -only. I would right click on my new feature class>Properties>Metadata

The first box is a drop down, I chose "Layer has its own metadata"

[curtvprice]

Sounds like a possible issue with Pro's new 2.1 functionality to have metadata for a layer and feature class separately. Please consider reporting this issue to support so they can get it fixed.

[GarretDuffy]

I also had encountered this problem.  Didn't realise that my compressing the geodatabase made it read-only... a problem of my own making... 😞

[curtvprice]

Ah, Compact (usually a good idea) vs Compress (need to consider your use case).

[SpatialSam]

This error appeared when I was editing attribute data in pro. I tried re-exporting the features to a gdb and it didn't work. However, I did try something else that worked.

Close out of pro and it will prompt you to save all edits. This isn't a long term solution but it seems to be working smoothly for me now.