The data source your layer references is not supported by map services with Feature Access (feature service) capability, WFS capable map services with transaction support (WFS-T), or by image services with the edit capability enabled.
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. WFS-T services require that all layers and stand-alone tables in the map reference a single enterprise geodatabase using the same database connection. The enterprise geodatabase or database must be registered with the ArcGIS server. Editable image services also require a registered enterprise geodatabase.
The solution to this issue depends on how you register this enterprise geodatabase or database. Use the Data Stores tab of the ArcGIS Server Properties dialog box to register your enterprise geodatabase or database with the 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 layers 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 enter a new database connection, or click Import to browse to and use an existing database connection.
- Click the Add
- If you want the service to reference the same data as your map
- Import the data referenced by the layer 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 layers so that they all point to this geodatabase.
- 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 layer 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 layers so that they all point to this geodatabase.
- 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 services require 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. Editable image services also require a registered enterprise geodatabase.
Feature services published to ArcGIS Server require that all layers and stand-alone tables reference a single enterprise geodatabase or database using the same database connection. This enterprise geodatabase or database connection must also be registered with the ArcGIS server. All other data sources, such as shapefiles and file geodatabases, are not supported.