ArcGIS 10 Error: no editable layers

RomainHerren · ‎03-23-2012

Hello, I work on a lot of data that is on a server for my job. Since I switched to ArcGIS 10, I have all the time the problem as in the attached picture.
I do not work with geodatabase, but with .shp on the server. When starting an editing session, I receive always the error message "no editable layers". I looked for solutions and read a lot on forums (like this thread http://forums.arcgis.com/threads/27600-no-editable-layers-and-can-t-edit-versioned...) and the only thing that seems working is to copy everything on the C drive. But that's not a real solution...
I did not have this problem with ArcGIS 9.3, and because I work in a company, it is important for us to have our data on a server!

Does anyone have a idea? Thank you!
[ATTACH=CONFIG]12952[/ATTACH]

PeterJones · ‎02-16-2017

I have a similar problem but I am using file geodatabases. The geodb is on a local server. I've noticed it tends to happen when I have lots of layers in the map (not sure if it is the multiple projections of different files that could be causing the issue - this is the only thing I can really put it down too). My dataframe and geodb are in the same projection.

There are no permission issues (I administer this particular local drive).

The only work around I have is to close ArcMap and reopen a blank map. Then add the layer I want to add (and maybe a few references layers). I can then edit the geodatabase no worries.

I also can't copy a layer from one map to a new blank map ... I will have the same issues with no editable layers.

Anyone else have any thoughts?? Resolutions??

RobCahalan · ‎03-10-2017

I only have a little bit of server experience but are you sure they are Feature Access enabled? If not, republish with Feature Access in order to edit.

deleted-user-bLE_OOY6Zt-r · ‎05-31-2017

Closing ArcMap and restarting solved my problem on this issue. Anyone know why?

ShaningYu · ‎07-11-2017

I got the same problem. It was found that it was due to the crashed SDE DB. After re-building the DB and creation of the version, the problem was gone.