Skip to end of metadata
Go to start of metadata


The following list contains all possible error types detected and reported by the STRUVAL service.


Error Code

Message ID

Message Text

Error Details

500

 

Internal server error. Validation service not available.

The STRUVAL service is not able to process the inputs due to an internal server error.

140

 

<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 concept {0}

The data file contains series having dimensions or attributes which are not defined in DSD.

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 dataset includes primary measure {0}, not expected by the DSD.

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 (unexpected size).

Dataset contains series keys with unexpected size. 

150

904-2

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

Dataset contains series keys which unexpected size. 

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.

150

018

XML error - The dataset contains an invalid node.

Appears when an unexpected node exists in the dataset file.

150

019

Error never occurs

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

Error never occurs

Non flat dataset expected, (dimension At Observation is not 'All Dimensions') but flat dataset encountered. Flat datasets contain only observation elements

150

021

XML error - Unexpected text ''{0}'' found at node ''{1}''

Unexpected text is found as children of one SDMX node which does not contain text. SDMX node names are kept in an internal structure and has the names like: Header, Series, Obs, Group etc. This error message appears 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 appear if the referenced structure is incomplete, ie the agencyId, id or maintainable ParentId are missing or empty.

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.

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.

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 code list.

150

030

{0} {1} is reporting invalid value {3} which is not of expected type {2}.

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.

150

032

Observation missing time dimension for time series data.

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 constraints in DSD.

150

039

Duplicate observation found: {0}

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")

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.

150

043

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

If the dataset header contains a URN reference to other artifact 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

501

048

The DSD {0} is missing a time dimension.

DSDs that STRUVAL can process must contain a time dimension.

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

Excel data reader error {0}

Appears when Reading the excel file was not possible

140

053

Invalid Parameters detected {0}

Appears when misconfiguration exists inside Parameter Sheet or Mapping Sheet

150

054

Error While Processing XML : {0}

Appears when XML structure validation fails

  • No labels