In many cases, error and warning messages are logged by the Spatial Server, but these messages are not forwarded to the ArcIMS Application Server or clients. These errors and warnings are logged because the Spatial Server couldn't fully process the request. However, a normal response is still returned to the client. The response will contain partial results, and some data may be missing or incorrectly rendered. This is in contrast to failed error messages. Failed error messages include the ERROR element in the response and are reported to the ArcIMS Application Server and clients.

Some common reasons are listed below for messages that are logged only in the Spatial Server log files. Some probable error or warning messages and their associated codes are also listed.

• A map is generated but a layer is missing
• Not all features for a layer are displayed
• A layer is displayed using the wrong symbology
• A map is generated but labels for a layer are missing
• The number of selected features is incorrect
• The returned image is not in the format requested
• The font for labels is incorrect
• After a query, no features are returned
• After a query, records are not returned for all selected features
• During an extract request, not all requested layers are included in the ZIP file
• No addresses are returned from a geocode request
• In an ArcMap Image Service layout, the height and width are not the expected values

Problem: A map is generated but a layer is missing.

Solution: Check the Image Server and ArcMap Image Server log files. Although a map was returned, there may be some warning or error messages included in the log files. Some common reasons for a missing layer are:

• A connection to a datasource cannot be made.
  • [ERR2004] Dataset "{dataset name}" cannot be created. Dataset is missing, unknown type, or invalid. [dynamic layer]
  • [ERR2007] Dataset "{dataset name}" cannot find workspace "{workspace name}". Check if the workspace name is correct. [dynamic layer]
  • [ERR2008] Workspace "{workspace name}" not found.
  • [ERR2011] Cannot connect with {workspace type} name="{workspace name}".
  • [ERR2107] Cannot validate file {file name}.
  • [ERR2401] Cannot connect to {ArcSDE server, instance, user}.
  • [ERR2402] Field {field name} not found.
  • [ERR2406] (SDE connection error code {[error code} {message} )
  • [ERR2501] Cannot open file {dbf file}.
  • [ERR2504] {file name} - SHP, SHX or DBF files not found in dir {directory}.
• A layer ID was included that does not exist in the service or list of dynamic layers.
  • [ERR0903] Buffer Target Layer with ID {ID} not found.
  • [ERR2003] Fromlayer="{layer ID}" - this layer ID not found.
• Output from a SEPARATELAYER is missing or incorrect.
  • [ERR0961] Layer {ID} is not an acetate layer.
  • [WRN0946] SEPARATELAYER {layer id} dimensions are too big or too small, reset to IMAGESIZE values.
• A data field was referenced that does not exist for a value map.
  • [ERR0912] VALUEMAPRENDERER lookupfield not found: {lookup field}.
  • [ERR2109] Field {field name} not found.
• A dynamic layer was included in the request, but the service does not allow dynamic layers.
  • [ERR0506] Dynamic layers are not supported.
  • [ERR0918] Cannot add workspace. This service is not defined as dynamic.
  • [ERR0948] Cannot add dynamic layer. This service is not defined as dynamic.
• A referenced join table does not exist.
  • [ERR2107] Cannot validate file {file name}. (Shapefiles)
  • [ERR2404] Join table {ArcSDE table name} not found. (ArcSDE)
• An incorrect symbol for the layer type or the renderer type was referenced.
  • [ERR0951] Error parsing SIMPLERENDERER symbol.
  • [ERR0909] Error parsing VALUEMAPRENDERER EXACT symbol.
  • [ERR0910] Error parsing VALUEMAPRENDERER RANGE symbol.
  • [ERR0911] Error parsing VALUEMAPRENDERER OTHER symbol.
• A reference was made to a gif or jpg image for one of the raster symbols, and the image does not exist or an incorrect path name was given.
  • [WRN0913] Could not open RASTERMARKERSYMBOL image: {image name}.
  • [WRN0924] Could not open RASTERFILLSYMBOL image: {image name}.
  • [WRN0928] No 'image' attribute for RASTERMARKERSYMBOL.
  • [WRN0929] No 'image' attribute for RASTERFILLSYMBOL.
• The shapefile for the layer is invalid. To test for invalid shapefiles, try to open them in Author or ArcExplorer-Java Edition. If a file is invalid, it is not included in the list of available data in Catalog.
  • [ERR2501] Cannot open file {dbf file}.
  • [ERR2504] {file name} - SHP, SHX or DBF files not found in dir {directory}.
  • [ERR2506] DBF file is invalid (field {field name} duplicated) - {dbf file}.
• In ArcMap Image Services, the map is generated with unexpected results due to an underlying problem in ArcObjects.
  • [ERR0526] HRESULT description: {message}
• Not in log files: no error or warning message is written to the log files when an incorrect symbol is used with a renderer, such as when a line symbol is used for a point layer or a polygon symbol is used for a point or line layer. However, the layer will not display. See the ArcXML Programmer's Reference Guide for valid symbols for a layer type. Also, these types of mistakes can be avoided by testing the request or map configuration file using the ArcXML DTD.

Problem: Not all features for a layer are displayed.

Solution: Check the Image Server log files. Although a map was returned, there may be some warning or error messages included in the log files. Some common reasons why features are missing are:

• The image feature limit has been exceeded.
  • [ERR0953] Featurelimit is reached for this layer. Some features were not drawn.
• Not in log files: the process of image generalization has removed features. See IMAGEGENERALIZATION in the ArcXML Programmer's Reference Guide for more information.
• Not in log files: features are missing near the horizon on a projected layer. An inappropriate projection for the data may be the problem. Another reason may be that the layer should be densified. See DENSIFY in the ArcXML Programmer's Reference Guide for more information.

Problem: A layer is displayed using the wrong symbology.

Solution 1: Check the Image Server log files. The layer may have a warning message indicating the problem. In many cases, the problem is that an element in the request or map configuration file has an incorrect attribute value. In this situation, the default attribute value was used instead. Many of these mistakes can be avoided by testing the request or map configuration file using the ArcXML DTD.

• [WRN0907] Could not set mapunits for SCALEBAR.
• [WRN0908] Could not set scaleunits for SCALEBAR.
• [WRN0912] Could not parse SIMPLEMARKERSYMBOL type. Default used.
• [WRN0914] Could not parse SIMPLELINESYMBOL type. Default used.
• [WRN0915] Could not parse SIMPLELINESYMBOL captype. Default used.
• [WRN0916] Could not parse SIMPLELINESYMBOL jointype. Default used.
• [WRN0917] Could not parse HASHLINESYMBOL type. Default used.
• [WRN0918] Could not parse SIMPLEPOLYGONSYMBOL filltype. Default used.
• [WRN0919] Could not parse SIMPLEPOLYGONSYMBOL boundarytype. Default used.
• [WRN0920] Could not parse SIMPLEPOLYGONSYMBOL boundarycaptype. Default used.
• [WRN0921] Could not parse SIMPLEPOLYGONSYMBOL boundaryjointype. Default used.
• [WRN0923] Could not parse GRADIENTFILLSYMBOL type. Default used.
• [WRN0934] Invalid size for RASTERMARKERSYMBOL. Reset to defaults.
• [WRN0935] Invalid RASTER_RANGE: 'lower' is equal or more than 'upper'.

Solution 2: Check the ArcMap Image Server log files. The acetate layer may have a warning message indicating the problem. In many cases, the default was used instead. Many of these mistakes can be avoided by testing the request using the ArcXML DTD.

• [WRN0502] Unknown fill type. Default value is used.
• [WRN0505] Unknown line type. Default value is used.
• [WRN0506] Unsupported fill type. Type solid is used instead.

Problem: A map is generated but labels for a layer are missing.

Solution: Check the Image Server log files. Although a map was returned, there may be some warning or error messages included in the log files. Many of these mistakes can be avoided by testing the request or map configuration file using the ArcXML DTD. Some common reasons that cause the labels to not display are:

• An incorrect label symbol was referenced for the renderer type. For example, SIMPLELINESYMBOL, which is not a label symbol, was used inside SIMPLELABELRENDERER.
  • [ERR0950] Error parsing SIMPLELABELRENDERER symbol.
  • [ERR0905] Error parsing VALUEMAPLABELRENDERER EXACT symbol.
  • [ERR0906] Error parsing VALUEMAPLABELRENDERER RANGE symbol.
  • [ERR0907] Error parsing VALUEMAPLABELRENDERER OTHER symbol.
  • [WRN0930] Unknown renderer for TEXTSYMBOL.
  • [WRN0931] Unknown renderer for SHIELDSYMBOL.
  • [WRN0932] Unknown renderer for RASTERSHIELDSYMBOL.
  • [WRN0933] Unknown renderer for CALLOUTMARKERSYMBOL.
• A reference was made to a data field that does not exist for a value map.
  • [ERR0908] VALUEMAPLABELRENDERER lookupfield not found: {0}.
• A gif or jpg image for RASTERSHIELDSYMBOL was improperly referenced, and the image does not exist or an incorrect path name is given.
  • [WRN0926] Could not open RASTERSHIELDSYMBOL gif image: {0}.
  • [WRN0927] No 'image' attribute for RASTERSHIELDSYMBOL.
• CALLOUTMARKERSYMBOL was used on a line layer.
  • [ERR0901] CALLOUTMARKERSYMBOL is not supported for line feature types.

Problem: The number of selected features is incorrect.

Solution: Check the Image Server log files. There is likely a problem with the query associated with the layer. Some common mistakes are:

• An invalid value was used for a spatial filter relation. All features for the queried layer are returned.
  • [ERR2009] Relation in SPATIALFILTER tag is incorrect.
• The layer selected for the filter is invalid. A map is generated but no features for the query layer are displayed.
  • [ERR2004] Dataset "{dataset name}" cannot be created. Dataset is missing, unknown type, or invalid.
• The SQL clause is invalid. A map is generated but no features for the query layer are displayed.
  • [ERR2106] User specified SQL clause is invalid. WHERE string is: {'where' clause} (Shapefiles)
  • [ERR2108] Joinexpression attribute is invalid; specified tables cannot be joined. (Shapefiles)
  • [ERR2404] Join table {ArcSDE table name} not found. (ArcSDE)
  • [ERR2405] User specified SQL clause is invalid. WHERE string is: {string} (ArcSDE)
• The geometry for a buffer is invalid.
  • [ERR2010] Cannot build buffer.

Problem: The returned image is not in the format requested. For example, a PNG image was requested, but a jpg image was returned.

Solution: Check the Image Server or ArcMap Image Server log files. The layer may have a warning message indicating the problem. The requested image format may be invalid or listed as a disallowed format.

• [WRN0508] Type "{image format}" is not allowed. Default type "{image format}" is used instead.
• [WRN0936] Type {image format} is not allowed. Default type {image format} is used instead.

Problem: The font for labels is incorrect.

Solution: Check the Image Server log files. Make sure the font exists on all Spatial Server machines.

• [WRN0937] Performance warning: font {font} is not found. Global font cache is being reloaded.
• [WRN0938] Cannot find font {font} in font directory. Reset to default.

Problem: After a query, no features are returned.

Solution: Check the Query Server (for Image Services) or Feature Server (for Feature Services) log files for error or warning messages. Some common mistakes are:

• None of the field names in the subfields attribute is valid. Make sure the correct layer is being used.
  • [ERR2109] Field {field name} not found. (Shapefiles)
  • [ERR2402] Field {field name} not found. (ArcSDE)
• An invalid value is used for a spatial filter relation. All features for the query layer are returned.
  • [ERR2009] Relation in SPATIALFILTER tag is incorrect.
• The SQL clause is invalid. A map is generated but no features for the query layer are displayed.
  • [ERR2106] User specified SQL clause is invalid. WHERE string is: {'where' clause} (Shapefiles)
  • [ERR2108] Joinexpression attribute is invalid; specified tables cannot be joined. (Shapefiles)
  • [ERR2404] Join table {ArcSDE table name} not found. (ArcSDE)
  • [ERR2405] User specified SQL clause is invalid. WHERE string is: {string} (ArcSDE)
• The geometry for a buffer is invalid.
  • [ERR2010] Cannot build buffer.
• Not in log files: the GET_FEATURES beginrecord attribute is out of range.

Problem: After a query, records are not returned for all selected features.

Solution: Check the Query Server (for Image Services) or Feature Server (for Feature Services) log files. A preset feature limit may have been exceeded. For more information on feature limits, see Change the feature limit for a query.

• The feature limit set in the Feature/Query Server configuration files, aimsfs.cfg and aimsqs.cfg, has been exceeded.
• A feature limit set for a layer in a map configuration file using SPATIALQUERY featurelimit has been exceeded.

Problem: During an extract request, not all requested layers are included in the ZIP file.

Solution: Check the Extract Server log files. Although a ZIP file was returned, there may be some warning or error messages included in the log files. Some common reasons why data is missing from a ZIP file are:

• A dynamic layer was included in the request, but the service does not allow dynamic layers.
  • [ERR0606] Cannot add workspace. This service is not defined as dynamic.
  • [ERR0608] Cannot add dynamic layer. This service is not defined as dynamic.
• A layer was incorrectly projected.
  • [WRN0944]Image layer {layer name} does not include COORDSYS. The layer has been drawn unprojected.
• The referenced layer ID does not exist in the service or list of dynamic layers.
  • [ERR0607] Could not find layer with ID {ID}.
  • [ERR2003] Fromlayer="{layer ID}" - this layer ID not found.
• A referenced join table does not exist
  • [ERR2107] Cannot validate file {file name}. (Shapefiles)
  • [ERR2404] Join table {ArcSDE table name} not found.
• A connection to a datasource cannot be made.
  • [ERR2004] Dataset "{dataset name}" cannot be created. Dataset is missing, unknown type, or invalid.
  • [ERR2007] Dataset "{dataset name}" cannot find workspace "{workspace name}". Check if the workspace name is correct. [dynamic layer]
  • [ERR2008] Workspace "{workspace name}" not found.
  • [ERR2011] Cannot connect with {workspace type} name="{workspace name}".
  • [ERR2107] Cannot validate file {file name}.
  • [ERR2401] Cannot connect to {ArcSDE server, instance, user}.
  • [ERR2402] Field {field name} not found.
  • [ERR2406] (SDE connection error code {[error code} {message} )
  • [ERR2501] Cannot open file {dbf file}.
  • [ERR2504] {file name} - SHP, SHX or DBF files not found in dir {directory}.
• The shapefile for the layer is invalid. To test for invalid shapefiles, try to open them in Author or ArcExplorer 9. If a file is invalid, it is not included in the list of available data in Catalog.
  • [ERR2501] Cannot open file {dbf file}.
  • [ERR2504] {file name} - SHP, SHX or DBF files not found in dir {directory}.
  • [ERR2506] DBF file is invalid (field {field name} duplicated) - {dbf file}.

Problem: No addresses are returned from a geocode request.

Solution: Check the Geocode Server log files for error messages. Some common reasons are:

• No house number was included in the request.
  • [ERR0827] House number is missing - the address cannot be processed.
• The geocode index files cannot be found.
  • [ERR0808] File not found : {file}.
  • [ERR0809] Geocoding index not found for layer with ID {ID}.
  • Not in log files: the GCI index file exists but is invalid. If unsure, reindex the geocode layer in ArcIMS Author.

Problem: In an ArcMap Image Service layout, the height and width are not the expected values.

Solution: Check the ArcMap Image Server log files.

• [WRN0510] Width or Height is invalid in IMAGESIZE. Default is used.