Skip To Content

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

The data source referenced by this stand-alone table, or data that is joined or related to this stand-alone table, has not been registered with the federated server. Data will be copied to the server.

Caution:

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 v1. 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 the v1 version, 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.

Solution

  • Do nothing. The source data will be copied to the federated server. This includes all related or joined data.
  • If you do not wish to copy your data to the server you will need to register the original data source with the federated server.
    • The provided solution will open the Registration dialog. Enter a name for the data store and click OK.

More information

Registering a data source with the server helps ensure that the server has access to all the data that the web layer references. If a data source is not registered with the server, the data referenced by the standalone table in a map you are sharing will be copied to the federated server. For more information on registering data, see: Manage registered data stores