Skip To Content

24012: Standalone table's data source is not registered with the server and data will be copied to the server

You are sharing a web map or web layer that includes a stand-alone table and you have chosen to reference registered data. However, the data source referenced by the stand-alone table, or data that is joined or related to it, is not registered with the federated server. The data will be copied to the server.

Solution

  • Allow the data to be copied to the server.

    Do nothing. The source data, including all joined or related data, will be copied to the federated server.

  • Register the data with the server.

    Hover over the analyzer message. Click the Options button Options that appears and click Register Data Source With Server. In the Add data store dialog box, complete the required information and click Create. For more information, see Manage registered data stores.

    Note:

    If you do not have the privilege to register data stores in your ArcGIS organization, a message to contact your organization administrator appears. Your administrator can assign you the privilege to register data stores or can register the data store for you.

  • View the data stores registered with the federated server.

    Hover over the analyzer message. Click the Options button Options that appears and click Open Manage Data Stores Pane.

More information

Registering data with the server helps ensure that the server has access to the layer's data source. For more information on registering data, see Manage registered data stores.

You may encounter this message 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. 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 message. This would also occur if you have different connections to the geodatabase using different user names.