00090: <value> requires a registered database

You are either publishing a map service with Feature Access (feature service) capability, a WFS capable map service with transaction support (WFS-T), or an Image Service with editing capability enabled, and you have not registered an enterprise geodatabase with the ArcGIS server.

The service type will be indicated by the name in the section labeled <value> in the error message.

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

Use the Data Stores tab of the ArcGIS Server Properties to register your enterprise geodatabase 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.
  1. 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.
  2. Enter a name for the database registration.
  3. Click Edit to register a new server database connection, or click Import to browse to, and use, an existing database connection.
  Note:

  If any of your layers reference data sources unsupported by feature or WFS-T services, such as shapefiles or file geodatabase feature classes, you may want to consider using a server-managed database, in which case the unsupported data will get copied to this enterprise geodatabase. This will make the layer usable in a feature service.

• If you want the service to reference the same data as your map, register this enterprise geodatabase with the ArcGIS server.
  1. Click Add next to the Registered Databases list box to open the Register Database dialog box.
  2. Enter a name for the database registration.
  3. Check Same as publisher database connection.
  4. Under Publisher database connection, click Add 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, you will need to register both the enterprise geodatabase used by the map and the enterprise geodatabase to be used by the service.
  1. Click Add next to the Registered Databases list box to open the Register Database dialog box.
  2. Enter a name for the registered database.
  3. Uncheck Same as publisher database connection.
  4. Under Publisher database connection, click Add to enter a new database connection, or click Import to browse to and use an existing database connection.
  5. Under Server database connection, click Add 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 for Server

More information

Feature, WFS-T, and edit-enabled Image services require that all layers in the service reference a single enterprise geodatabase using the same database connection. This enterprise geodatabase connection must also be registered with the ArcGIS server.

Data registration provides the server with a list of locations where the source data for your services originates. Data registration is an optional step that provides two main benefits:

• Data registration helps you validate whether your services are using data locations known and approved by the server administrator.
• In some cloud scenarios, data registration can provide automatic remapping of the paths to your data when you publish (and thereby upload) your map, globe, or other resource to the server.

Learn more about data storage considerations for, deployment scenarios for, and making your data accessible to the server