ArcGIS Pro
  • Overview
  • Extensions
    • Exploration and Visualization
    • Imagery
    • Customize and Create
    • Cartography
    • Analytics Data Science
    • Share your Work
    • Launch New Capabilities
    • Developer Tools
    • Data Management
  • Free Trial
  • Resources
    • Pricing
Pricing
  • Home
  • Get Started
  • Help
  • Tool Reference
  • Python
  • SDK
HelpShare your workAnalyzer error messages

Share with ArcGIS Pro

Share with ArcGIS Pro Understanding services, layers, and maps

Share web layers

Introduction to sharing web layers Web feature layer Web tile layer Vector tile layer Map image layer Stand-alone table Web scene layer Web imagery layer Web elevation layer Service parameters

Publish a hosted web layer from a web feature layer

Publish a hosted web layer from a web feature layer

Save a service definition

Introduction to saving service definitions Save a service definition for a web layer Save a service definition for a map service Publish a service definition

Share web maps and web scenes

Share a web map Configure a web map Save a web map Share a web scene Configure a web scene

Share a package

Introduction to sharing packages Share a project package Share a map package Share a layer package Share a tile package Share a vector tile package Share a scene layer package Share a geoprocessing package Share a deep learning model package Share a mobile map package Share a mobile scene package

ArcGIS Publisher

What is the ArcGIS Publisher extension? Tutorial: Create an offline map Create an offline scene

Share a web style

Share a web style

Share a locator

Introduction to sharing locators Share a locator Set properties on locators shared to your portal Overwrite a locator

Share a task item

Share a task item Save a map file Save a layer file Save a layout file Save a style file

Export a map or layout

Introduction to export a map or layout Export to AIX Export to BMP Export to EMF Export to EPS Export to GIF Export to JPEG Export to PDF Export to PNG Export to SVG or SVGZ Export to TGA Export to TIFF

Print a map or layout

Print a map or layout

Publish to a stand-alone server

Publish services Map Service Geocode Service Image Service Geoprocessing Service

Sharing job status

Sharing job status Manage registered data stores Analyze your GIS resource

Analyzer error messages

