English

Error: Could not edit any of the map's layers, No data sources in the map are registered as versioned or you lack privileges to modify data sources

Error Message

When starting a versioned edit session, the following error message is displayed:

"Could not edit any of the map's layers,
No data sources in the map are registered as versioned or you lack privileges to modify data sources which are registered as versioned."

Cause

The error message listed above is displayed when starting a versioned edit session on a workspace. This message has several possible causes, such as the data has not been registered as versioned, or the user attempting to start an editing session does not have the proper object permissions to select, insert, update and delete, which would be granted by the data owner within ArcCatalog.

However, there is one additional possible cause of this error, if the ArcCatalog or ArcMap application becomes locked, is killed or crashes during a data load or edit session of a feature class residing within a geodatabase, then the feature class can be placed and stuck in Load-Only IO Mode, thus preventing any new edits or data loading from taking place.

If the feature class resides within a feature dataset, then the entire feature dataset including all feature classes within it can become unavailable for editing until the affected feature class is changed from Load-Only IO mode to Normal IO mode.

This error message can continue to persist even though the data has been properly registered as versioned and all of the appropriate permissions have been assigned.

Solution or Workaround

First check to make sure that the objects being edited are indeed versioned by opening these objects in ArcCatalog or the Catalog window in ArcMap.

Verify that the layer is versioned:

1. On the Editor toolbar, click Editor and click Options.
2. On the Versioning tab the Editing Options dialog box, unselect the 'Edit a version of the database with the ability to undo and redo checkbox.


Verify that the data is not stuck in Load-Only IO mode:

To determine if this error has been encountered due to data being stuck in Load-Only IO Mode, follow these steps:

  1. Since all data within the database must be checked to see if it is listed in Load or Normal mode, execute the sde command listed below. This command is executed on the entire database. In addition, the results returned from this command are lengthy, therefore the results are sent to a text file, as denoted by adding the [>output.txt] to the end of the sde command line syntax.

    Code:
    sdelayer -o describe
    [-i <service> | <port#> | <direct connection>] [-s <server_name>]
    [-D <database_name>] -u <DB_user_name> [-p <DB_user_password>] [-q]

    Example:

    Code:
    sdelayer -o describe -i sde:sqlserver:GIS -D Landbase >Describe.Landbase1.txt

  2. Open the output text file and review the contents, look for any data in which the I/O mode is set to LOAD.
  3. If data is found that displays an I/O mode of LOAD, then there are two options for changing this mode to NORMAL.

    • Option 1: Open the properties dialog of the feature class within ArcCatalog, calculate a spatial index and click Save.

    • Option 2: Execute the following sde command syntax:

    Code:
    sdelayer -o normal_io -l <table,column>
    [-i <service> | <port#> | <direct connection>] [-s <server_name>]
    [-D <database_name>] -u <DB_user_name> [-p <DB_user_password>] [-q]

    Example:

    Code:
    sdelayer -o normal_io -l victoria,parcels -u av -p mo -i esri_40