Schema lock problem - Error 464

1,664 views
Skip to first unread message

Herb.Sc...@gov.bc.ca

unread,
Mar 9, 2011, 3:48:49 PM3/9/11
to geop...@googlegroups.com
I'm trying to perform a copy features process. Works fine the first time. If I try to run the script again, I get a schema lock error. I've got the gp.OverwriteOutput = 1 but this doesn't seem to have any effect in this case. I've copied the message below. Any ideas?
 
Cheers,
 

Executing: test

Start Time: Wed Mar 09 12:34:50 2011

Running script test...

<class 'arcgisscripting.ExecuteError'>: ERROR 000464: Cannot get exclusive schema lock. Either being edited or in use by another application.

Failed to execute (CopyFeatures).

Failed to execute (test).

End Time: Wed Mar 09 12:34:51 2011 (Elapsed Time: 1.00 seconds)

Fran Tarkington

unread,
Mar 9, 2011, 6:00:54 PM3/9/11
to geop...@googlegroups.com
Hey Herb.

Close all ArcGIS applications (Arc Catalog/ ArcMap etc) and then try running the command.  If that doesn't do it then close all applications, then open you python script again and try running.

Let me know if that sorts it out!

Cheers

Kevin

--
You received this message because you are subscribed to the Google Groups "Python - ARCGIS geoprocessing" group.
To post to this group, send email to geop...@googlegroups.com.
To unsubscribe from this group, send email to geopython+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/geopython?hl=en.

Herb.Sc...@gov.bc.ca

unread,
Mar 10, 2011, 12:06:03 PM3/10/11
to geop...@googlegroups.com
Sorry, I should of mentioned that the only way I have found around this problem IS to close all ArcMap sessions, including ArcCatalog, and logoff, then log back in. But this method sure seems clunky. If I run my script once, make a change or two, I have to logoff and then log back on to run the script again. There must be a better way.  I have been temporarily getting around this by renaming the feature class everytime I want to run the script ... again, there must be a better way.
 
I am assuming that people do this all the time, especially when debugging.
 
Thanks for the suggestion, let me know if you've got any other ideas.
 
Cheers,
 
Herb 
Reply all
Reply to author
Forward
0 new messages