31 DVT-02012 to DVT-26021

DVT-02012: Column {0} exceeds boundary {1}.

Cause: The specified column number was greater than the total number of columns.

Action: Get the total number of columns, by calling the getColumnCount method of the graph or of the column header in the pivot table. Then specify a column that does not exceed the total number of columns.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-02013: Row {0} exceeds boundary {1}.

Cause: The specified row number was greater than the total number of rows.

Action: Get the total number of rows, by calling the getRowCount method of the graph or of the column header in the pivot table. Then specify a row that does not exceed the total number of rows.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-02015: Slice {0} exceeds boundary {1}.

Cause: The specified slice number was greater than the total number of slices.

Action: Specify a slice that does not exceed the total number of slices.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-02016: Layer {0} exceeds boundary {1}.

Cause: The specified layer was greater than the total number of layers that are available on the given edge.

Action: Specify a layer that does not exceed the total number of layers.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-02017: Series {0} exceeds boundary {1}.

Cause: The specified series was greater than the total series that is available in the graph.

Action: Specify a zero-based series index that does not exceed the total series. The Graph.getDisplaySeries method should provide the number of series that are displayed in the graph. Or, if Graph.isDataRowShownAsASeries returns true, then Graph.getRowCount returns the number of series that can be displayed. If Graph.isDataRowShownAsASeries returns false, then Graph.getColumnCount returns the total number of series that can be displayed.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-02018: Edge {0} exceeds boundary {1}.

Cause: The specified edge was greater than the total number of edges that are available on the given edge. Valid edges for methods that require an edge are: DataDirector.COLUMN_EDGE, DataDirector.ROW_EDGE, and DataDirector.PAGE_EDGE.

Action: Specify a valid edge constant.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-02019: Current DataSource does not support required type: {0}.{1}.

Cause: The DataSource did not support the required type of data in its DataMap. For example, the view requested DataMap.DATA_GROUPSORT information, and the DataSource that the view uses did not supply group sort information.

Action: Request support for the required data types in the DataSource, or use a different DataSource.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-02020: DTD file cannot be found.

Cause: The specified DTD could not be found. The XML parser needed the DTD in order to validate XML files.

Action: Ensure that the specified DTD file exists, or disable XML validation. DTDs for Data Visualization components are in their respective packages. To turn off validation, call Dataview.setXMLValidated(false);.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-03000: No Mergeable object is provided.

Cause: No default Mergeable object was provided to resolve rules.

Action: Provide at least one default Mergeable object, so that rules can be resolved. For more information about Mergeable objects, see the Javadoc for the oracle.dss.rules.Mergeable interface.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-03001: attempt to call merge(Mergeable) on an incompatible Mergeable class

Cause: An attempt was made to merge incompatible Mergeable classes. Only Mergeable objects of the same class can be merged. For example, ViewStyle objects can be merged, but a ViewStyle cannot be merged with a ViewFormat.

Action: Merge two classes that are compatible. For more information, see the Javadoc for the oracle.dss.rules.RuleBundle class.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-06000: unexpected data error from Pivot Table data model

Cause: An unexpected exception was thrown by the Pivot Table's data model.

Action: Log a bug against the application. Verify that the Pivot Table's data model is configured properly.

Level: 1

Type: ERROR

Impact: Data

DVT-06001: no Converter for data type {0} during Pivot Table text formatting

Cause: The application could not create a Converter for a specific data type. The most likely reason was that a Converter was not registered for that data type.

Action: Log a bug against the application. Verify that the application can create a default Converter for all data types rendered by the Pivot Table.

Level: 1

Type: TRACE

Impact: Configuration

DVT-07001: cannot create Graph image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-08000: unexpected data error from Data Model

Cause: An invalid operation was performed by Data Model.

Action: Log a bug against the application. Verify that the Data model is configured properly.

Level: 1

Type: ERROR

Impact: Data

DVT-09006: cannot copy event: {0}

Cause: An error occurred while trying to copy the specified event.

Action: Invoke the printStackTrace method on the exception object to display the full error stack and to identify the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09007: Measure argument must not be null in initCubeQuery.

Cause: A null measure list was passed to the initCubeQuery method.

Action: Pass in a valid list of measures to the initCubeQuery method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09008: Dimensions and measures arguments must not both be null in initQuery.

Cause: Arguments for dimensions and a measure list were both null when passed to the initQuery method.

