cannot add to existing mosaic dataset

6217
13
04-10-2013 09:11 AM
Labels (1)
PeterHoffman
Occasional Contributor
I get the following errors:
cannot create an insert cursor using the mosaic dataset
cannot acquire a lock.
This used to work.
0 Kudos
13 Replies
RobertRiley
New Contributor II
Receiving the same error trying to Define Overviews in a mosaic dataset.
The function worked fine with the first two mosaic datasets in the same file geoDB.
Third time (and fourth, fifth, and sixth) a charm.

<Errors>
<Error>ERROR 999999: Error executing function.</Error>
<Error>Cannot create an insert cursor using the mosaic dataset.</Error>
<Error>Cannot acquire a lock.</Error>
<Error>Cannot acquire a lock.</Error>
<Error>Failed to execute (DefineOverviews).</Error>
</Errors>

ArcCatalog 10.1 (Build 3143)
0 Kudos
PeterHoffman
Occasional Contributor
Working with ESRI we found that turning off background processing and using the foreground method it worked fine. There is a 64 bit geoprocessing sp1 available but I have not installed it yet.
RobertRiley
New Contributor II
Roger that.  Enlisted ESRI help as well.

Even with x64 geoprocessing SP1, had to disable background processing in order to process this particular raster dataset.

Thanks.

BIM
0 Kudos
PeterHoffman
Occasional Contributor
OK, good to know, back to drawing board, thanks,
0 Kudos
JacksonTrappett
Occasional Contributor II
Working with ESRI we found that turning off background processing and using the foreground method it worked fine. There is a 64 bit geoprocessing sp1 available but I have not installed it yet.


This worked for me too - thanks!
0 Kudos
RobertCarlos
New Contributor II

Yes.  Worked. 

Turned off background processing and using the foreground method.

In ArcCatalog go to Geoprocessing at the top and select Geoprocessing Options.

In Geoprocessing Options Offcheck the Checkbox labeled "Enable" within the Background Geoprocessing section. (This is in the upper middle section of the GUI Window.)

CarlyRobbins
New Contributor

Still a working solution in 2018! Thank you.

0 Kudos
KevinMacLeod4
Frequent Contributor

this bug is still here 3 years later..sigh. Confirmed though, still works! Thanks Peter.  

0 Kudos
JingLi4
New Contributor II

I apologize for the inconvenience caused by this issue. I believe this issue has been addressed in ArcGIS 10.6 and later version. Which version are you using when encountering this issue?

If you are using 10.6 or later version and still see this behavior, I would appreciate it if you could detail the steps used so that I can follow it to reproduce the issue in house.

Thanks

0 Kudos