Why is Pro making locks on stuff in a GDB and then giving me errors that a lock exists. YOU CREATED THE LOCK, WHY WOULD YOU NEED TO MAKE ANOTHER ONE? ITS THE ONLY APPLICATION THAT CAN USE DATA IN A GDB. I'm literally having to restart the program all the time what is happening?
Hello @ChrisCowin_dhs Locks are there for various reasons, eg to ensure the data's properties do not change while it is being used. There are different types of Locks and the Lock type may change as your usage of the data changes.
https://support.esri.com/en/technical-article/000006976
https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/manage-geodatabase-locks.ht...
What particular errors do you see, and what are you trying to do when you see them ?
Nothing is changing it though! Or I change something and save it and then go to do use a geoprocessing tool and it just says can't do it there is a lock. Add a field, go to use field calculator and nope cant do that because there is a lock. OK have to restart, so I restart and run the field calculator, now I go to run an analysis, nope cant because there is a lock. I just constantly have to restart the entire program on any change to any component that I'm trying to analyze. It is infuriating.
ArcPro/arcpy are some of the only programs that can create locks on a GDB, yes. However, individual ArcPro processes don't communicate with one another and can lock eachother out of a database or project file. Have you checked that you don't have hanging locks from a previous Pro instance (Check Task Manager and look for ArcGIS Indexing Server) or that there aren't other processes (e.g. a Python terminal with arcpy loaded and pointing at your database) running?
No python is running, I'm creating all the data fresh so a brand-new project, a brand-new gdb, only one instance of pro running. I bring in two csv's and make an xy table and import those into facilities and incidents and go to solve the network analysis and it fails to solve. I've tried ending the process for the indexer, doesnt do anything. The only thing that works is to close the entire project, sometimes even have to restart the program and then I can do the next step before it creates another lock that it invariably prevents me from doing the next step because the lock.