STRUVAL ERROR CODES AND MESSAGES
The following list contains all possible error types detected and reported by the STRUVAL service.
Latest update: 08/04/2024, Converter Web App Guide v1.48
| Error Code | Message Code | MessageText | Error Details |
| 500 | Null | Internal server error. Validation service not available. | The STRUVAL service is not able to process the input as the file is not in the expected format or is corrupted |
| 140 | Null | <Message from XML Parser> | The SDMX-ML file is not a well-formed XML file. It may contain such errors as invalid characters, tags that are not closed or are closed out of order. Well formedness of an XML file can be checked using different tools, such as the advanced text editors or online |
| 150 | 3 | The dataset contains a series with a missing mandatory concept {0} | The data file contains series with uncomplete key, a dimension or mandatory attribute is missing |
| 150 | 4 | The DSD {0} used does not define a time dimension, required for the time series data. | When building a time-series dataset, one must use a DSD that includes a time dimension |
| 150 | 5 | The DSD is missing a primary measure, this is required for time series data : {0} | When building a time-series dataset, one must use a DSD that has a primary measure |
| 150 | 904-1 | Series key {0} is not defined in DSD. | Dataset contains series keys which unexpected size |
| 150 | 904-2 | Series key {0} is not defined in DSD (incorrect codes). | Dataset contains series keys which unexpected size. |
| 150 | 7 | The dataset contains a concept {0} that is not defined in DSD. | All concepts used in a dataset must be defined in a DSD |
| 150 | 8 | Attribute {0} defined as mandatory in DSD is missing from the dataset. | The dataset contains a mandatory series level attribute which is not present in the data file |
| 150 | 9 | Series attribute {0} is not defined in DSD. | The encountered attribute at the series level in data file does not exist in Data Structure |
| 150 | 10 | Attribute {0} defined as mandatory in DSD is missing from the group. | The dataset contains a mandatory group level attribute which is not present in the data file |
| 150 | 11 | Attribute {0} is assigned to the incorrect group. | The encountered attribute at the dataset level in data file does not exist in Data Structure |
| 150 | 12 | Attribute {0} defined as mandatory in DSD is missing from the observation. | The dataset contains a mandatory observation level attribute which is not present in the data file |
| 150 | 13 | Attribute {0} is not defined in DSD for observation. | The encountered observation attribute is not defined by Data Structure. |
| 150 | 14 | Dataset group {0} is not defined in the DSD. | Dataset contains group keys which unexpected size |
| 150 | 15 | Dataset group {0} is not defined in the DSD. | Data Structure Definition does not define a Group with id '%s' |
| 150 | 16 | The mandatory concept {0} in DSD is currently missing from the group. | The dataset contains a group which does not have all mandatory concepts defined in the DSD |
| 150 | 17 | Concept {0} is assigned to the incorrect group. | The encountered group in the dataset contains a concept which is not defined in the DSD |
| 150 | 18 | XML error - The dataset contains an invalid node. | Appears when an unexpected node exists in the dataset file |
| 150 | 19 | Flat dataSet expected, (dimension At Observation is 'All Dimensions') but Series element encountered. Flat dataSets contain only Obs elements | A flat dataset is a dataset that consists of observations, which are not grouped in series. Each observation gives values for all dimensions ("all dimensions are under observation"). It is an error to have a series element in a flat dataset |
| 150 | 20 | Non flat dataSet expected, (dimension At Observation is not 'All Dimensions') but flat dataset encountered. Flat dataSets contain only Obs elements | A flat dataset is a dataset that consists of observations, which are not grouped in series. Each observation gives values for all dimensions ("all dimensions are under observation"). It is an error to have a series element in a flat dataset |
| 150 | 21 | XML error - Unexpected text "{0}" found at node "{1}" | Unexpected text is found as children of one sdmx node which does not contains text. Sdmx node names are kept in an internal structure and has the names like: Header, Series, Obs, Group etc. This error message appear when the dataset contains as children of these elements |
| 150 | 22 | XML error - Dataset header fails to reference a provision agreement, dataflow, or DSD. | Dataset header fails to reference a provision agreement, a dataflow, or a data structure definition |
| 150 | 23 | XML error - Dataset does not contain a header. | Dataset does not contain a header |
| 150 | 24 | XML error - Dataset structure reference incomplete. | The message appears if the referenced structure is incomplete, i.e. the agencyId, id or maintainableParentId are missing or empty |
| 150 | 25 | XML error - Invalid DSD reference. | Dataset structure reference invalid, could not process reference, no Ref node or URN node found |
| 150 | 26 | Attribute {0} is not defined in DSD. | An attribute at dataset level is present in data file but it is not defined in the DSD. |
| 150 | 27 | Expected component {0} must be an attribute, but is {1}. | Another component appears as a dataset attribute in data file. |
| 150 | 28 | Attribute {0} incorrectly attached to {2} instead of to {1}. | The dataset has an attribute with different attachment level. |
| 150 | 29 | {0} ''{1}'' is reporting value ''{2}'' which is not a valid representation in referenced codelist ''{3}''. | An attribute at dataset, series or observation level has a value which is not valid in the referenced codelist. |
| 150 | 30 | {0} {1} is reporting invalid value "{2}" which{3}. | Appears when reported value of a concept is unexpected. |
| 150 | 31 | Component {0} in group {1} not defined in DSD {2}. | The dataset contains groups which contains components that are not defined as group components in the DSD. |
| 150 | 32 | The observation does not have a value for its time dimension (i.e. the reference period is missing). | Observation missing time dimension for time series data. |
| 150 | 33 | Observations not allowed for this dataset. | Appears if there is a constraint on the dataset which does not allow observations. |
| 150 | 34 | Observation time ''{0}'' is before the expected reporting period start date "{1}". | Appears if there is a constraint which specify report start date and the observation time is before this date. |
| 150 | 35 | Observation Time ''{0}'' is after the expected reporting period end date "{1}". | Appears if there is a constraint which specify report end date and the observation time is after this date. |
| 150 | 36 | Series not allowed in this dataset. | Appears if there is a constraint on the dataset which does not allow series. |
| 150 | 37 | Series key {0} not allowed. | Appears if the dimension is not allowed in the key due to an existing constraint |
| 150 | 38 | Illegal Series key {0} contains invalid value "{1}" not defined in DSD for {2} {3}. | Appears when the series key contains some value which is disallowed by included constraints |
| 150 | 39 | Duplicate observation found | Appears when more than one observation are found in one series. |
| 150 | 40 | Data validation failed : {0} | It appears when a custom validation rule does not pass. |
| Data validation failed : Failure("checkDataSetAttributeValue") | |||
| 150 | 41 | Cross-sectional component {0} is incorrectly attached to {2} instead of to {1}. | The cross-sectional component is attached to a wrong level. |
| 150 | 42 | Invalid date format "{0}". | Appears if the TIME_PERIOD attribute does not match the TIME_FORMAT. |
| 150 | 43 | Structure type wrongly references {1} instead of {0}. | If the dataset header contains a URN reference to other artefact then expected. |
| 100 | 44 | The dataset references dataflow “{0}” which could not be resolved. | The structure file supplied to the STRUVAL service call does not contain a dataflow (identified by agency, name, and version) that is referenced from the dataset. |
| 100 | 45 | The dataset references DSD “{0}” which could not be resolved. | The structure file supplied to the STRUVAL service call does not contain a DSD (identified by agency, name, and version) that is referenced from the dataset. |
| 501 | 46 | Component attribute {0} with parent {1} not supported. | When an XML attribute is in the wrong element. |
| 501 | 47 | Cannot read dataset for structure of type: '{0}' | If the dataset has a structure reference which is neither DSD or Dataflow |
| 501 | 48 | The DSD {0} is missing a time dimension. | DSDs that STRUVAL can process must contain a time dimension. |
| 501 | 49 | Cannot validate the header of format {0}. | Appears when the struval tries to validate a header but the given dataset file is not detected as been one of the following formats: COMPACT_2_0, GENERIC_2_0, CROSS_SECTIONAL_2_0, UTILITY_2_0, GENERIC_2_1, GENERIC_2_1_XS, COMPACT_2_1 or COMPACT_2_1_XS |
| 150 | 50 | Property not found {0} | Appears when the validation fails, because of missing input or structure file |
| 140 | 51 | Configuration Error {0} | Appears when Excel Data Reader was not configured correctly |
| 140 | 52 | Data reader error. {0}. | Appears when Reading the input file was not possible |
| 140 | 53 | Data reader | The Dataset requires an embedded or external Parameters sheet to process the data. |
| 150 | 54 | Error While Processing XML : {0} | Appears when XML structure validation fails |
| 150 | 55 | Structure Fails Validation: {0} | Appears when parameters validation fails |
| 150 | 56 | I/O exception: {0} | Appears when a file either does not exist or could not be recognised. |
| 150 | 57 | Unsupported {0} | Indicates that the requested operation is not supported. |
| 150 | 58 | Referenced structure could not be resolved {0} | Structure not found. |
| 150 | 59 | null | General request error check your request files and parameters. |
| 150 | 60 | The dataset contains a header row with a missing mandatory {0}: {1}. | The input file is an empty Csv file and a dimension or mandatory attribute is missing from the header row. |
| 150 | 61 | Data reader error | Appears when Reading the input file was not possible. {0}. |
| 150 | 62 | {0} {1} value contains invalid character. | Appears when an invalid character was detected in a component value. |
| 150 | 63 | {0} ''{1}'' is reporting invalid value which{2} | Appears when reported value of a concept is unexpected |
| 150 | 64 | Illegal Series key {0} contains an invalid value not defined in DSD for {1} ''{2}'' | Appears when the series key contains some value which is disallowed by included constraints |
| 150 | 65 | Duplicate columns/concepts found in Header Row: {0} | Appears when the header row in a CSV file contains duplicate concepts/columns |
| 150 | 66 | Attribute {0} has less instances than minimum occurrences defined by Data Structure. | Appears when the attribute has less occurrences than from what it is defined by DSD or Dataflow |
| 150 | 67 | Attribute {0} has more instances than maximum occurrences defined by Data Structure. | Appears when the attribute has less occurrences than from what it is defined by DSD or Dataflow |