Action: Pass in a valid value for either one or both of these arguments when calling the initQuery method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09011: Dimension is out of range in metadata cursor for edge and dimension: {0} and {1}.

Cause: The specified dimension was out of range in the method that was called for the specified edge and dimension arguments.

Action: Ensure that the dimension is valid when calling the method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09013: cannot create new instance of QueryManager or subclass when cloning

Cause: Application code could not call the constructor that takes a QueryManagerObject parameter when trying to clone an instance of QueryManager or a subclass of QueryManager.

Action: If the actual object is a subclass of QueryManager, then examine the subclass constructors for failure in the code that extends QueryManager.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09016: cannot find property

Cause: The persistent XML file was not compatible with this object.

Action: Re-create the object.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09017: cannot redo

Cause: There were no more operations on the stack to redo.

Action: No action is necessary.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09032: The specified measure {0} is invalid.

Cause: A measure name was specified that cannot be found in the database.

Action: Ensure that all named measures exist in the database.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09036: cannot undo

Cause: There were no more operations on the stack to undo.

Action: No action is necessary.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09042: MetadataManager cannot return the measure dimension.

Cause: Invalid or corrupt metadata was found in the database.

Action: Repair problems with or rebuild the database schema.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09044: illegal DataDirector type request

Cause: A relational DataDirector was requested for a nontabular query.

Action: Either call createCubeDataDirector, or set the QueryConstants.PROPERTY_TABULAR_QUERY property to true before requesting a relational data director.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09511: illegal pivot operation

Cause: Dimensions or locations were provided that would not result in a legal pivot operation.

Action: Check the given arguments and reconcile them with the layout of the current query.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09512: illegal swap operation

Cause: Dimensions or locations were provided that would not result in a legal swap operation.

Action: Check the given arguments and reconcile them with the layout of the current query.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09513: illegal swap edges operation

Cause: Edges were provided that would not result in a legal swap operation.

Action: Check the given edges and reconcile them with the layout of the current query.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09515: No query is defined.

Cause: A method was called that requires an existing query.

Action: Create a query before calling the method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-09532: The specified dimension or item is invalid: {0}.

Cause: A dimension or item name was specified that cannot be found in the current database.

Action: Ensure that all named dimensions or items are in the current database.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10000: Event is not consumable.

Cause: An attempt was made to consume an event that is not consumable.

Action: No action is necessary.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10100: Cannot connect to the database. (Reason: See error {0})

Cause: There are a variety of possible reasons why the connection was not made.

Action: Check the cause and action text for the DVT error message that is specified after "Reason:".

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10101: Handler fails to handle UserObject.

Cause: A failed attempt was made to bind or look up an object whose state could not be set or retrieved.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10105: BISession is not specified.

Cause: An instance of BISession was not set on the MetadataManager object.

Action: Set a BISession on the MetadataManager object, using the setSession method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10107: User cannot set the specified property: {0}.

Cause: An attempt was made to set a property other than Label on an MDObject.

Action: Ensure that only the Label property is set on the MDObject.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10108: MetadataManager cannot disconnect the connection.

Cause: MetadataManager could not disconnect the connection.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10109: MetadataManager cannot free the connection.

Cause: The MetadataManager could not release the connection.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10110: MetadataManager cannot retrieve the OracleConnection.

Cause: The MetadataManager could not retrieve the OracleConnection.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10300: cannot bind a context

Cause: An attempt was made to save a folder using the bind method.

Action: To create a new folder, use the createSubcontext method. To copy a folder to another folder, use the copy method. To move a folder to another folder, use the move method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10301: The specified attribute is not valid.

Cause: The key or the value of one or more attributes in the method was not valid.

Action: Specify a valid attribute key and value.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10302: Name {0} is invalid; the name must not be an empty string.

Cause: The specified name was not valid. For any methods of BIContext that require a name argument, the user cannot specify a null value. The following methods also require that the name argument not be an empty string: bind, rebind, createSubcontext, destroySubcontext, rename and unbind.

Action: Specify a name whose value is not an empty string.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10303: The specified object is invalid.

Cause: An attempt was made to save a UserObject that contains an object that is not accepted by the specific driver.

Action: Set the appropriate object in UserObject for the specified driver type.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10304: The specified search control is invalid.

