nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FileGDBException: The user does not have permission to execute the operation.

PrzemyslawTyrtania

I'm getting this error when trying to execute table.Delete(row), the error is thrown on the first row. There are many tables in this file geodatabase so I've tried with different ones for some tables it works and for others it doesn't. These are all standalone tables, no relationships, editor tracking is not on. File geodatabase is generated from a 10.2.2 geodatabase. This table has a few fields and the only field that stands out is Settings which is defined as nvarchar(max) in geodatabase.

Fields:

ObjectID

Name: text 255

Settings: text 1073741822

ModifiedTime: date

Version: Text 255

SettingsType: Text 255

RowCollection rowCollection = table.Search("*", whereClause, RowInstance.Unique);

foreach (Row row in rowCollection)

{

table.Delete(row);

}

Finde mehr Beiträge mit dem Tag

Accepted answers

LanceShipman

The API only supports simple features. Extensions are not simple data. so this is consistent. Thank you for verify that this was the issue.

All comments

VinceAngelo

So the obvious question is: What is different about the tables on which Delete is permitted from those on which it is not? Are there filesystem permission issues? Are you sure there isn't any non-simple aspect to the tables? What does Table::IsEditable report?

- V

PrzemyslawTyrtania

Thanks for quick reply. So to answer your questions, I've been looking at different tables and i don't see anything different, of course i maybe overlooking something or not looking in the right places, BUT IsEditable is returning FALSE, so that is big hint, can you tell me what controls that flag? Code that generates this file geodatabase is a python script, it connects to geodatabase with account that has owner permissions and does this for each table:

source_db = "\\\\" + hostname + "\\Deployment\\Connection.sde"

arcpy.env.workspace = source_db

items = arcpy.ListTables()

for sourceItem in items:

targetItem = string.split(sourceItem, ".")[len(string.split(sourceItem, "."))-1]

target = target_db + "\\" + targetItem

source = source_db + "\\" + sourceItem

arcpy.Copy_management(source, target, "Table")

I can add screenshots from ArcCatalog if you think its helpful

LanceShipman

The API will not allow the edit of table or feature classes involved in Annotation and Dimension feature classes, Relationship Classes, Networks (GN and ND), Topologies, Terrains, Representations, Parcel Fabrics and Edit Tracked tables/feature classes.

Screen shots showing the content of the file geodatabase would be helpful.

Regards,

Lance Shipman

PrzemyslawTyrtania

If there is something else i can look at please let me know.

PrzemyslawTyrtania

I don't think this table is involved in any of these, I've posted some screenshots.

VinceAngelo

When you work out how to get IsEditable to return true, you might want to try to truncate the table using Geodatabase::ExecuteSQL with "DELETE FROM tablename" without a WHERE clause or spatial constraint. It will likely be much faster than iterating the rows in an unbounded query and deleting each.

- V

PrzemyslawTyrtania

So we deleted everything from the sde database except the table in question and created fgdb from it and it still failed with same error, then we created new PGDB and exported the table to that database, then delete futura_settings table from sde then copied it from pgdb to sde and then exported to fgdb then it worked fine.

Screenshot 2025-06-24 141018.png

VinceAngelo

So it sounds like your enterprise geodatabase metadata was corrupt, and that was passed through to the FGDB by Copy_management, so the API was seeing the table as non-simple. Once the table really was simple, then IsEditable returned true, and you were able to delete. If you have a copy of the data in its corrupt state, I expect Tech Support would want to look at it.

- V

PrzemyslawTyrtania

I was going to attach the databases to the message but I'd prefer something more secure so if you can email me and provide me with a way to upload then i'll do that, total size of the files is about 12 mb so I don't think I can attach to the email: przemyslawt@futuragis.com

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.