Skip To Content

00231: Layer's data source must be registered with the server

You are sharing a map image layer with a dependent feature layer or a scene layer with an associated feature layer with the Reference registered data option and the workspace of your layer is not registered with the federated server.

ArcGIS Pro does not support copying data into a managed database when sharing map image layers. You may encounter this analyzer when overwriting map image layers with dependent feature layers that were published from ArcMap where data could be copied into the managed database.


  • Register the layer's workspace with the federated server.
    • The provided solution will open the Registration dialog. Enter a name for the data store and click OK.
  • If sharing a map image layer that won't be used for editing workflows, unselect Feature for your Layer Type.
  • If sharing a scene layer, change the data option to Copy all data.

More Information

When sharing a map image layer with a dependent feature layer, all layers in the map must have the same registered enterprise geodatabase or database data source. When sharing to ArcGIS Enterprise 10.6.1 or later, scene layers with associated feature layers can reference data in either a registered file geodatabase or enterprise geodatabase. Data sources can be registered before publishing through the manage registered data stores pane or by resolving this analyzer. For more information, see Manage registered data stores.

You may encounter this analyzer even though the source enterprise geodatabase or enterprise database has already been registered with the federated server. The reason for this is that the connection properties (user name, password, version, and so on) used by a layer or stand-alone table referencing the source enterprise geodatabase do not match the connection properties of the enterprise geodatabase registered with the server. In this case, you not only register an enterprise geodatabase, you also register the connection to the geodatabase. Registration is required for each separate connection.

For example, say you have an enterprise geodatabase named DB1 that has two versions: default and version 1. You only register the connection to DB1 using the default version. If you attempt to share a map containing layers or stand-alone tables pointing to version 1, and you have not registered this connection to DB1, you will encounter this analyzer. This would also occur if you have different connections to the geodatabase using different user names.