Cause: The specified search control was not valid for one of the following reasons: The search scope was not valid. It must be one of the following: OBJECT_SCOPE, ONELEVEL_SCOPE, SUBTREE_SCOPE, ONELEVEL_SCOPE_WITH_FOLDERS, or SELECTIVE_ONELEVEL_SCOPE. The specified time limit was a negative number. The specified count limit was a negative number.

Action: Review the possible reasons and take the appropriate action.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10305: Object with name {0} already exists.

Cause: An attempt was made to save an object with a name that was already bound to an object in the storage system, or the destination folder already contained an object that was bound to that particular name when the copy or move operation was performed.

Action: If this is a save operation, then use the rebind method to overwrite the existing object that is bound with that name. If this is a copy operation, then specify a different target name.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10306: Object with name {0} cannot be found.

Cause: An attempt was made to retrieve, copy, or move an object that does not exist.

Action: No action is necessary.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10307: User lacks sufficient privileges to perform the operation.

Cause: An attempt was made to perform an operation that requires specific privileges, for example, saving an object to a folder in which the user does not have write access.

Action: Request that the owner or user of the folder with full-control privileges assign sufficient privileges to the appropriate user to perform the operation.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10308: The object is not a valid context.

Cause: Depending on the operation, this error could occur because: The destination folder for copy or move operations was not a valid folder. The name argument in list, listBindings, or search operations did not resolve to a folder.

Action: Specify a valid folder name.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10309: This operation is not supported.

Cause: The operation was not supported by the driver in which the operation was invoked.

Action: No action is necessary.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10310: unknown exception

Cause: An unknown error occurred.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10311: error while adding, removing, or modifying attributes

Cause: An error has occurred while performing the modifyAttributes operation.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10313: A circular reference is detected.

Cause: The operation attempted to use aggregated, copied, or moved objects that cause a circular reference.

Action: If this is a bind or rebind operation, then ensure that no circular reference exists in the aggregate tree. If this is a copy or move operation on a folder, then ensure that the parent folder is not copied or moved to the subfolder.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10315: The specified folder path is invalid.

Cause: An attempt was made to save an object in a folder path that does not exist.

Action: Specify a valid folder path.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10500: MetadataManager driver cannot be instantiated.

Cause: A failure occurred while creating an instance of the MetadataManager driver. The failure can happen only if the MetadataManager drivers are interfaces or are abstract classes.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10501: illegal attempt to access the MetadataManager driver

Cause: A failure occurred while creating an instance of the MetadataManager driver. The failure can happen only if the MetadataManager drivers are not public or are not in the MetadataManager package.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10502: MetadataManager driver is not found.

Cause: A failure occurred while creating an instance of the MetadataManager driver. The failure can happen only if the necessary jar files are not referenced in the CLASSPATH setting.

Action: Ensure that all necessary classes are included in the CLASSPATH setting.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10503: User cannot set the specified property: {0}.

Cause: An attempt was made to set a property other than Label on the MeasureDimension MDObject.

Action: Ensure that only the Label property is set on the MeasureDimension MDObject.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-10504: MetadataManager cannot retrieve the OracleConnection.

Cause: The MetadataManager could not retrieve the OracleConnection.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-12000: unexpected error

Cause: An unknown exception occurred in a call to a different class.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-16001: BISession is not specified.

Cause: An instance of BISession was not set on the Connection object.

Action: Set a BISession on the Connection object using the setSession method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-16002: Operation is incomplete because there is no database connection.

Cause: The connection was not initialized.

Action: Invoke the connect method before performing this operation.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-16003: cannot set the connection object because a connection already exists

Cause: Could not set the connection object because a connection already exists.

Action: Disconnect and set the connection object again.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-16004: The operation cannot complete because the object retrieved is a nonserializable object.

Cause: The operation was not completed because the retrieved object was not serializable.

Action: Retrieve an object only if it does not require serialization.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-16400: Connection driver cannot be instantiated.

Cause: A failure occurred while creating an instance of the Connection driver. The failure can happen only if the Connection drivers are interfaces or abstract classes.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-16401: illegal attempt to access the Connection driver

Cause: A failure occurred while creating an instance of the Connection driver. The failure can happen only if the Connection drivers are not public or are not in the Connection package.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-16402: Connection driver is not found.

Cause: A failure occurred while creating an instance of the Connection driver. The failure can happen if the necessary jar files are not referenced in the CLASSPATH setting.

Action: Ensure that all necessary classes are included in the CLASSPATH setting.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-18008: No QueryContext is defined.

