Error Code

Message Code

MessageText

Error Details

Comments

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

003

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

004

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

005

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

Replaced by other validations (like missing concept 031 or some other code depending on the specific case because the size of the series keys may be higher or lower than expected size)

150

904-2

Series key {0} is not defined in DSD (incorrect codes).

Dataset contains series keys which unexpected size. 

Replaced by 029 and the error is found when the code of the concept is incorrect.

150

007

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

008

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

009

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

010

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

011

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

012

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

013

Attribute {0} is not defined in DSD for observation.

The encountered observation attribute is not defined by Data Structure.

150

014

Dataset group {0} is not defined in the DSD.

Dataset contains group keys which unexpected size

150

015

Dataset group {0} is not defined in the DSD.

Data Structure Definition does not define a Group with id '%s'

150

016

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

017

Concept {0} is assigned to the incorrect group.

The encountered group in the dataset contains a concept which is not defined in the DSD

Replaced by 011 and “Xml unexpected attribute”[1]

150

018

XML error - The dataset contains an invalid node.

Appears when an unexpected node exists in the dataset file

150

019

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

020

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

021

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

022

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

023

XML error - Dataset does not contain a header.

Dataset does not contain a header

150

024

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

Replaced by 022 validation (which was not implemented from the beginning)

150

025

XML error - Invalid DSD reference.

Dataset structure reference invalid, could not process reference, no Ref node or URN node found

150

026

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.

Replaced by 009 and 011 (depending on the case) and “Xml undefined attribute” [2]

150

027

Expected component {0} must be an attribute, but is {1}.

Another component appears as a dataset attribute in data file.

150

028

Attribute {0} incorrectly attached to {2} instead of to {1}.

The dataset has an attribute with different attachment level.

Replaced by the errors 009 or 011.

150

029

{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

030

{0} {1} is reporting invalid value "{2}" which{3}.

Appears when reported value of a concept is unexpected.

150

031

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.

Replaced by 011 and “Xml unexpected attribute”[3]

150

032

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

033

Observations not allowed for this dataset.

Appears if there is a constraint on the dataset which does not allow observations.

150

034

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

035

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

036

Series not allowed in this dataset.

Appears if there is a constraint on the dataset which does not allow series.

150

037

Series key {0} not allowed.

Appears if the dimension is not allowed in the key due to an existing constraint

150

038

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

039

Duplicate observation found

Appears when more than one observation are found in one series.

150

040

Data validation failed : {0}

It appears when a custom validation rule does not pass.

Data validation failed : Failure("checkDataSetAttributeValue")

Error never occurs

150

041

Cross-sectional component {0} is incorrectly attached to {2} instead of to {1}.

The cross-sectional component is attached to a wrong level.

150

042

Invalid date format "{0}".

Appears if the TIME_PERIOD attribute does not match the TIME_FORMAT.

Validation left for a future release. (see SDMXCONV-310).

150

043

Structure type wrongly references {1} instead of {0}.

If the dataset header contains a URN reference to other artefact then expected.

100

044

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

045

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

046

Component attribute {0} with parent {1} not supported.

When an  XML attribute is in the wrong element.

501

047

Cannot read dataset for structure of type: '{0}'

If the dataset has a structure reference which is neither DSD or Dataflow

The message is not testable in Converter applications because we don't support structures other than DSD and Dataflows.  This error message appears only if struval is used as API.

501

048

The DSD {0} is missing a time dimension.

DSDs that STRUVAL can process must contain a time dimension.

The error message 501 - 048 - "The DSD {0} is missing a time dimension" is in conflict with 150 - 004 - "The DSD {0} used does not define a time dimension, required for the time series data". They both refer to the same thing, the first was created by Intrasoft ( hence the 4 digits message code) in order to cover some bugs in SdmxSource ( see SDMXSOURCE-10) whereas the 004 is thrown by Sdmx Source (so it's standard). Starting with Converter 6.9.1 the first one (9946) is no longer used.

501

049

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

050

Property not found {0}

Appears when the validation  fails, because of missing input or structure file

140

051

Configuration Error {0}

Appears when Excel Data Reader was not configured correctly

140

052

Data reader error. {0}.

Appears when Reading the input file was not possible

140

053

Data reader

The Dataset requires an embedded or external Parameters sheet to process the data.

150

054

Error While Processing XML : {0}

Appears when XML structure validation fails

150

055

Structure Fails Validation: {0}

Appears when parameters validation fails

150

056

I/O exception: {0}

Appears when a file either does not exist or could not be recognised.

      150

057

Unsupported {0}

Indicates that the requested operation is not supported.

150

058

Referenced structure could not be resolved {0}

Structure not found.

150

059

null

General request error check your request files and parameters.

150

060

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

061

Data reader error

Appears when Reading the input file was not possible. {0}.

150

062

{0} {1} value contains invalid character.

Appears when an invalid character was detected in a component value.

150

063

{0} ''{1}'' is reporting invalid value which{2}

Appears when reported value of a concept is unexpected

150

064

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

065

Duplicate columns/concepts found in Header Row: {0}

Appears when the header row in a CSV file contains duplicate concepts/columns