56 MAPVIEWER-00001 to MAPVIEWER-06057

MAPVIEWER-00001: No 'xml_request' parameter found in the request.: Cause: The incoming HTTP request did not contain the mandatory parameter named 'xml_request'.; Action: Ensure the HTTP request for MapViewer contains the required parameter.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00002: Could not get a free MapMaker. Server is busy?: Cause: MapViewer could not obtain the necessary resource to process an incoming request.; Action: Try increasing the value of the "number_of_mappers" attribute in the definition of the involved data source.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00003: SQL error occurred while generating map.: Cause: MapViewer encountered an error while executing a SQL query.; Action: Check the MapViewer server logs for details about the SQL exception and take appropriate actions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00004: Unable to add a predefined theme.: Cause: MapViewer could not add or load a predefined theme while processing the current map request.; Action: Ensure the predefined theme exists in the database or is accessible via the given data source.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00005: Error while compressing raw image data.: Cause: MapViewer could not successfully compress a generated map image into the requested file format.; Action: Check the MapViewer server logs for the actual stack trace and take appropriate actions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00006: Location for saving map image files not specified.: Cause: MapViewer could not obtain the path information for saving generated map files.; Action: Check the MapViewer configuration file and make sure a path for saving image files is specified or the default path is a valid one.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00007: No map image generated.: Cause: MapViewer did not generate a map image.; Action: Check the MapViewer server logs for details/exceptions and take appropriate actions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00008: Unable to add local theme(s).: Cause: MapViewer could not create a new local theme for the current map request.; Action: Check the MapViewer server logs for details/exceptions and take appropriate actions. Make sure the individual Geo-Features are in proper format.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00009: Unable to add JDBC theme(s).: Cause: MapViewer could not create a new JDBC (dynamic) theme for the current map request.; Action: Check the MapViewer server logs for details/exceptions and take appropriate actions. Make sure the data source information is correct, and characters in the user-supplied SQL query are properly escaped for XML.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00010: Error loading MapViewer configuration file.: Cause: MapViewer could not properly load its configuration file.; Action: Make sure the XML configuration file is in valid and well-formed format.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00011: Error creating a map data source.: Cause: MapViewer could not create a new data source.; Action: Make sure correct database connection information is supplied, including host name, database instance name/sid, listener port, and login user/password. Also make sure the host name or IP address is reachable by the host running the MapViewer server.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00012: Error obfuscating data source password in the config file.: Cause: MapViewer could not obfuscate the login password for a data source defined in its configuration file.; Action: Make sure the password is prefixed with an exclamation point (!).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00013: Clear-text passwords in the config file must be prefixed with a '!' (exclamation mark).: Cause: Clear text password in the MapViewer configuration file was not prefixed with '!'.; Action: Make sure the database login password for any data source defined in the configuration file is prefixed with an exclamation point (!).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00014: Error adding a MARKER style from an image URL.: Cause: MapViewer could not create a dynamic MARKER style that is based on a URL.; Action: Make sure the URL of the image is reachable from the host running the MapViewer server. If MapViewer is running behind a firewall, you may need to set up HTTP proxy information in MapViewer's configuration file, or via JVM run-time properties.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00015: Cannot fetch image from given URL: Cause: MapViewer could not fetch and load an image from a given URL.; Action: Make sure the URL of the image is reachable from the host running the MapViewer server. If MapViewer is running behind a firewall, you may need to set up HTTP proxy information in MapViewer's configuration file, or via JVM run-time properties.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00016: Error while attempting to clear a mapping metadata cache.: Cause: MapViewer could not clear the cached mapping metadata (style/theme/basemap definitions) for a given data source from memory.; Action: Make sure a correct data source name is specified. Also check MapViewer server logs for possible exceptions and stack traces.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00017: MapViewer is not ready. Please try again later.: Cause: MapViewer was still starting core services such as the mapping servlet. If this error still occurs 30 seconds after starting MapViewer, it may be stuck trying to connect to one or more database instances.; Action: Check and monitor MapViewer server logs to see which server has not been started yet. Check data source definitions in the configuration file and make sure all the database instances involved are up and running.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00018: Error parsing XML map request.: Cause: MapViewer encountered an error while parsing an XML map request.; Action: Make sure a well formed and valid XML map request is sent to the MapViewer server.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00019: Specified data source does not exist.: Cause: A specified data source did not exist or was not known by this MapViewer server.; Action: Make sure a correct data source name is supplied.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00020: Invalid general-purpose or admin XML request.: Cause: The incoming admin or non-map request was invalid or not supported.; Action: Make sure only valid and supported requests are sent to the MapViewer
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00021: No data source specified in the XML request.: Cause: The incoming request did not specify any data source name, and the MapViewer server has no default data source.; Action: Make sure a valid data source is specified as part of the request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00101: XML map request: invalid 'geoFeature' element found.: Cause: The incoming map request contained an invalid 'geoFeature' element.; Action: Make sure all the 'geoFeature' elements have valid syntax.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00102: XML map request: invalid 'box' element found.: Cause: The incoming map request contained an invalid 'box' element.; Action: Make sure the 'box' element has valid syntax.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00103: XML map request: 'geoFeature' element must have a geometry defined.: Cause: The incoming map request contained one or more 'geoFeature' elements that do not contain any geometry data.; Action: Make sure all 'geoFeature' elements contain a geometry.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00104: XML map request: invalid geometry definition found.: Cause: A 'geoFeature' element with invalid geometry data was found in the XML map request.; Action: Make sure all 'geoFeature' elements contain a valid geometry.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00105: XML map request: 'geoFeature' does not support postal address.: Cause: A 'geoFeature' element with postal/street address was found in the XML map request.; Action: Currently 'geoFeature' elements could not use street address string to specify the location.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00106: XML map request: invalid JDBC theme definition.: Cause: The incoming map request contained an invalid JDBC theme.; Action: Make sure all JDBC themes have proper syntax.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00107: XML map request: 'center' element does not contain a 'geoFeature' sub-element.: Cause: The 'center' element of the incoming map request did not contain a 'geoFeature' sub-element.; Action: Ensure that the 'center' element has a 'geoFeature' sub-element that specifies a point geometry for the map center.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00108: XML map request: 'center' element must define either a 'size' or 'scale' attribute.: Cause: The 'center' element of the incoming map request did not contain any size or map-scale information.; Action: Ensure that the 'center' element has either a 'size' or 'scale' attribute that defines the map data window.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00109: XML map request: invalid map size or scale value.: Cause: The 'center' element of the incoming map request contained an invalid size or scale value.; Action: Make sure a proper value is specified for the 'size' or 'scale' attribute of the 'center' element in the XML map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00110: XML map request: invalid map height/width.: Cause: The incoming map request specified an invalid image width or height value.; Action: Make sure a proper value (positive integer) is specified for both the width and height attributes of the root 'map_request' element.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00111: XML map request: invalid theme (min/max) scale range.: Cause: Some theme(s) in the incoming map request contained an invalid min/max scale range specification.; Action: Make sure proper value scale ranges are set for all themes in the map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00112: XML map request: invalid WMS theme specified.: Cause: The incoming map request contained an invalid WMS theme.; Action: Make sure all WMS themes are properly defined in the XML map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00113: Permission denied for this operation.: Cause: The requested operation was not permitted by the MapViewer server.; Action: Make sure your operation is permitted by MapViewer. For example, the server may disallow JDBC themes in the map request, or disable direct INFO requests. You will need either to avoid performing these operations or to modify MapViewer configuration to allow these operations.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00114: Invalid type for dynamic binding parameter.: Cause: The incoming map request supplied invalid value(s) for a theme's binding variable.; Action: Make sure values for your theme's binding parameters are all of correct type.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00115: list_predefined_themes: No base map found for map tile layer.: Cause: The 'list_predefined_themes' request specified a map tile layer that is based on a nonexistent base map.; Action: Make sure the base map for the specified map tile layer exists in the database view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00116: list_predefined_themes: Map tile layer not found.: Cause: The 'list_predefined_themes' request specified a map tile layer that is not found.; Action: Make sure the specified map tile layer exists in the database view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01000: No themes to render.: Cause: The Map request had no base map or themes defined.; Action: Add a base map that contains a list of themes or define individual themes on your request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01001: Cannot load base map.: Cause: A database error may have happened while reading the base map definition from the USER_SDO_MAPS view, or the requested base map was not defined.; Action: Make sure the base map exists in the database; also check the MapViewer log for database errors and additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01002: Cannot load theme.: Cause: A database error may have happened while reading the theme definition from the USER_SDO_THEMES view, or the requested theme was not defined.; Action: Make sure the theme exists in the database; also check the MapViewer log for database errors and additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01003: Cannot load style.: Cause: A database error may have happened while reading the style definition from the USER_SDO_STYLES view. Or the requested style was not defined.; Action: Make sure the style exists in the database; also check the MapViewer log for database errors and additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01004: Bounding Themes returned null MBR. Themes were not rendered.: Cause: Bounding themes may have been used to define the query window for the map request, but it produced no spatial feature. The map request was aborted due to this condition.; Action: Change the bounding theme or themes definition, so the definition defines a select statement that returns one or more features. In Map Builder, this message can happen when previewing base maps with full extent (no center and size defined). Map Builder uses the first theme of the base map as the bounding theme when a full extent is applied. If this first theme returns no features for a full extent request, then you should remove it from the base map list of themes.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01005: No spatial data to render.: Cause: A full extent request (no center and size defined) returned no features.; Action: Change the theme or themes definition to select one or more features.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01006: Invalid style type for Point features.: Cause: The style type used could not be applied to render point features.; Action: Do not use AREA or LINE styles to render point features.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01007: Feature has no geometric representation.: Cause: The feature geometry was null.; Action: Check the feature geometry column in the database table.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01008: Cannot parse xml style string: missing closing ": Cause: The XML string was not correct and could not be parsed.; Action: Check for the missing closing character '"'.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01009: Invalid style class specified in xml style string.: Cause: Attribute class on the xml definition was undefined.; Action: Assign a valid value to attribute class (COLOR,LINE,TEXT,MARKER,AREA).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01010: Style cannot be created from a xml string that does not define the style class.: Cause: Unknown style class type defined.; Action: Change the attribute class value to a known type (COLOR,LINE,TEXT,MARKER,AREA).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01011: Cannot find a custom image renderer for format:: Cause: Image theme format was not supported and there was no custom image renderer defined for this format.; Action: Use a known image format (GIF,JPEG,PNG,TIFF) or implement a custom image renderer for this format.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01012: Cannot create image to render from byte array.: Cause: Image array of bytes may be null or corrupted.; Action: Check the image data source. If it comes from a database column, verify that the column content is not null. If the image content appears to be correct, then report the error to Oracle.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01013: Invalid base map definition.: Cause: The XML string for base map definition could not be parsed.; Action: Fix the XML string that defines the base map.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01014: Invalid styling rules definition.: Cause: The XML string for theme styling rules could not be parsed.; Action: Fix the XML string that defines the theme styling rules.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01015: Unable to retrieve theme definition.: Cause: The theme did not exist in USER_SDO_THEMES view.; Action: Add a theme definition to user themes view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01016: Theme with undefined styling rules.: Cause: The styling rules section of theme XML definition was null.; Action: Ensure that a theme styling rules section is defined in the theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01017: Undefined image column attribute in image theme definition.: Cause: The image theme definition did not contain the image column attribute.; Action: Define attribute 'image_column' in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01018: Undefined image format attribute in image theme definition.: Cause: The image theme definition did not contain the image format attribute.; Action: Define attribute 'image_format in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01019: One or more attributes missing in image theme definition.: Cause: Some mandatory attributes were missing from the image theme definition.; Action: Attributes for defined image column ('image_column') and image format ('image_format') must be defined in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01020: Undefined network name attribute in network theme definition.: Cause: The network theme definition did not contain the network name attribute.; Action: Define the attribute 'network_name' in the network theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01021: Undefined topology name attribute in topology theme definition.: Cause: The topology theme definition did not contain the topology name attribute.; Action: Define the attribute 'topology_name' in the topology theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01022: Undefined WFS service URL attribute in WFS theme definition.: Cause: The WFS theme definition did not contain the service URL attribute.; Action: Define the attribute 'service_url' in the WFS theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01023: Unable to find entry in ALL_SDO_GEOM_METADATA table for theme:: Cause: Theme base table and spatial column have not been registered in the user metadata view (USER_SDO_GEOM_METADATA).; Action: Register the theme base table and spatial column in the user metadata view, by inserting a row in the USER_SDO_GEOM_METATADA view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01024: Unable to convert query window SRID to theme SRID.: Cause: Conversion of map request query window projection to theme projection has failed. The database procedure sdo_cs.transform was used to convert coordinates from one SRID to another SRID.; Action: Check the log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01025: Cannot use ratio scale mode with theme that has unknown SRID.: Cause: A request with a ratio scale was attempted, but the data did not contain a valid Oracle SRID.; Action: Assign a valid SRID to the spatial data.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01026: Unable to get an instance of spatial provider.: Cause: A custom spatial provider was not be defined in MapViewer's configuration file, or the provider class path was not accessible.; Action: Check the spatial provider section in the MapViewer configuration file for the definition of the provider. If it is defined there, check the libary jar file path, and make sure it is part of the classpath definition for the application.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01027: Custom geometry theme must have a spatial data provider defined.: Cause: The custom geometry theme definition did not contain the spatial provider attribute.; Action: Define the attribute 'provider_id' in the custom theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01028: Custom spatial data provider is null.: Cause: The custom spatial data provider was not initialized and is null.; Action: Check if the provider name is defined in the theme definition, and also check if the provider class library is defined in the MapViewer configuration file and is part of the application classpath.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01029: Undefined geometry column for dynamic geometry theme.: Cause: A dynamic geometry theme definition did not contain the spatial column attribute.; Action: Define the attribute 'spatial_column' in the dynamic geometry theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01030: A set of four question marks separated by commas is required to define a geometry theme with a dynamic SDO_FILTER.: Cause: A set of questions marks was not used in the SDO_ORDINATE_ARRAY for a dynamic geometry theme with a SQL expression that also includes the spatial filter operator (SDO_FILTER). These question marks will be replaced with values based on the map request center and size.; Action: Use the following pattern for the ordinate array on the SOD_FILTER expression: SDO_ORDINATE_ARRAY(?,?,?,?).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01031: Not enough binding parameters defined.: Cause: The theme definition contained binding parameters on its query expression, but the parameters were not provided inn the map request.; Action: Pass the theme binding parameters to your theme definition, using the methods provided by the JavaScript API (Oracle Maps), or by the Java API; or if issuing a direct XML request, define the binding parameters in the theme section.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01032: GeoRaster spatial extent is null.: Cause: The GeoRaster object contained a null geometry as its spatial extent.; Action: Update the GeoRaster spatial extent using the PLSQL procedure sdo_geor.generateSpatialExtent.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01033: Invalid image stretch low value.: Cause: The image stretch low value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range.; Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01034: Invalid image stretch high value.: Cause: The image stretch high value was not numeric and ranging from 0 to 256. The default value 100 is used if the number is out of this range.; Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01035: Invalid brightness value.: Cause: The image brightness value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range; Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01036: Undefined brightness value for image processing.: Cause: The image brightness value was not defined, as required when a brightness operation is to be applied on a GeoRaster object.; Action: Define the parameter 'value' for brightness in the theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01037: Invalid contrast value.: Cause: The image contrast value was not numeric and ranging from 0 to 256. The default value 256 is used if the number is out of this range; Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01038: Undefined contrast value for image processing.: Cause: The image contrast value was not defined, as required when a contrast operation is to be applied on a GeoRaster object.; Action: Define the parameter 'value' for contrast in the theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01039: Invalid threshold value.: Cause: The image threshold value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range; Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01040: Invalid low threshold value.: Cause: The image threshold low value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range; Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01041: Invalid high threshold value.: Cause: The image threshold high value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range; Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01042: Invalid image column type for image theme.: Cause: The image theme data was not stored in a column of type BLOB or ORDIMAGE.; Action: Assign a valid image column in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01043: Network category is null.: Cause: The network model category information was null in the metadata view.; Action: Check the contents of column 'network_category' in the network metadata view USER_SDO_NETWORK_METADATA.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01044: Network geometry type is null.: Cause: The network model geometry type information was null in the metadata view.; Action: Check the contents of column 'geometry_type' in the network metadata view USER_SDO_NETWORK_METADATA.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01045: Undefined topology column for topology theme.: Cause: The topology theme definition did not contain the spatial column attribute.; Action: Define the attribute 'spatial_column' in the topology theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01046: WFS theme server URL is null.: Cause: The WFS server URL was not defined.; Action: Check if the WFS theme definition has a value for the attribute 'service_url'.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01047: WMS theme server URL is null.: Cause: The WMS server URL was not been defined.; Action: Check if the WMS theme definition has a value for attribute 'service_url'.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01048: Cannot load WMS map image.: Cause: The image could not be retrieved from the WMS server.; Action: Check if the WMS server URL defined in the theme definition is accessible. Change the timeout value in the theme definition if a timeout has happened.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01049: X or Y column not found in SQL query.: Cause: The SQL query string in a dynamic JDBC theme did not contain either x or y column.; Action: If your dynamic JDBC theme is using x and y columns to specify the location of a point theme (instead of an SDO_GEOMETRY column), make sure that both the x and y columns are present in the SQL query. Otherwise, check the query itself and make sure a proper SDO_GEOMETRY type column is selected.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02000: There is no database connection loaded.: Cause: Operation could not be performed unless a database connection has been added or loaded.; Action: Use Map Builder interface options to create or to add (load) a connection.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02001: Connection test failed.: Cause: The connection parameters were wrong, the database was down, or the listener was not running.; Action: Check the MapViewer log or console for database errors, and change connection parameters if necessary.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02002: Unable to register data source connection.: Cause: The connection parameters were wrong, the database was down, or the listener was not running.; Action: Check the MapViewer log or console for database errors. If the connection has been already added to Map Builder, check the connections parameters in the Map Builder preferences file (default file is oasmapbuilder.xml), and modify them if needed. Restart Map Builder to load the current preferences file. If it is a new connection being added, change the connection parameters and test the connection before trying to add it.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02050: Unable to save base map definition.: Cause: A database error may have happened while saving the base map in the USER_SDO_MAPS view.; Action: Check the MapViewer log for database errord.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02051: Unable to save style definition.: Cause: A database error may have happened while saving the style in the USER_SDO_STYLES view.; Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02052: Unable to save theme definition.: Cause: A database error may have happened while saving the theme in the USER_SDO_THEMES view.; Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02053: Unable to save tile layer definition.: Cause: A database error may have happened while saving the tile layer in the USER_SDO_CACHED_MAPS view.; Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02054: Unable to duplicate metadata.: Cause: A database error may have happened while saving a duplicate metadata.; Action: Make sure the new metadata name does not exist on the target database. Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02055: Unable to delete metadata.: Cause: A database error may have happened while removing metadata from a database view.; Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02100: Invalid advanced style type.: Cause: The style XML definition contained an invalid or unknown advanced style type.; Action: Fix the style XML definition with an external tool, and refresh the connection in Map Builder.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02101: Unable to build theme definition.: Cause: A database error may have happened while reading theme parameters.; Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02102: Unable to parse hexadecimal value.: Cause: The string value was not recognized as a valid hexadecimal expression.; Action: Use the pattern #xxxxxx to represent the hexadecimal color value. Character # must be first followed by six digits or letters. Each x may be a digit between 0 and 9, or one of the letters "a,b,c,d,e,f".
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02103: Unable to parse style definition.: Cause: Database-related errors or SQL exceptions may have happened while reading style parameters.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02104: System will not be able to save this file.: Cause: The file path was not accessible to the system.; Action: Define a file name with a valid system path.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02105: Unable to save HTML file.: Cause: An IO error may have happened while saving file on disk.; Action: Check the MapViewer log for error details, and change file name if needed.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02200: Invalid raster block size.: Cause: The block size was nor a positive even number and power of two.; Action: Define a value that is positive and a power of two, such as 64 or 128.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02201: Unable to create GeoRaster table.: Cause: Database-related errors or SQL exceptions may have happened while creating a GeoRaster table.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02202: Unable to create GeoRaster raster data table.: Cause: Database-related errors or SQL exceptions may have happened while creating a GeoRaster raster data table. A raster data table name can not be repeated over cross schemas.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02203: Unable to insert GeoRaster record.: Cause: Database-related errors or SQL exceptions may have happened while creating a new GeoRaster record.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02204: Unable to import image file.: Cause: Database-related errors or SQL exceptions may have happened while importing image into a GeoRaster record.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02205: Unable to georeference GeoRaster object.: Cause: Database-related errors or SQL exceptions may have happened while georeferencing the GeoRaster object.; Action: Check the MapViewer log for database-related errors or SQL exceptions, and change georeferencing parameters if necessary.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02206: Unable to update spatial extent of GeoRaster object.: Cause: Database-related errors or SQL exceptions may have happened while updating the spatial extent of the GeoRaster object.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02207: Unable to generate pyramids for GeoRaster object.: Cause: Database-related errors or SQL exceptions may have happened while generating pyramids for the GeoRaster object. Map Builder uses resampling mode NN.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02208: Unable to retrieve GeoRaster object size.: Cause: Database-related errors or SQL exceptions may have happened while retrieving the GeoRaster size from the metadata.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02209: Unable to save GeoRaster metadata.: Cause: Database-related errors or SQL exceptions may have happened while registering the GeoRaster spatial extent in the USER_SDO_GEOM_METADATA view.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02210: Unable to create spatial indexes for GeoRaster table.: Cause: Database-related errors or SQL exceptions may have happened while creating spatial indexes on the GeoRaster SPATIALEXTENT attribute.; Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02300: Spatial data provider is not registered.: Cause: The list of registered spatial data providers did not contain the provider name.; Action: Check the Map Builder preferences file (default file is oasmapbuilder.xml) to see if it defines the provider parameters. Spatial providers are registered at Map Builder startup if they are defined in the preferences file.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02301: Unable to initialize spatial data provider.: Cause: Initialization parameters were missing or were not accepted by the spatial provider.; Action: Check the spatial provider documentation for information about initialization parameters.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02302: Unable to create an instance of spatial provider class.: Cause: The library jar file location may not have been accessible to the application.; Action: Check the spatial provider parameters in the preferences file (default file is oasmapbuilder.xml), and modify the jar file location if necessary.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03001: MapViewer cannot process your map request. Check MapViewer log for details.: Cause: MapViewer could not process a map request sent by your Java application.; Action: Check the MapViewer server logs written when the error occurred. Correct any mistakes accordingly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03002: Cannot check the existance of: Cause: MapViewer could not find the specified mapping metadata or spatial data table.; Action: Make sure the mentioned item (metadata such as style/theme/basemap or spatial data table) exists in the data base.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03003: Cannot add a datasource:: Cause: MapViewer could not add a new data source per your map request.; Action: Adding a data source on-the-fly using the Java client API is no longer allowed. Data sources should be defined in the configuration file or added using the admin web page.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03004: cannot list pre-defined themes in:: Cause: MapViewer could not get the list of themes in the specified base map.; Action: Make sure the base map exists in the database and that it contains predefined themes.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03005: invalid image format specified.: Cause: The image format (for the map response) specified was invalid or not supported.; Action: Make sure that only image formats specified in the API are used in your code.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03006: Failed to establish HTTP connection to MapViewer service.: Cause: The client failed to connect to the MapViewer servlet.; Action: Make sure the networking configuration settings (such as proxy settings) are correct in the client. Also make sure the correct MapViewer URL is supplied.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03007: Failed to locate image URL in the XML map response.: Cause: The XML map response from the server did not contain a map image URL.; Action: Check MapViewer server logs to see if there is any error when processing the map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05500: Oracle Maps client internal error.: Cause: Oracle Maps client encountered an internal error.; Action: Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05501: Map tile layer not found. Check map tile layer name and/or data source name.: Cause: MapViewer server could not find the specified map tile layer.; Action: Make sure the map tile layer and data source do exist and their names are spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05502: Cannot get map tile layer config information.: Cause: The client could not get the map tile layer configuration information from the server.; Action: Make sure the map tile layer and data source do exist and their names are spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05503: FOI ID cannot be null.: Cause: The ID of the newly created FOI was null.; Action: Make sure the FOI ID is not null.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05504: MapViewer server base URL is not defined.: Cause: The MapViewer server base URL was not specified.; Action: Make sure the MapViewer server base URL is properly specified when creating the new MVMapView instance.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05505: Wrong map center point specified. It should be an MVSdoGeometry point.: Cause: The parameter passed as the map center into MVMapView.setCenter() or MVMapView.setCenterAndZoomLevel() was not a valid point MVSdoGeometry object.; Action: Make sure the map center parameter is specified as a valid point type MVSdoGeometry object.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05506: Invalid zoom level.: Cause: The specified zoom level was invalid.; Action: Make sure the zoom level value is not null and is within the predefined range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05507: Map tile layer name cannot be null.: Cause: The map tile layer name was null.; Action: Make sure map tile layer name is not null.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05508: FOI Id is already used, please pick a new Id.: Cause: The ID of the newly created FOI was already used by another FOI.; Action: Choose a different ID for the new FOI.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05509: Theme-based FOI layer name is used, please pick a new name.: Cause: The name of the newly created theme-based FOI layer was already used by another theme-based FOI layer.; Action: Choose a different name for the new theme-based FOI layer.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05510: Cannot find theme-based FOI layer.: Cause: The client could not find the given theme-based FOI layer.; Action: Make sure the theme-based FOI layer has already been added to the MVMapView instance.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05511: Error occurred when sending request to MapViewer server.: Cause: An error occurred when the client sent the request to the MapViewer server.; Action: Make sure the MapViewer server is running and accessible from the client.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05512: Not enough points have been drawn.: Cause: Not enough points were drawn when calling MVRedline.generate().; Action: Make sure enough points have been drawn before calling MVRedline.generate().
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05513: Not a valid line or polygon type MVSdoGeometry.: Cause: getLength() or getArea() was called on a MVSdoGeometry object that is neither a polyline nor a polygon.; Action: Make sure these two methods are called on a polyline or polygon MVSdoGeometry object.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05514: Must have a filtering geometry when in high-light only mode.: Cause: A filtering geometry was not specified for a highlight-only theme-based FOI.; Action: Make sure the filtering geometry is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05516: Synchronized remote call is not supported when using Oracle Maps' non-AJAX remoting.: Cause: An attempt was made to invoke a synchronized remote call when using the Oracle Maps non-AJAX remoting mechanism.; Action: Send an asynchronous remote call instead.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05517: Request string is too long for Oracle Maps' non-AJAX remoting.: Cause: The FOI request exceeded the length limit of the Oracle Maps non-AJAX remoting mechanism.; Action: Force the Oracle Maps client to use browser built-in AJAX remoting mechanism with MapViewer's built-in remoting proxy. Please refer to MVMapView.enableXMLHTTP for more information.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05518: Map tile layer hasn't been successfully added.: Cause: The map tile layer was not successfully added to the MVMapView instance.; Action: Make sure both of the following two conditions are met when adding a map tile layer to the MVMapView instance: 1. The MapViewer base URL is valid. 2. The map tile layer name and data source name are specified correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05519: One or more parameter is missing or invalid.: Cause: One or more parametesr in the function call were missing or invalid.; Action: Make sure all required parameters are specified correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05520: Geometry SRID is null.: Cause: The srid attribute of the MVSdoGeometry object was not specified.; Action: Make sure the srid is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05521: Call back function cannot be null when browser's builtin XMLHttp/XMLHttpRequest is disabled.: Cause: The callback function was not specified when Oracle Maps' non-AJAX remoting mechanism was used.; Action: Specify a callback function.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05522: Client side coordinate system conversion not supported.: Cause: The client tried to invoke client-side coordinate system conversion that is not supported.; Action: Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05523: Cannot process response from MapViewer server.: Cause: The client encountered an error when processing the response from the MapViewer server.; Action: Check the server response and server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05524: Theme feature highlighting is disabled for this theme.: Cause: The application tried to highlight or de-highlight a theme-based FOI layer that had theme feature highlighting disabled.; Action: Call MVThemeBasedFOI.enableHighlight to enable theme feature highlighting.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05525: Theme has not been added to a MVMapView instance.: Cause: The theme-based FOI layer had not been added to an MVMapView instance when the application invoked certain theme method.; Action: Make sure the theme method is invoked after the theme is added to an MVMapView instance.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06001: FOI width value is wrong.: Cause: MapViewer received an invalid width value for a FOI request.; Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06002: FOI height value is wrong.: Cause: MapViewer received an invalid height value for a FOI request.; Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06003: FOI ratX value is wrong.: Cause: MapViewer received an invalid ratX value for a FOI request.; Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06004: FOI ratY value is wrong.: Cause: MapViewer received an invalid ratY value for a FOI request.; Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06005: FOI bounding box value is wrong.: Cause: MapViewer received an invalid bounding box for a FOI request.; Action: This error should never happen. Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06007: Error rendering a FIG.: Cause: MapViewer encountered an error while rendering a feature of interest (FOI) object.; Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06008: Error rendering a POI.: Cause: MapViewer encountered an error while rendering a point of interest (POI) image.; Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06009: Error processing an FOI request.: Cause: MapViewer encountered an error while processing a feature of interest (FOI) request.; Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06011: Unsupported FOI request type.: Cause: MapViewer encountered an unknown type of feature of interest (FOI) request.; Action: You should never see this error. Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06013: Incorrect FIG 'gtype' number.: Cause: MapViewer encountered an invalid geometry type ('figgtype') in a FIG request.; Action: Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06014: FOI style not found.: Cause: MapViewer could not find the style specified in the FOI request.; Action: Make sure the style specified in your individual FOI or theme-based FOI layer request exists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06015: Map cache name is missing for bounding FOI theme.: Cause: MapViewer could not find the required map tile layer name in a bounding theme request.; Action: Make sure a map tile layer has been added to your map before issuing a bounding theme request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06016: JDBC theme based FOI support is disabled for the given data source.: Cause: MapViewer was configured to disable JDBC theme-based FOI on the given data source.; Action: Enable JDBC theme-based FOI support in the data source definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06017: Create tile admin task: Map tile layer not found.: Cause: MapViewer could not find the map tile layer specified in a tile admin request.; Action: Make sure the map tile layer does exist and is correctly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06018: Can not read from view USER_SDO_TILE_ADMIN_TASKS.: Cause: MapViewer could not read view USER_SDO_TILE_ADMIN_TASKS from the database connection.; Action: Make sure the SQL script mcsdefinition.sql is executed and the view USER_SDO_TILE_ADMIN_TASKS is created.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06019: Invalid SRS(spatial referencing system). This might be caused by invalid SRID or no database connection being available to retrieve SRS information: Cause: The SRID was not valid or no database connection was available to retrieve SRS information.; Action: Make sure the SRID is valid and MapViewer has a valid database connection (data source).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06020: Invalid map tile layer name. "." is not allowed in map tile layer names.: Cause: The map tile layer name specified when creating a map tile layer contained '.' (period).; Action: Remove '.' from the map tile layer name.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06021: Map tile layer name is null. Cannot create map tile layer.: Cause: The map tile layer name specified when creating a map tile layer was empty.; Action: Make sure the map tile layer name is not empty.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06022: Cannot load the map source adapter class.: Cause: MapViewer could not load the map source adapter class.; Action: Make sure the path of the adapter class jar file is valid and it does contain the adapter class.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06023: Cannot update database map tile layer configuration.: Cause: MapViewer encountered an error when updating map tile layer configuration stored in the database view USER_SDO_CACHED_MAPS.; Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06024: Either <internal_map_source> clause or <external_map_source> clause must be defined: Cause: Neither the <internal_map_source> clause nor <external_map_source> clause was defined in the XML tile layer creation request.; Action: Make sure the clauses are properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06025: Zoom levels definition is missing.: Cause: Zoom levels definition was missing in the XML tile layer creation request.; Action: Make sure the <zoom_levels> element is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06026: Coordinate system definition is missing.: Cause: The coordinate system definition was missing in the XML tile layer creation request.; Action: Make sure the <coordinate_system> element is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06027: Map source adapter class is null.: Cause: The map source adapter class was not specified when creating an external map tile layer.; Action: Make sure the map source adapter class is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06028: Property name is empty(null) and is ignored.: Cause: The 'name' attribute of the external map source adapter property was empty or null.; Action: Make sure the 'name' attribute of the property is not empty.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06029: Invalid tile image width/height definition: Cause: The tile image width and/or height were null or not valid numbers.; Action: Make sure tile image width and height are valid not null numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06030: Wrong zoom levels definition.: Cause: The zoom levels definition in the XML tile layer creation request was wrong.; Action: Make sure the zoom levels definition is valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06031: Cannot parse coordinate definition.: Cause: MapViewer could not parse the coordinate system definition in the XML tile layer creation request.; Action: Make sure the syntax of the XML coordinate system definition is valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06032: Data source cannot be null.: Cause: A data source was not specified.; Action: Make sure a data source is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06033: Base map cannot be null for a internal map source.: Cause: A base map was not specified for an internal map tile layer.; Action: Make sure a base map is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06034: Data source does not exist.: Cause: MapViewer could not find the specified data source.; Action: Make sure the data source does exist and its name is spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06035: Base map does not exist.: Cause: MapViewer could not find the specified base map.; Action: Make sure the base map source does exist and its name is spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06036: MapTileServer is not ready. Please try again later.: Cause: The map tile server was still being initialized and was not ready.; Action: Wait until the tile server is ready.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06037: You must log in as admin user in order to perform this task.: Cause: The user did not have the admin privilege when trying to perform an admin task.; Action: Log in as the admin user before submitting the admin task.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06038: Not all scale, tile_width, tile_height definition can be empty.: Cause: None of scale, tile_width, and tile_height parameters was specified for a zoom level.; Action: Make sure at least one of parameters is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06039: No map data unit conversion information is available. Cannot create mesh rules.: Cause: MapViewer could not find map data unit conversion parameters for the given coordinate system.; Action: Use tile_width instead of scale to specify zoom level definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06040: Map tile server is being shutdown!: Cause: The map tile server was being shutdown.; Action: Wait until MapViewer is restarted and the map tile server is ready.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06041: Invalid zoom level.: Cause: The zoom level was missing or invalid.; Action: Make sure the zoom level is not null and valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06042: MapViewer is not ready.: Cause: MapViewer was still being initialized and was not yet ready.; Action: Wait until MapViewer is ready.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06043: Cannot access map tile layer configuration in database.: Cause: MapViewer encountered error when trying to read the map tile layer configuration from the database.; Action: Check the MapViewer server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06044: The map tile is not correctly specified in the tile request.: Cause: The tx or ty parameter (or both) of the map tile request was not specified or was invalid.; Action: Make sure the tile tx and ty are properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06045: Cannot create directory.: Cause: MapViewer could not create the directory for tile storage.; Action: Make sure MapViewer can write to the file system and that the file system is not full.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06046: Cannot insert map tile layer configuration into database.: Cause: MapViewer could not insert the map tile layer configuration into the database view.; Action: Check the MapViewer server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06047: Cannot find map tile layer.: Cause: The specified map tile layer did not exist.; Action: Make sure the map tile layer does exist and its name is spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06048: Cannot load adapter jar file into database.: Cause: MapViewer encountered an error when writing the adapter jar file into the database.; Action: Check the MapViewer server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06049: <map_tile_server_admin_request> tag is missing from the request.: Cause: The <map_tile_server_admin_request> tag was missing in the XML tile server admin request.; Action: Make sure this tag is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06050: Map tile layer definition is missing in the request.: Cause: <map_tile_layer> tag was missing in the XML tile layer creation/redefining request.; Action: Make sure <map_tile_layer> tag is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06051: Unknow request type.: Cause: The tile admin request type was wrong.; Action: Make sure the tile admin request type is specified correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06052: Error in parsing xml request.: Cause: MapViewer encountered error when parsing the XML tile admin request.; Action: Make sure the XML request is well formatted and free of syntax errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06053: Zoom level or scale is not specified or invalid.: Cause: The tile zoom level was not specified in the tile request.; Action: Make sure the tile zoom level is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06054: Tile location definition is missing in the request. Either the tile mesh code or the tile location coordinates(tx,ty) must be specified.: Cause: The tx or ty parameter (or both) of the map tile request was not specified or was invalid.; Action: Make sure that the tile tx and ty are properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06055: Map location/size definition is missing in the request. Either the map bounding box(bbox) or the map center(cx,cy) and map size(width,height) must be specified.: Cause: Neither map bounding box nor map center and size was specified.; Action: Make sure either the map bounding box or the map center and size are specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06056: Invalid bounding box definition.: Cause: The bounding box definition was invalid.; Action: Make sure the bounding box definition is valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06057: A map tile layer with the same name already exists.: Cause: An already taken name was used to create a new map tile layer.; Action: Choose a different name for the tile layer.
Level: 1

Type: ERROR

Impact: Process