Select to view content in your preferred language

ArcGIS Pro - Error 999999 "Cannot acquire a lock"

17674
12
09-29-2015 12:50 PM
TravisBugg1
Occasional Contributor

I find that I'm getting this error quite a bit. Mostly when working with Mosaic Datasets, but also with other geoprocessing tools. The data is stored on a network location. No one else is accessing the data. I'm not sure why there is a lock in place. In the past, I've been able to get around this by using the ArcPy command line. That works maybe 50% of the time.

I just tested this by creating a new File GDB and then attempting to create a Mosaic Dataset within the GDB. The GDB had never touched, and still I get this error. Is this because I'm accessing a network drive? This is the same location that I work in when in ArcMap 10.1, and it works fine from there.

Also, I've noticed that about half of the time, Mosaic Datasets aren't even visible from the "Add Data" window.

Can anyone shed any light on the situation? Why are these GDBs locked? Adding vector data from file GDBs doesn't seem to be a problem, but mosaic datasets are very problematic. I've upgraded to ArcGIS Pro 1.1.1, and this is still happening.

Thanks.

Edit: It looks like the Create Mosaic Dataset tool gets as far as creating the AMD...CAT catalog file within the GDB before it fails.

0 Kudos
12 Replies
WhitneyRapp
Occasional Contributor

After being driven berserk by this in AGP 2.4.3 the last few weeks, I reverted back to ArcMap 10.7.1 to complete field calcs on a dataset.  My featureclass has over 13 million points in a fGDB, so I already have complexities based on size, but AGP was compounding my chaos.  I sometimes could get AGP to cooperate after a computer restart, compress the fGDB, say sweet nothings to it, but other times my hair greyed in frustration.  The fGDB is on my C drive with no other complications.  No issues since going back to ArcMap.

0 Kudos
JoeBorgione
MVP Emeritus

Gray hair isn't so bad...

No, seriously, are you having a lock issue with you database?  

That should just about do it....
0 Kudos
WhitneyRapp
Occasional Contributor

Yes, I was CONSTANTLY getting the error with AGP 2.4.3 with higher frequency the longer the aprx was open, my computer had been on, and/or the more records that were selected.  The exact same fGDB and feature class has caused me no issues in ArcMap 10.7.1 with Field Calc on selected records (often >500k records).  I did not try the suggestion of enabling the undo option in AGP  

0 Kudos