Error codes can occur in one of many hundreds of locations in the system. Sometimes the code is returned by a function deep in the stack and far removed from your code that is handling the error. Consequently, the descriptions of these codes cannot always be specific to the problem you are faced with; further investigation and analysis is often required.
The table below defines the error codes that can arise from any of these editing operations.
SQL statement is not valid.
Access permission to database file denied.
A database callback function called abort.
The database is locked. Did you commit a transaction while a cursor was open?
Write operation attempted on a read-only database.
Operation terminated by an interrupt.
The database file is corrupt.
SQLite encountered an invalid op code.
The database file can't be opened.
The database file is empty.
The value falls outside a range of allowable values.
Database constraint violation, such as adding duplicate value to a unique field.
The data types are not compatible.
Misuse of SQLite API. Generally, using an uninitialized or closed object.
Feature not supported on this OS.
Bind parameter greater than the number of binds.
File exists, but is not a SQLite database.
Called an unimplemented virtual function.
Database create was called with fail_existing and found an existing database.
Database was not found at this path.
Table, index, and field names cannot be longer than 128 characters.
Shape type not supported in runtime geodatabase.
Raster fields are not supported in the runtime geodatabase.
Cannot create a second relationship for the same row in a one-to-one relationship class.
Item not found in the database (table, domain, relationship class, and so on).
Value is already present in the coded value domain.
Value is not present in the coded value domain.
The wrong item type was passed to a polymorphic function.
OID and GlobalID fields cannot be nullable.
Default value not supported for this field type.
This table is not editable.
The requested field was not found.
Cannot alter the type of an existing field.
Cannot alter the width of an existing field.
Cannot make nullable field not-nullable.
Cannot make not-editable field editable.
Cannot make not-deletable field deletable.
The table must be named to generate index names.
The type is not support by the domain.
The minimum of a range domain cannot be greater than the maximum.
Attributed relationship classes cannot have geometry or raster fields.
Cannot delete a key field of a relationship class.
Cannot extract a null row value. Call is_null to check.
Cannot execute multiple SQL statements in the same command.
No SQL statements were found in the command.
A query with a search geometry must specify geometry in the subfields.
This transaction was already started.
This transaction has not been started.
The shape must have a z-value.
The shape must have an m-value.
The shape must not have a z-value.
The shape must not have an m-value.
The shape has the wrong type for the field.
This field type cannot be updated.
The update or delete statement did not affect any rows.
The field has an invalid subtype.
The subtype field must be an integer field.
Subtypes are not enabled on this table.
A table can only have one each of OID, GlobalID, and Geometry.
Cannot delete OID, GlobalID, Geometry fields; the subtype field; and fields that are marked not deletable.
The requested index was not found.
The cursor is not on a row and cannot extract values.
Geodatabase-managed fields, such as editor tracking fields, cannot be assigned to.
The item to be created already exists in the database.
The spatial index name is invalid. The spatial index name may be a duplicate name. Rename the table to ensure a unique name.
The operation requires a spatial index.
The name of the field is invalid as it is a reserved name.
Schema modifications are not supported for change tracking-enabled tables.
The database does not have changes.
There is no sync replica associated with this database.
The storage type is not supported.
The operation is not supported by the sync replica model.
There is an error with the replica client generation number(s). Check that the value has been initialized.
There are no uploads waiting to be acknowledged.
Cannot write to the database because its last write time is in the future.
An invalid argument was passed in.
The transportation network data is corrupt.
Could not read transportation network data.
There are pending edits on the feature. This feature will not be synchronized.
Change tracking is not enabled on this table.
The transportation network data files could not be opened, and may be missing.
The transportation network data format is not supported by the current implementation.
The database is on a different device or at a different location than it was locked to. Cannot sync without reregistering first.
In a connected environment, you can apply the edits to the feature service as soon as you make them. For more information on this workflow and the classes, methods, and error objects refer to the Commit your edits section in the Edit features document in the Guide section of your specific platform documentation on ArcGIS for Developers.
Errors raised during any of these steps are outlined in Apply Edits (Feature Service) document. Go to the error code link in the Description section.
In a disconnected workflow, you synchronize your edits back to the service once you have a network connection. For more information on this workflow and the classes, methods, and error objects, refer to the Sync offline edits document in the Guide section of your specific platform documentation on ArcGIS for Developers.
Errors raised during any of these steps are outlined in Error handling with sync.