Cause: A method was called that requires an existing QueryContext object.

Action: Create a QueryContext object before calling the method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-18009: No Selection is defined.

Cause: A method was called that requires an existing Selection object.

Action: Create a Selection object before calling the method.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-18010: The QueryAccess object cannot be created.

Cause: A QueryAccess object could not be created.

Action: Verify that a valid QueryContext object exists. To create a QueryAccess object, use syntax such as queryContext.createQueryAccess.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-18011: A DataAccess object cannot be created.

Cause: A DataAccess object could not be created.

Action: Verify that a valid QueryAccess object exists and that the dimension that is specified for the Selection is valid.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-18012: unexpected error

Cause: An unknown exception occurred in a call to a different class.

Action: Check the underlying error stack to find the root cause of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-22004: cannot create Gauge image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-23000: End date cannot be earlier than start date.

Cause: The end date specified for the Gantt chart was earlier than the specified start date.

Action: Specify a correct start date and end date for the Gantt chart.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-23001: The time unit in the major axis must be greater than the time unit in the minor axis.

Cause: The time unit specified in the major axis was not greater than the time unit specified in the minor axis. For example, if "days" was specified as the time unit for the minor axis, then the time unit specified in the major time axis must be greater than "days", such as "months", and not anything less, such as "hours".

Action: Ensure that the time unit in the major axis is greater than the time unit in the minor axis.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-23002: An invalid time scale is specified.

Cause: The specified time scale in the major or minor axis was not recognized.

Action: Specify a valid time scale for the axis.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-23003: End date of a task cannot be earlier than its start date. Start date: {0}, End date: {1}

Cause: The end date specified for the task was earlier than its start date.

Action: Check the data to ensure that the start date and end date are loaded correctly.

Level: 1

Type: WARNING

Impact: Data

DVT-23004: No tooltip keys or labels are specified.

Cause: No tooltip keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the tooltip to ensure that the tooltip is not empty.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23005: No legend keys or labels are specified.

Cause: No legend keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the legend to ensure that the legend is not empty.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23006: The number of tooltip keys does not match the number of tooltip labels.

Cause: The number of tooltip keys did not match the number of tooltip labels specified in the Gantt tag.

Action: Ensure that the number of tooltip keys specified in the Gantt tag (tooltipKeys attribute) matches the tooltip labels specified in the Gantt tag (tooltipLabels attribute).

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23007: The number of legend keys does not match the number of legend labels.

Cause: The number of legend keys did not match the number of legend labels specified in the Gantt tag.

Action: Ensure that the number of legend keys specified in the Gantt tag (legendKeys attribute) matches the legend labels specified in the Gantt tag (legendKeyLabels attribute).

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23008: The start date of the task is out of range. Value: {0}

Cause: The start and end date of a task was outside of the time range specified for the Gantt chart.

Action: No action necessary, if it is okay not to show the task. Otherwise, verify data is correct or specify a wider time range for the Gantt chart (using the startTime and endTime attributes)

Level: 1

Type: WARNING

Impact: Data

DVT-23009: cannot find format for type {0}; skipping task: {1}

Cause: No format for type {0} was registered.

Action: Register a TaskbarFormat with the TaskbarFormatManager for the type indicated.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23010: The specified day of the week is invalid. Value: {0}

Cause: The day of the week specified was not recognized.

Action: Specify a value for the day of the week that is one of these seven constants from the java.util.Calendar class: Calendar.SUNDAY, Calendar.MONDAY, Calendar.TUESDAY, Calendar.WEDNESDAY, Calendar.THURSDAY, Calendar.FRIDAY, Calendar.SATURDAY.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23011: The value specified for alignment is invalid. Task ID: {0}

Cause: The alignment value specified for the label or icon was invalid.

Action: Specify a value for alignment that is one of these three constants from the oracle.adf.view.faces.bi.component.gantt.GanttConstants class: GanttConstants.LEFT, GanttConstants.RIGHT, GanttConstants.INSIDE.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23012: GanttDropTarget can only be attached to a Gantt component.

Cause: The GanttDropTarget tag was added as a child of a non-Gantt component.

Action: Ensure that the GanttDropTarget tag is a child tag of either a Project Gantt or Scheduling Gantt component.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-23013: The start date of a task is null.

Cause: The start date of a task was null.

Action: Check the data to ensure that the start date is not null.

Level: 1

Type: WARNING

