title: ArcGIS file geodatabase lock issues
body: <p>Currently, our workforce has about 15 users who all view the same file geodatabases. Typically, when viewing the data only, a schema lock (sr.lock) is created for whichever feature class is being viewed inside of the geodatabase.  Here lately, one of the users has been creating both a schema lock and a read lock (rd.lock) on the same feature classes.  However, it does not do this for all feature classes being viewed. I can start an editing session on the geodatabase in which the read lock is created, and it will create my editing locks (ed.lock) and allow me to edit just fine like normal. It's only when I go to save my work that "a lock cannot be acquired". It at this point will not allow me to save my edits like normal. What would be causing just a few feature layers to be creating the random read locks on top of the schema locks? </p>