00062: Data frame contains data that does not use the same connection to an enterprise geodatabase

This error covers the following:

• You are publishing a map service with Feature Access (feature service), and your data frame contains layers or stand-alone tables that reference different enterprise geodatabases, and at least one of the geodatabases referenced in the data frame is registered with the ArcGIS server.
• You are publishing a map service with WFS capability with transaction support (WFS-T), and your data frame contains layers or stand-alone tables that reference different enterprise geodatabases, and at least one of the geodatabases referenced in the data frame is registered with the ArcGIS server.
• You are publishing to a spatial data server (SDS), and your data frame contains layers or stand-alone tables that reference different enterprise geodatabases, or enterprise databases.

Caution:

You may encounter this analyzer even though the source enterprise geodatabase (or enterprise database, if you are publishing to a spatial data server) has already been registered with the 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 publish 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.

Learn more about connecting to an enterprise geodatabase and database connections in ArcGIS

Solution

• For feature services and WFS-T
  1. Copy or move all the datasets you want to make available in the service into one of the enterprise geodatabases registered on the ArcGIS server.

     Learn more about copying datasets from other geodatabases

  2. Once you have all your data in a single enterprise geodatabase, set the data source for the layers so that they all point to this geodatabase using the same database connection.

     Learn more about setting data sources

  Tip:

  You can register an enterprise geodatabase as a server-managed database. If you do this, data will be copied to this geodatabase when you publish. For this to work correctly, all data sources referenced in the original document should not be registered on the ArcGIS server. You will need to unregister any of these folder paths or databases before publishing. Data referencing sources already registered on the ArcGIS server will not be copied to the server-managed database.

  Learn more about registering your geodatabase with ArcGIS Server

• For SDS
  1. Copy or move datasets referenced by your layer into a single enterprise geodatabase or a single standard enterprise database that is supported by your SDS connection type. See the table below for the supported databases by SDS connection type.

     Learn more about copying datasets from other geodatabases and copying datasets from other databases

  2. Once you have all your data in a single enterprise geodatabase or a single standard enterprise database, set the data source for the layers so that they all point to this single enterprise geodatabase.

     Learn more about setting data sources

More information

Feature and WFS-T services require that all layers and stand-alone tables in the service reference an enterprise geodatabase using a single connection and the geodatabase is registered with the ArcGIS server.

SDS services require that all layers and stand-alone tables in the service reference either an enterprise geodatabase or a standard enterprise database using a single connection. SDS-supported data sources include both enterprise geodatabases and nongeodatabase, standard enterprise databases. SDS connections can be either Java or .NET. Each of these SDS connection types supports specific enterprise data sources.

.NET	Microsoft SQL Server Windows Azure SQL Database
Java	PostgreSQL Oracle IBM DB2 and Spatial Extender

Learn more about authoring feature services, WFS services, and spatial data server (SDS) services