00001: Map does not have layers 00002: Map does not have a spatial reference 00003: Layer's data source is inaccessible 00007: Layer's definition query is invalid 00025: Selection layers are not supported 00031: Layer contains representation rule <value> which uses custom geometric effect or marker placement 00032: Standalone table's data source is inaccessible 00033: Standalone table's data source is not supported 00035: Layer contains representation rule <value> with geometric logic error 00044: The layer type or data source is not supported for schema only packages 00045: A layer description is required for packaging 00047: Layer's dataset is using an unknown coordinate system 00053: Layer is being shared with custom feature 00056: <value> contains multiple layers with the same name: <layer name> 00057: Layer name contains invalid characters 00062: Map contains data that does not use the same connection to an enterprise geodatabase 00079: Cache spatial reference does not match map/dataset/layer spatial reference 00085: Layer uses an unsupported renderer or property 00091: Schema packages do not support multiple workspaces 00093: Map description is required for packaging 00094: Participating locator cannot be loaded or is missing 00096: Locator is invalid 00101: OGC service's Name property is empty 00102: <value> does not contain a required layer type for <value> 00105: The layer type or data source is not supported for packages 00115: Layer name is empty 00123: Shape field is not visible 00127: <value> uses VBScript and you are publishing to ArcGIS Server (Linux) 00129: Map has <value> that records Editor Tracking dates in database time zone, but time zone has not been defined 00130: Map name is empty or contains invalid characters 00134: Layer's data source is not supported 00135: Standalone table's data source is not supported 00146: The <value> extension needed for layer <value> is not <value> 00147: The <value> is not licensed on the ArcGIS Server 00154: Layer's map is using an unknown coordinate system 00155: A transformation from the map's datum to WGS 1984 Major Auxiliary Sphere is required 00156: Locator with place-name alias table is not supported 00168: Geometric networks cannot be copied with a Basic license 00169: Standalone table name is empty 00170: Maximum Image Size of Requests of the mosaic dataset must be greater than 4096 X 4096 00171: The estimated amount of credits exceeds the amount available by <value> 00172: There are no credits available to publish this service 00175: <value> exceeds operating system limit 00176: <value> path exceeds operating system limit 00177: Path exceeds operating system limit 00184: Layer is not configured for or cannot be used with the Sync capability 00185: Table is not configured for or cannot be used with the Sync capability 00186: Datasets with mixed registration types cannot be used with the Sync capability 00189: The network dataset must be in a geodatabase 00191: Invalid feature service capabilities configuration for sync 00198: Locator must be at least version 10.0 00199: Remote locators not allowed 00200: Locator selection criteria are not supported 00210: <Value> uses the same layer ID as another layer/table: <value> assigned 00211: <value> cannot be used with sync capability 00212: Display field <value> must be visible 00216: Map does not contain a basemap 00217: Multipatch layer cannot be published to current portal 00220: The layer type is not supported in runtime content 00221: Feature layer is displaying more than 2000 features 00225: A transformation from the map's datum to WGS 1984 is required 00226: In-memory joins and relates are not supported 00227: Cached services do not support map rotation 00229: <Value> uses an unsupported spatial reference 00230: <value> has a different projection than the <value>'s projection 00231: Layer's data source must be registered with the server 00232: Standalone table's data source must be registered with the server 00233: Elevation service has a different projection than the scene's projection 00234: Layer's tiling scheme is not supported in the web scene viewer 00235: Tiled service layers must use <value> tiling scheme 00236: Layer uses an unsupported elevation setting 00237: Layer's data source cannot be replaced 00238: Standalone table's data source cannot be replaced 00239: Basemap's tiling scheme is not supported 00240: The tile cache size that will be generated locally exceeds the available disk space 00241: Field <value> is not supported as a display field 00242: Spatial reference of the map must match the spatial reference of the vector tile package: <value> 00243: 3D model marker for <value> exceeds the per symbol layer file size limit 00244: Raster data source does not have pyramids 00245: <value> requires enabling the option to only allow true curve updates by true curve clients 00246: Geoprocessing history items with errors cannot be included in the package 00248: Vertical transformation are not supported in web scenes 00251: The map must have the same coordinate system as the network dataset 00252: Tiling scheme is not supported for vector tile layers 00254: Multipoint layer type is not supported in web scene 00257: The root tile must overlap the data sufficiently for features to draw 00258: 3D model markers are not displayed in real-world units 00259: 3D rotation order in layer's symbology must be YXZ 00260: Toolbox <value> is inaccessible 00261: <capability> is enabled, but dataset <value> is not registered as branch versioned 00263: Datasets from branch versioned workspaces may only reference the DEFAULT branch: dataset <value> does not reference the DEFAULT branch 00264: Branch versioned dataset, <value>, is not supported from a versioned workspace when the service is editable. 00265: Publishing user, <value>, is not the <value> creator user, <value>. 00266: Sharing multiple <value> layers as a feature layer is not supported. 00268: All fields in <value> datasets must be visible: field <value> in layer <value> is not 00269: A <value> dataset may only be referenced by one layer: dataset <value> is referenced by layers <value> and <value>. 00270: Layers referencing <value> datasets must not contain definition queries: layer <value> contains a definition query. 00271: Versioned dataset, <value>, is not supported from a branch versioned workspace when the service is editable 00273: Display filters are not supported 00274: Multipoint layer type is not supported in web scene 00277: <capability> is enabled, but the connected geodatabase user, <value>, is not the branch versioned dataset’s owner, <value> 00278: The dataset, <value>, participates in a <value> but is not registered as branch versioned. 00279: When Version Management is enabled, the service must be editable. 00280: The combination of the scene's XY and Z unit is not supported 00288: Extent of the map and existing web layer must overlap 00290: Cannot connect through admin URL or services URL 00294: Editable feature services cannot contain database views. <value> is a database view 00296: Web layer name must start with a letter or underscore when WFS is enabled 00297: <value> layers must be shared with everyone 00298: Validation error table <value> must be referenced by a layer 00299: Validation error table <value> must be referenced by only one layer. 00300: No LRS dataset present in the LRS. Upgrade the LRS by running the Modify LRS geoprocessing tool on your LRS. 00301: Layers from more than one LRS present in the map. Update the map to have layers from only one LRS and publish. 00302: All fields in datasets with <value> must be visible: field <value> in layer <value> is not 00305: Network analysis layer is referencing a network service <value> 00308: Cannot load the Statistical Data Collection 00309: Cannot open Statistical Data Collection feature class 00310: GeoEnrichment service is not configured 00311: Script language is not supported: GeoEnrichment service supports only Python expressions 00312: Country cannot be determined for the Statistical Data Collection or the country is not available in the GeoEnrichment service 00319: Custom calculations are not supported by the version of GeoEnrichment Server to which you are connected 00320: The model definition file is corrupt 00321: Inputs are inaccessible 00322: Model type is invalid 00323: Shared instance pools do not support <value> 00325: The dictionary is an older version that is not supported for web styles 00326: The style does not contain a valid <value> symbol 00327: Style item key of <value> contains invalid characters 00328: Symbol <value> is restricted and cannot be shared 00329: <value> is unsupported for dictionary web styles 00330: ArcGIS Enterprise is currently in read-only mode 00331: Style <value> is inaccessible 00333: Symbol <value> exceeds the file size limit 00334: The symbology value <value> with label '<value>' is not defined in the subtype field '<value>' for dataset <value> and feature access is enabled 00336: The Sync Version Creation option None is not supported for data that is registered for traditional versioning; layer count=<value> 00337: When using the Create a version for each downloaded map Sync Version Creation option with branch versioned data, the data must have replica tracking enabled.  Branch versioned datasets without replica tracking count = <value> 00338: For the Sync Version Creation option Create a version for each user, branch versioned datasets are not supported; layer count=<value> 00339: Locator was built with roles or capabilities not compatible for sharing to this version of ArcGIS Server 00341: A topology dataset may only be referenced by one layer: dataset <value> is referenced by <value> layers. 00342: Multiple topology layers are not supported. 00343: Multiple topology layers are not supported—a Parcel Fabric contains a topology. 00344: The web layer being published cannot be consumed by ArcGIS Pro without all the Topology layers being present. Topology layer <value> is missing. 00345: A topology system layer is not in the map: <value> 00346: Topologies require Version Management and Validation to be both enabled or both disabled. 00347: Dataset is not branch versioned - All datasets in a topology must be branch versioned. 00348: Topology layer is not supported on a stand-alone ArcGIS Server. 00349: Topology layer is not supported with this version of ArcGIS Server. Minimum version: <value> 00351: Topology layer is not supported on a non-federated ArcGIS Server. 00352: The subtype field of a topology feature layer is not visible. 00353: The subtype field of a topology layer must be editable. 00354: Layers referenced by topology datasets must not contain definition queries: layer <value> contains a definition query. 00355: The Network Dataset is configured to retrieve live traffic from a portal other than the one to which the service is being published 00360: A <value> layer is not supported with this version of ArcGIS Server. Minimum version: <value> 00361: This locator is not supported for publishing. 00362: Datasets expose reserved field names 00363: Layer, <value>, cannot be published because it is stored in a mobile geodatabase 00364: Stand-alone table, <value>, cannot be published because it is stored in a mobile geodatabase

Analyzer warning messages

Back to Top
Back to Top

00184: Layer is not configured for or cannot be used with the Sync capability

This ArcGIS 2.7 documentation has been archived and is no longer updated. Content and links may be outdated. See the latest documentation.

In this topic

  1. Solutions
  2. More information

You are sharing a web feature layer that has sync enabled. The data being shared is not configured for sync-based workflows.

Solutions

  • If the web layer will not be used in sync-based workflows, click the Configuration tab in the sharing pane, click Configure Web Layer Properties Configure Web Layer Properties next to Feature, and uncheck Enable Sync.
  • Configure the data for sync. See below for sync requirements.

More information

For sync-based workflows, all layers in the web feature layer must either be versioned and contain a Global ID field or be nonversioned, have archiving enabled, and contain a Global ID field. If the layer participates in a relationship class or has attachments, the relationship class or attachments must be related using a Global ID field as the primary key.

For more information, see Prepare data for offline use.

In this topic
  1. Solutions
  2. More information