The data source your stand-alone table references is not supported by map services with Feature Access (feature service) capability or WFS capable map services with transaction support (WFS-T).
Solutions
Feature services published to ArcGIS Server require that all layers and stand-alone tables in the map reference a single enterprise geodatabase or enterprise database. Publishing query layers to ArcGIS Server are supported from enterprise databases only. WFS-T services require that all layers and stand-alone tables reference a single enterprise geodatabase using the same database connection. This enterprise geodatabase or database must be registered with the ArcGIS server.
The solution to this issue depends on how you register this enterprise geodatabase. Use the Data Stores tab of ArcGIS Server Properties to register your enterprise geodatabase or database with ArcGIS Server.
- If you want the service to reference data copied to a specified enterprise geodatabase, register a server-managed database. In this case, the data your layers currently reference will be copied to the enterprise geodatabase you just registered. The stand-alone tables in the service will reference data from this enterprise geodatabase and not from the original data source.
- Click the Add
drop-down menu next to the Registered Databases list box and select Register Server Managed Database to open the Register Database dialog box. - Enter a name for the database registration.
- Under Server database connection, click Edit to register a new database connection, or click Import to browse to and use an existing database connection.
Caution:
This solution will not work if the data source for this layer is currently registered with the ArcGIS server. For example, let's say this layer references file geodatabase data residing in the folder \\myMachine\data. You have folder \\myMachine\data registered with the ArcGIS server. You will need to unregister \\myMachine\data with the ArcGIS server. Once the ArcGIS server understands this data source as unregistered, it will copy the data to the registered, server-managed database.
Also, query layer data will not be copied to the server-managed enterprise geodatabase. If your map contains query layers you will need to export this data manually onto the registered enterprise geodatabase.
- Click the Add
- If you want the service to reference the same data as your map
- Import the data referenced by the stand-alone table to the enterprise geodatabase registered with the ArcGIS server. If publishing feature services to ArcGIS Server, it can also be an enterprise database.
- Once you have all your data in a single enterprise geodatabase, set the data source for the stand-alone tables so they all point to this geodatabase.
Learn more about setting data sources
Caution:
All data referencing an enterprise geodatabase must share a single connection to that database. This error may trigger even though the source database is the same; for example, if you have multiple connections to the same database and used different connections to add layers and stand-alone tables to the data frame, this error will result when you analyze.
Make sure that you use a single, common connection to the enterprise geodatabase when adding the data to your map or setting the data source for an existing stand-alone table.
- Click Add next to the Registered Databases list box to open the Register Database dialog box.
- Enter a name for the database registration.
- Check Same as client connection.
- Under Client database connection, click Edit to enter a new database connection, or click Import to browse to and use an existing database connection.
- If you want the service to reference a different enterprise geodatabase than your map and you don't want to use a server-managed database
- Import the data referenced by the stand-alone table to the enterprise geodatabase registered with the ArcGIS server. If publishing to ArcGIS Server it can also be an enterprise database.
- Once you have all your data in a single enterprise geodatabase, set the data source for the stand-alone tables so they all point to this geodatabase.
Learn more about setting data sources
Caution:
All data referencing an enterprise geodatabase must share a single connection to that database. This error may trigger even though the source database is the same; for example, if you have multiple connections to the same database and used different connections to add layers and stand-alone tables to the data frame, this error will result when you analyze.
Make sure that you use a single, common connection to the enterprise geodatabase when adding the data to your map or setting the data source for an existing layer.
- Click Add next to the Registered Databases list box to open the Register Database dialog box.
- Enter a name for the registered database.
- Uncheck Same as client connection.
- Under Client database connection, click Import to browse to the same database connection used by your map.
- Under Server database connection, click Edit to enter a new database connection, or click Import to browse to and use an existing database connection.
Learn more about registering your geodatabase with ArcGIS Server
More information
WFS-T requires that all layers and stand-alone tables reference a single enterprise geodatabase using the same database connection. All other data sources, such as shapefiles, file geodatabases, and query layers, are not supported. This enterprise geodatabase connection must also be registered with the ArcGIS server.
Feature services published to ArcGIS Server require that all layers and stand-alone tables reference a single enterprise geodatabase or enterprise database using the same database connection. Query layers are supported from enterprise databases only. All other data sources, such as shapefiles and file geodatabases, are not supported. This enterprise geodatabase or enterprise database connection must also be registered with the ArcGIS server.