You are attempting to publish a map that uses a personal geodatabase. The case that the geodatabase is being used is captured in the <value> parameter. These cases include the following:
- Layer's data source is a personal geodatabase.
- Layer's join data source is a personal geodatabase.
- Layer's relate data source is a personal geodatabase.
- Stand-alone table's data source is a personal geodatabase.
- Stand-alone table's join data source is a personal geodatabase.
- Stand-alone table's relate data source is a personal geodatabase.
- Convert your personal geodatabase to a file geodatabase or enterprise geodatabase.
- Alternatively, you can remove the layer or stand-alone table, or remove the join or relate, if it is not needed in the map service.
ArcGIS servers no longer support layers referencing personal geodatabases.
Generally speaking, the best performance will be achieved by using datasets that are native to ArcGIS, that is, geodatabases and key raster and image datasets. In many cases, your unsupported dataset can be loaded into a geodatabase feature class that can then be used in a basemap layer or in a published service.
For best performance with geodatabases, use either enterprise geodatabases or file geodatabases. In some cases, with many simultaneous users, enterprise geodatabases are faster. Since enterprise geodatabases are DBMS based, they will scale better than file geodatabases in situations where you have a large number of users (hundreds of users or more).