24011: <value> is not registered with the server and data will be copied to the server

You are sharing a web map or web layer and with referenced registered data. However, the data source referenced by this layer, or data that is joined or related to this layer, is not registered with the federated server. The data will be copied to the server.

The <value> parameter is data source, layer, or mosaic dataset.

If this warning appears for a mosaic dataset, it specifically pertains to the dataset itself. The imagery in the dataset is not analyzed and will not be copied to the server. To reference registered data, the raster data in the dataset must be registered with the server.

Solution

Do one of the following:

  • 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. If you are sharing a mosaic dataset, its contents will not be copied; only the mosaic dataset will be copied to the 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. On the Add data store dialog box, complete the required information, and click Create.

    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.

    The option to specify a server database connection does not support SQL Server databases using Microsoft Entra multifactor authentication (MFA). For more information, see Microsoft Entra ID options.

    If you are sharing a web imagery layer using data in a cloud store, registering cloud storage connection files created using certain providers and authentication types may not be supported. For more information, see Register a cloud store as a data store.

    Map image layers do not support referencing registered cloud stores.

  • If the server is federated with the portal, view the registered data stores and add a new data store.

    Hover over the analyzer message. Click the Options button Options that appears and click Open Manage Data Stores Pane. Click the Add button Add a data store item to the portal and choose the type of data store the web layer will reference data from. On the Add data store dialog box, complete the required information, and click Create.

Additional information

Registering data with the server helps ensure that the server has access to the layer's data source. For more information about 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, suppose 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.

For more information, see Analyze your GIS resource.