Impact: Data

DVT-23014: The task ID is null.

Cause: The task ID or split task ID was null.

Action: Check the data to ensure that the task ID or split task ID is not null.

Level: 1

Type: WARNING

Impact: Data

DVT-23015: The next date cannot be earlier than the previous date.

Cause: The next date returned by custom timescale was earlier than the previous date.

Action: Specify a correct next date.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26000: unable to find connection in {0}

Cause: Either the map configuration was not valid, or connection information was missing.

Action: Check the map configuration file.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26001: theme \"{0}\" cannot be displayed: missing value property

Cause: The value attribute of the theme was null.

Action: Check the value attribute of the theme.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26002: theme \"{0}\" cannot be displayed: invalid row key at row {1}

Cause: The specified row either did not have a row key, or the row id in the row key was null.

Action: Check the key and row id for the specified row.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26004: theme \"{0}\" cannot be displayed: row {1} with id={2} does not have a data value

Cause: The specified row did not have a data value.

Action: Check the data value for the specified row.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26005: theme \"{0}\" cannot be displayed: row {1} with id={2} does not have a location value

Cause: The specified row did not have a location value.

Action: Check the location value for the specified row.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26006: Labels for one or more rows of theme \"{0}\" are missing.

Cause: Some rows in the theme did not have a location label.

Action: Check the location labels in the theme.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-26008: Theme \"{0}\" does not have any data.

Cause: The specified theme did not return any rows.

Action: Check whether the specified theme is correctly returning no data.

Level: 1

Type: WARNING

Impact: Data

DVT-26009: unable to geocode data at row {0} of theme \"{1}\": {2}

Cause: The specified data could not be geocoded.

Action: Change the location value for the specified row.

Level: 1

Type: WARNING

Impact: Data

DVT-26010: The mouse click behavior of {0} is to render a popup, but there is no popup facet in the map.

Cause: The map had no popup facet, but the leftClickBehavior property was specified to render a popup.

Action: Check whether the mouse click behavior is correct.

Level: 1

Type: WARNING

Impact: Data

DVT-26011: The right-click behavior of {0} is to render a popup, but there is no popup facet in the map.

Cause: The map had no popup facet, but the rightClickBehavior property was specified to render a popup.

Action: Check whether the right-click behavior is correct.

Level: 1

Type: WARNING

Impact: Data

DVT-26012: The number of labels specified in legendLabels does not match the number of buckets. Legend labels: {0}, Buckets: {1}

Cause: The number of legend labels and buckets did not match.

Action: Check the number of legend labels.

Level: 1

Type: WARNING

Impact: Data

DVT-26013: unable to geocode the theme data: no Geocoder URL specified in {0}

Cause: Either the map configuration was not valid, or connection information for the Geocoder was missing.

Action: Check the map configuration file.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26014: unable to show all theme data for theme \"{0}\": multiple data values for {1} are specified but only the first data value is shown

Cause: Duplicate location data values were found.

Action: Check the data for duplicate location values.

Level: 1

Type: WARNING

Impact: Programmatic

DVT-26015: theme \"{0}\" cannot be displayed: no longitude data at row {1}

Cause: The specified row did not have a longitude value.

Action: Check the longitude for the specified row.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26016: theme {0} cannot be displayed: no latitude data at row {1}

Cause: The specified row did not have a latitude value.

Action: Check the latitude for the specified row.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26017: unable to connect to MapViewer at {0}

Cause: A MapViewer server was not found at the specified map URL.

Action: Check whether the connection URL is correct and the MapViewer servlet can accept new requests.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26018: unable to connect to Geocoder at {0}

Cause: The component was unable to connect to the Geocoder at the specified URL.

Action: Check whether the connection URL is correct and the Geocoder can accept new requests.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26019: unable to find a map of id {0} for mapToolbar {1}

Cause: The mapId attribute of the specified mapToolbar was not correct.

Action: Check the mapId attribute of the specified mapToolbar.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26020: A map tag cannot have more than one mapOverview tag.

Cause: There were more than one mapOverview tags in the map tag.

Action: Remove any extra mapOverview tags.

Level: 1

Type: ERROR

Impact: Programmatic

DVT-26021: A map tag cannot have more than one mapLegend tag.

Cause: There were more than one mapLegend tags in the map tag.

Action: Remove any extra mapLegend tags.

Level: 1

Type: ERROR

Impact: Programmatic