You are sharing a map image layer with a dependent feature layer. Your web layer includes a stand-alone table that is not registered with the federated server.
ArcGIS Pro does not support copying data into a managed database when you share map image layers.
Note:
You may encounter this error when you overwrite map image layers with dependent feature layers and copied data that were published from ArcMap, where data could be copied into the managed database.
Solutions
Register the table's workspace with the federated server.
Hover over the analyzer message. Click the Options button
that appears and click
Register Data Source With Server. On 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
that appears and click
Open Manage Data Stores Pane.Choose not to share the dependent feature layer.
In the Share As Web Layer pane, click the General tab. Under Layer Type, uncheck the Feature box. Data will be copied to the server and will not be editable.
More Information
When you share a map image layer with a dependent feature layer, all layers and standalone tables in the map must have the same registered enterprise geodatabase or database data source. Data sources can be registered before publishing through the Manage Registered Data Stores pane or by resolving this error. For more information, 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.