TOP

Runtime Error Reference

D0001S

Message Format

D0001S: Output buffer too small; total buffer size:

or

D0001S: Output buffer too small; total bytes requested:

Message Cause

A pre-allocated output buffer was provided (e.g., using the ASN.1/C ossDecode() function's fourth parameter), but the memory block passed was too small to contain the entire decoded PDU. Any of these scenarios can cause this problem:

  • The size of off-shoot structures referenced by pointers in the main PDU structure is not taken into account. When your PDU contains pointered fields, a sizeof() operation on the main structure is not enough to determine its decoded size. Be sure to consider the memory needed to store the secondary data pointed to by the main structure's fields, as well.
  • Enough memory is pre-allocated for the decoder output, but ossSetDecodingLength() is not called before calling ossDecode(). The call to ossSetDecodingLength() tells the decoder the size of the pre-allocated output buffer.
  • You meant to have the decoder automatically allocate memory, but forgot to set the address pointed to by ossDecode()'s fourth argument to NULL. Set the address to NULL so ossDecode() allocates the necessary output memory.

Possible Solution

Increase the size of the pre-allocated output buffer passed to ossDecode()'s fourth argument or pass a NULL pointer to instruct the decoder to automatically allocate the needed space.


E0001S

Message Format

E0001S: Output buffer too small; total buffer size:

or

E0001S: Output buffer too small; total bytes requested:

Message Cause

A pre-allocated output buffer was provided (e.g., using the ASN.1/C ossEncode() function's fourth parameter), but the memory block passed was too small to contain the entire decoded PDU.

This error message is often issued because the size of off-shoot structures referenced by pointers in the main PDU structure is not taken into account.

Possible Solution

Use the ossDetermineEncodingLength() function to determine how much space a PDU will require and allocate memory accordingly. Alternatively, pass a NULL pointer to ossEncode()'s fourth argument to instruct the encoder to automatically allocate the needed space.


D0002S

Message Format

D0002S: Data type has not been implemented yet

Message Cause

The decoder is using PER, XER, E-XER, or OER, but a data type was found with a representation that is currently not supported by the PER, XER, E-XER, or OER Space-Optimized Decoder. This error occurs when these type representations are encountered:

  • NULLTERM DLINKED character string
  • NULLTERM LINKED character string
  • UNBOUNDED DLINK ANY
  • UNBOUNDED LINKED ANY
  • UNBOUNDED DLINKED BIT STRING
  • UNBOUNDED LINKED BIT STRING
  • UNBOUNDED DLINKED character string
  • UNBOUNDED LINKED character string
  • UNBOUNDED DLINKED OCTET STRING
  • UNBOUNDED LINKED OCTET STRING
  • VARYING DLINKED BIT STRING
  • VARYING LINKED BIT STRING
  • VARYING DLINKED character string
  • VARYING LINKED character string
  • VARYING DLINKED OCTET STRING
  • VARYING LINKED OCTET STRING

Possible Solution

Remove the OSS.LINKED or OSS.DLINKED directive from the problematic type in your input ASN.1 specification. Then ASN.1-compile your specification and re-link the generated files with your application.


E0002S

Message Format

E0002S: Data type has not been implemented yet

Message Cause

The encoder encountered an unrecognizable data type. This can happen when a newer version of the OSS ASN.1 compiler is used with an older version of the OSS ASN.1 runtime libraries.

Possible Solution

Use the osswhat utility, included with the OSS ASN.1 Tools, to make certain that your runtime library version matches your ASN.1 compiler version. Consider upgrading to a newer version of the runtime if you find that it is older than your version of the compiler.


D0003S | E0003S

Message Format

x0003S: PDU number not in range:

Message Cause

The encoder/decoder was passed a PDU identification number that is greater than the highest PDU number assigned by the ASN.1 compiler.

Possible solutions

  • In the ASN.1 compiler-generated header file, locate the value of the #define typename_PDU constant that matches the type you want to encode or decode. Declare a short or int type variable and assign this value to it. If encoding, pass this variable as the second argument to the encoder; if decoding, pass the address of the variable as the second argument to the decoder. This ensures that an out-of-range PDU number will not be passed.
  • To automatically encode or decode open types, be sure to set the AUTOMATIC_ENCDEC flag before calling the encoder or decoder.
  • Similar errors can result when a specification is ASN.1-compiled with the wrong asn1dflt file. When your ASN.1 compiler runs on a platform different from your target (runtime) platform, use the ASN.1 compiler with the correct asn1dflt file to generate output compatible with your target platform. Specify the asn1dflt file on the command-line before any other input files. Also, on Windows and similar platforms, be sure to use the asn1dflt file that matches the data packing and alignment option (e.g., /zp4, /a8) used to C or C++ compile.

D0004S | E0004S

Message Format

x0004S: Version number of control table differs from that of encoder/decoder

Message Cause

The encoder/decoder library file is incompatible with the ASN.1 compiler in use. The two components are of different versions.

Possible Solution

Use the osswhat utility, included with the OSS ASN.1 Tools, to make certain that your runtime library version matches your ASN.1 compiler version. If you find that you have an older version of the runtime or compiler, consider upgrading to a newer version.


D0005S | E0005S

Message Format

x0005S: Global data access serialization error

Message Cause

The encoder/decoder experienced a serialization error when modifying the OssGlobal structure or another global variable.

Possible Solution

When using multiple simultaneous threads in your application, allocate and initialize a separate OssGlobal structure for each thread.


D0006S | E0006S

Message Format

x0006S: Unexpected NULL pointer as argument to encoder/decoder

Message Cause

The encoder/decoder's third argument is NULL, when it should contain the input address.

Possible Solutions

  • Pass the address of the PDU to be encoded as the third encoder argument. Likewise, pass the address of the OssBuf data structure that contains the input encoded data as the third decoder argument.
  • An error can also occur if a mandatory C-compiler command-line option is omitted when a generated control table or code file is compiled. Mandatory options are those that OSS Nokalva was asked (explicitly or implicitly) to use when compiling its encoder/decoder library files.

D0007S | E0007S

Message Format

x0007S: The files generated by the ASN.1 compiler are incompatible with the runtime library version.

Message Cause

This error can occur in any of these situations:

  • Files generated by a trial license compiler are linked with a non-trial runtime library, or vice versa.
  • Output from a version 8.* or later compiler is being used with a pre-8.0 runtime, or vice versa. Except for this combination, compiler versions and runtime versions can usually be mixed.
  • The generated files were created by cross-compiling to the target platform, but the wrong asn1dflt file was used with the compiler.

Possible Solution

Use the osswhat utility, included with the OSS ASN.1 Tools, to make certain that your runtime library version matches your ASN.1 compiler version. If you find that you have an older version of the runtime or compiler, consider upgrading to a newer version.


D0008S | E0008S

Message Format

x0008S: Out of memory; bytes requested:

Message Cause

The encoder/decoder received an out of memory signal from the operating system when trying to allocate the amount of bytes specified for the output.

Possible Solution

Free up some system resources before using the encoder/decoder. Try the following suggestions:

  • Turn off runtime tracing, that is, do not specify the DEBUGPDU flag.
  • Turn off constraint checking by specifying the NOCONSTRAIN flag.

E0009S

Message Format

E0009S: Out-of-range CHOICE selector:

Message Cause

In a PDU generated to represent a CHOICE, the encoder found that the value of the choice field exceeded the maximum allowed selector value.

Possible Solutions

  • Use the generated #define alternative_chosen constants to assign values to the choice field. This ensures that an out-of-range value will not be assigned. Also, be sure to pass the correct PDU number to the encoder. Use the #define typename_PDU constant for the type you want to encode.
  • Similar errors can result when a specification is ASN.1-compiled with the wrong asn1dflt file. When your ASN.1 compiler runs on a platform different from your target (runtime) platform, use the ASN.1 compiler with the correct asn1dflt file to generate output compatible with your target platform. Specify the asn1dflt file on the command-line before any other input files. Also, on Windows and similar platforms, be sure to use the asn1dflt file that matches the data packing and alignment option (e.g., /zp4, /a8) used to C or C++ compile.

D0009S

Message Format

D0009S: Out-of-range CHOICE selector:

Message Cause

While decoding a PER-encoded message, the decoder found that the choice selector of a PDU generated to represent a CHOICE exceeded the maximum allowed.

Possible Solution

Confirm that the encoding and decoding applications use the same ASN.1 notation.


D0010S | E0010S

Message Format

x0010S: Bad OBJECT IDENTIFIER: problematic sub-identifier number

Message Cause

The encoder/decoder found an OBJECT IDENTIFIER value that violates the ASN.1 standard. Any of the following input conditions could cause this error:

  • An OBJECT IDENTIFIER value is completely empty.
  • An OBJECT IDENTIFIER value has only one node.
  • The value of the first node in an OBJECT IDENTIFIER value is not 0, 1, or 2.
  • The first two nodes of the OBJECT IDENTIFIER value have a sum of forty or greater.
  • The first two nodes of the OBJECT IDENTIFIER value are zero and the third node is outside the range of 1 through 26.

Possible Solution

Modify the OBJECT IDENTIFIER value so that it meets the requirements set by the ASN.1 standard.

NOTE: If values that violate the ASN.1 standard must be encoded, specify the -allowBadValues ASN.1 compiler option or use the RELATIVE-OID ASN.1 type instead of OBJECT IDENTIFIER.


E0011S

Message Format

E0011S: Unexpected NULL pointer in input

Message Cause

The encoder found a NULL pointered field in a PDU when the address of a value was expected.

Possible Solutions

Change the pointered field to hold the address of a valid value for the appropriate ASN.1 type.

This error can also occur when

  • The application executable cannot access the memory manager DLL. Make sure that all necessary DLLs are in the executable search path of your operating system.
  • ossLoadMemoryManager() is used to load the file memory manager at runtime, but the OSS libraries are linked statically instead of dynamically.

D0012S | E0012S

Message Format

x0012S: Out-of-range value in time type

Issued By

All encoders and decoders.

Message Cause

The encoder/decoder encountered a time value in which one or more components have values outside the allowed range. The valid value ranges for time components are

  • Month: 1..12
  • Day: 1..31
  • Hour: 0..23
  • Minute: 0..59
  • Second: 0..59
  • Millisec: 0..999 for GeneralizedTime or 0 for UTCTime.

Possible Solution

Change the component value to fall within the range set by the ASN.1 standard.


D0013S | E0013S

Message Format

x0013S: Time value must be in universal coordinated time format and must end with 'Z'

Message Cause

When DER was in use, the encoder/decoder encountered a time value that was not in UTC (Universal Time Coordinated) format. All time values in DER must be in this format per the ASN.1 standard.

Possible Solution

Change the format of the violating time value to conform with the restrictions on DER-encoded time values in the ASN.1 standard.


D0014S | E0014S

Message Format

x0014S: A memory-violation error occurred, signal number

Message Cause

The encoder/decoder received an error signal from the memory manager when trying to store some piece of data.

Possible Solutions

  • Check your user-defined memory manager for errors. Alternatively, make sure that the process running your application has enough memory to accomplish all necessary tasks.
  • If the OSS API functions are called from multiple simultaneous threads, make certain that no two functions have access to the same OssGlobal structure at the same time. Do this by either serializing access to the OssGlobal structure or initializing a separate copy of OssGlobal for each thread. If the latter is chosen, call ossinit() and ossterm() from within the same thread. NOTE: If you use the OSS ASN.1 Tools for Java or C++, instantiate a new Coder environment for each thread in use.
  • If multiple simultaneous threads are used when linking with the static OSS libraries (e.g., soeddefa.lib) on Windows, call ossInitSync() before using the OSS API functions and ossTermSync() after using them to achieve thread-safety.

D0015E

Message Format

D0015E: Object identifier has too many subidentifiers:

Message Cause

The decoder encountered an OBJECT IDENTIFIER value with more than forty sub-identifiers, which is the maximum allowed.

Possible Solution

Reduce the number of sub-identifiers in the OBJECT IDENTIFIER value.


D0016S | E0016S

Message Format

x0016S: Size constraint exceeded, length of value = length

Message Cause

The BER/XER/E-XER/OER encoder/decoder or the constraint checker encountered inconsistent values in the input data.

Example

typedef struct {
    int length;
    char value[40];
} boundedString;

When BER is used, the value of the length field in this fixed-size array must be between 0 and 40. This error will be issued if a length greater than 40 is passed to the encoder.

Possible Solutions

  • Remove the inconsistency in the data input to the encoder.
  • Similar errors can result when a specification is ASN.1-compiled with the wrong asn1dflt file. When your ASN.1 compiler runs on a platform different from your target (runtime) platform, use the ASN.1 compiler with the correct asn1dflt file to generate output compatible with your target platform. Specify the asn1dflt file on the command-line before any other input files. Also, on Windows and similar platforms, be sure to use the asn1dflt file that matches the data packing and alignment option (e.g., /zp4, /a8) used to C or C++ compile.

D0017E | E0017E

Message Format

x0017E: Encoded object identifier value too long for local representation:

Message Cause

The encoder/decoder encountered an OBJECT IDENTIFIER value that is too large to fit in the local representation.

Possible Solution

Use the OSS.ENCODED compiler directive to create a representation of the OBJECT IDENTIFIER type that can accommodate the large value.


D0018E

Message Format

D0018E: Tag needlessly long

Message Cause

The BER/DER decoder found a needlessly long tag encoding.

Possible Solution

Specify the OSS_RELAXED encoder/decoder runtime flag to allow such long tags.


D0019E

Message Format

D0019E: Tag too long: tag

Message Cause

The BER/DER decoder found a tag encoding that occupies more than 14 encoded bits.

Possible Solution

Reduce the value of the tag to be less than 16,383.


D0020E

Message Format

D0020E: Exponent needlessly long

Message Cause

The decoder found an exponent for a REAL type that has nine leading 1's or 0's.

Possible Solution

Correct the faulty encoding or specify the OSS_RELAXED encoder/decoder runtime flag to allow such exponents.


D0021E

Message Format

D0021E: Exponent too long: exponent

Message Cause

The decoder found an exponent for a REAL type that is too large to fit in a platform-dependent representation of REAL types.

Possible Solution

Use the OSS.DECIMAL compiler directive to choose a REAL type representation that can accommodate the limitations of your particular platform.


D0022E

Message Format

D0022E: Integer or enumerated value needlessly long

Message Cause

The decoder was passed an encoding that violates one or more clauses of X.690, which mandates that INTEGER type values be encoded in the fewest number of bytes possible.

Possible Solutions

  • Check that the encoding rules in use match how the input data was encoded. Use the ossGetEncodingRules() and ossSetEncodingRules() functions for this purpose. NOTE: If you use the OSS ASN.1 Tools for Java or C++, call the appropriate Coder to determine the correct encoding rules to use.
  • Try to work around the invalid encodings using the ossSetFlags() or ossSetDecodingFlags() function and specify the OSS_RELAXED flag. This could cause the decoder to silently accept the invalid encodings.

D0023E

Message Format

D0023E: Integer or enumerated value too long: value

Message Cause

An integer was decoded and is either too large (byte-wise) to fit into a signed or unsigned long int or its size exceeds the bounds set in your C-compiler limits.h file.

Possible Solution

Use the ASN1.HugeInteger or OSS.HUGE compiler directive to create a platform-independent representation of the problematic integer type that allows much larger values.


D0024E

Message Format

D0024E: Sub-identifier needlessly long

Message Cause

While decoding an OBJECT IDENTIFIER value, the decoder found a sub-identifier with seven leading 0-bits, which violates the ASN.1 standard.

Possible Solution

To work around the invalid encodings, use the ossSetFlags() or ossSetDecodingFlags() function and specify the OSS_RELAXED flag. The decoder will then silently accept the invalid encodings.


D0025E

Message Format

D0025E: Sub-identifier too long: value

Message Cause

While decoding an OBJECT IDENTIFIER value, the decoder found a sub-identifier that is either too large (byte-wise) to fit into a signed or unsigned long int or its size exceeds the bounds set for a data type in your C-compiler limits.h file.

Possible Solution

Use the OSS.OBJECTID or OSS.ENCODED compiler directive to create an OBJECT IDENTIFIER type representation that can handle larger sub-identifier values.


D0026S | E0026S

Message Format

x0026S: Length too long: length

Message Cause

The encoder or decoder found that the length field of a data type was too long to fit in an unsigned long int.

Possible Solutions

  • Make sure the length is specified correctly.
  • With PER, this error usually occurs when the encoded data is corrupt.

D0027S

Message Format

D0027S: Size too long: size

Message Cause

While decoding, the decoder found a size field that exceeds the bounds set for a data type in your C-compiler limits.h file.

Possible Solution

Change the representation of the size field.


D0028E

Message Format

D0028E: Non-standard EOC octets

Message Cause

While decoding, the decoder found an encoding with a tag of 0. Using an empty octet signals the end of content, so a zero value in a tag location is inappropriate.

Possible Solution

Check the encoding application for errors.


D0029E | E0029E

Message Format

x0029E: Too many OPTIONAL fields:.

Message Cause

The encoder/decoder found a SEQUENCE or a SET data type that had more non-mandatory fields than is currently allowed. This error occurs when the number of optional fields in a structure requires a preamble of more than 800 bits in its PER encoding.

Possible Solutions

  • Reduce the number of optional fields.
  • The decoder could issue this error when handed a corrupt PER encoding.

D0030S | E0030S

Message Format

x0030S: Unknown size

Message Cause

The encoder/decoder found a data item in the generated .c file whose size exceeds what the runtime version in use supports.

Possible Solution

Use the osswhat utility, included with the OSS ASN.1 Tools, to make certain that your runtime library version matches your ASN.1 compiler version. Consider upgrading to a newer version of the runtime if you find that it is older than your version of the compiler.


D0031S

Message Format

D0031S: Inconsistent lengths

Message Cause

The decoder found a definite-length encoding of an explicitly-tagged type that has inconsistent lengths. That is, the inner length does not equal the stated outer length minus the inner tag and length lengths.

Possible Solution

Check the encoding application for errors.


D0032E

Message Format

D0032E: Too many extension additions:

Message Cause

The encoder/decoder found a SEQUENCE or a SET data type that has more extension-addition fields than are currently allowed. This error occurs when the number of extension-addition fields in a structure requires a preamble of more than 800 bits in its PER encoding.

Possible Solution

Reduce the number of extension additions.


D0033E

Message Format

D0033E: Tag mismatch or tag not expected: [foundTag] (expected tag [tag]); check field 'fieldName' (type: typeName) of PDU #n 'e'.

Message Cause

This error has three common causes:

  • The decoder found an unexpected tag for a component within a SEQUENCE, SET, SEQUENCE OF, SET OF, CHOICE, or selection type.
  • The decoder found a tag mismatch between outer and inner tags of an explicitly-tagged encoding.
  • The decoder found a large OCTET STRING or BIT STRING value broken into multiple pieces; one of the pieces does not have the correct tag for the OCTET STRING or BIT STRING type.

Possible Solution

Check the encoding application for errors.


D0034E

Message Format

D0034E: PDU number and input tags do not match:

Message Cause

The decoder found that the tags in the input encoding do not match the expected tags of the PDU to be decoded.

Possible Solution

Check that the PDU number passed to the decoder conforms to the data structure to be decoded.


D0035E

Message Format

D0035E: The first octet is not in the range 0-7

Message Cause

The decoder found a BER/OER encoded BIT STRING type whose trailing bits do not end on an octet boundary.

Possible Solution

Check the encoding application for errors.


D0036E | E0036E

Message Format

x0036E: The first octet is not 0

Message Cause

The encoder/decoder found trailing bits from the last encoding that are improperly aligned on an octet boundary.

Possible Solution

Check the encoding application for errors.


D0037E | E0037E

Message Format

x0037E: Value misencoded or length wrong for value

Message Cause

The encoder/decoder found one of the following abnormalities:

  • A mis-encoded time value.
  • A decimal REAL value that ends too soon.
  • A NULL value that is not empty.
  • A BOOLEAN value with a length other than 1.
  • An empty INTEGER value.
  • An encoded OBJECT IDENTIFIER value whose length is not the sum of its sub-lengths.
  • An encoding whose last byte has the eighth bit set.
  • An extension addition encoding that has a different (shorter) length than what was expected.
  • With PER in use, the decoder found a loosely- or un-constrained INTEGER value encoding that has unnecessary zero octets at its end.

Possible Solutions

  • Check the encoding application for errors.
  • Try specifying the OSS_RELAXED flag with the ossSetFlags() function.
  • When this error occurs for an OBJECT IDENTIFIER, the cause could be that the specified node values do not fit in a short integer, which is the default representation for OID nodes. To encode/decode long node values, specify the OSS.OBJECTID directive at the beginning of the .asn file where the problematic OBJECT IDENTIFIER type is located.

D0038E

Message Format

D0038E: Expected digits in mantissa

Message Cause

The decoder found an encoding of a REAL type that lacks a mantissa value.

Possible Solution

Check the encoding application for errors.


D0039E

Message Format

D0039E: Expected digits in exponent

Message Cause

The decoder found an encoding of a REAL type that lacks an exponent value.

Possible Solution

Check the encoding application for errors.


D0040E

Message Format

D0040E: Invalid NR1 (real) encoding

Message Cause

The decoder found an encoding of a REAL type that violates the ISO 6093 NR1 format.

Possible Solution

Check the encoding application for errors.


D0041E

Message Format

D0041E: Invalid NR2 (real) encoding

Message Cause

The decoder found an encoding of a REAL type that violates the ISO 6093 NR2 format.

Possible Solution

Check the encoding application for errors.


D0042E

Message Format

D0042E: Invalid NR3 (real) encoding

Message Cause

The decoder found an encoding of a REAL type that violates the ISO 6093 NR3 format.

Possible Solution

Check the encoding application for errors.


D0043E

Message Format

D0043E: REAL 0 with contents found

Message Cause

The decoder found an encoding of a REAL type with an empty octet, instead of a zero value with no contents-encoding per the ASN.1 standard.

Possible Solution

Check the encoding application for errors.


D0044E

Message Format

D0044E: Reserved real encoding

Message Cause

The decoder found an encoding of a REAL type that uses a reserved encoding format. See "Encoding of a real value" in ITU-T Recommendation X.690 (2015) for more details.

Possible Solution

Change the encoding application to use an encoding format that is not reserved by the ASN.1 standard.


D0045E

Message Format

D0045E: Too many values in input; skipped

Message Cause

The decoder found that the contents encoding of a character string, OBJECT IDENTIFIER, inextensible SET OF, or inextensible SEQUENCE OF is longer than the maximum allowed in the local data structure. The extra values were skipped.

Possible Solution

Check the encoding application for errors.


D0046E

Message Format

D0046E: Found NULL embedded in null-terminated STRING

Message Cause

The decoder found that the contents encoding of a null-terminated character string has a NULL character at some place other than the terminating position. The decoder transforms such embedded NULL characters into white spaces.

Possible Solution

Try using the UNBOUNDED representation; it allows any size string without needing a NULL to terminate it.

Example

typedef struct AsciiString {
     unsigned int    length;
     char            *value;
} AsciiString;

In this C representation, a null-terminator can occur within the value because the string length is stored in the length field of the structure. Try applying the OSS.UNBOUNDED compiler directive to the problematic type.


D0047E

Message Format

D0047E: Tag not recognized: [foundTag]; check field 'fieldName' (type: typeName) of PDU #n 'pduname'.

Message Cause

The decoder found a tag in an encoding for a non-extensible SET, SEQUENCE, or CHOICE type that does not correspond to any component or alternative listed in the ASN.1 specification.

Possible Solutions

  • Check the encoding application for errors.
  • When an explicit tag (e.g., [APPLICATION 120]) is applied to a type, make sure that it is the same one used by the encoding party for that type.
  • Be sure to pass the correct PDU number (as the second argument to the decoder) that matches the type to be decoded.

D0048E

Message Format

D0048E: Field repeated

Message Cause

The decoder found an encoding of a SET type that contains two or more values for the same type.

Possible Solution

Check the encoding application for errors.


D0049E

Message Format

D0049E: Field omitted

Message Cause

The decoder could not find a mandatory SET or SEQUENCE component in its encoding.

Possible Solution

Check the encoding application for errors.


D0050S

Message Format

D0050S: Expected EOC octets

Message Cause

The decoder found too few end-of-contents octets at the end of a SET OF or SEQUENCE OF type.

Possible Solution

Check the encoding application for errors.


D0051S

Message Format

Found primitive encoding with indefinite length

Message Cause

The decoder found a primitive encoding of an ASN.1 type that is specified using the indefinite length form. However, according to the ASN.1 standard, the indefinite length form is valid only for constructed encodings.

Similar errors can occur when the data in the encoded buffer is not aligned correctly. For example, if the address of OssBuf.value does not match the beginning of a new encoding, the decoder could misinterpret the encoding and issue an error.

Possible Solution

Check the encoding application for errors.


D0052S

Message Format

D0052S: Expected constructed type but found primitive

Message Cause

The decoder found a primitive encoding of a SEQUENCE, SEQUENCE OF, SET, SET OF, or an explicitly-tagged type. The encoding of these types can only be constructed, according to the ASN.1 standard.

Similar errors can occur when the data in the encoded buffer is not aligned correctly. For example, if the address of OssBuf.value does not match the beginning of a new encoding, the decoder could misinterpret the encoding and issue an error.

Possible Solution

Check the encoding application for errors.


D0053S

Message Format

D0053S: Expected primitive type but found constructed

Message Cause

The decoder found a constructed encoding of a BOOLEAN, INTEGER, ENUMERATED, REAL, NULL, or OBJECT IDENTIFIER type. The encoding of these types can only be primitive, according to the ASN.1 standard.

Similar errors can occur when the data in the encoded buffer is not aligned correctly. For example, if the address of OssBuf.value does not match the beginning of a new encoding, the decoder could misinterpret the encoding and issue an error.

Possible Solution

Check the encoding application for errors.


D0054S

Message Format

D0054S: PDU tag not recognized:

Message Cause

The decoder found an encoding of a PDU whose tag is not listed in the generated control-table or code file.

Possible Solutions

  • Confirm that the correct control-table or code file was linked when the application executable was built.
  • Make sure that the PDU number passed to the decoder matches the ASN.1 type to be decoded. Use the compiler-generated typename_PDU constant for this purpose.
  • Check that the correct encoding rules are set, that is, those that match the data to be decoded. For example, to decode PER ALIGNED encodings, issue the following function call before calling the decoder:
    ossSetEncodingRules(world, OSS_PER_ALIGNED);

x0055E

This error code is currently not in use.


D0056S

Message Format

D0056S: This error cannot happen; inform OSS, code = number

Message Cause

The decoder encountered an unknown exception error.

Possible Solution

Email your exact decoder input to OSS Nokalva Support. Include your product license number, located in the comment at the top of the ASN.1 compiler-generated header and c/cpp/java files and the OSS ASN.1 Tools version and platform you are using.


D0057S

Message Format

D0057S: Decoder argument for length is negative; length = negative number

Message Cause

The user provided a pre-allocated output buffer for the decoder, but its specified length is negative.

Possible Solutions

  • Use the ossSetDecodingLength() function to specify a non-negative length for the pre-allocated buffer.
  • Instruct the decoder to automatically allocate output memory by passing a NULL pointer as the fourth argument to ossDecode().

D0058E

Message Format

D0058E: Expected tag, found EOC octets

Message Cause

The decoder found an end-of-contents octet where a tag for an ASN.1 type was expected.

Possible Solution

Check the encoding application for errors. When decoding PER, make sure to specify OSS_PER_ALIGNED or OSS_PER_UNALIGNED using the ossSetEncodingRules() function before calling the decoder; PER encodings do not have tags.


D0059E

Message Format

D0059E: The value is not an encoding of a single ASN.1 type.

Message Cause

The decoder found an ANY or open type encoding that contains more than one value. Both types can contain only one value.

Possible Solution

Check the encoding application for errors. When decoding from a file, confirm that your application code is linked with the file memory manager and that ossMarkObj() is called to reference the encoded data.


D0060S | V0060S

Message Format

D0060S: User constraint function returns error

Message Cause

The decoder called a user-defined constraint function to check a type value; the function returned a non-zero error code.

Possible Solutions

  • Provide input to the decoder containing values that satisfy the user constraint.
  • Use the -noUserConstraints option when ASN.1-compiling your syntax.

D0061S | V0061S

Message Format

D0061S: Single value constraint violated, value = value

Message Cause

The decoder detected a single value constraint violation for an INTEGER, REAL, or character string type.

Possible Solutions

  • Provide input to the decoder containing values that satisfy the constraint.
  • Use the -noConstraints option when ASN.1-compiling your syntax.

D0062S | V0062S

Message Format

D0062S: Value range constraint violated, value = value

Message Cause

The decoder detected a value range constraint violation for an INTEGER or REAL type.

Possible Solutions

  • Provide input to the decoder containing values that satisfy the constraint.
  • Pass the NOCONSTRAIN flag to the decoder using the ossSetFlags() function.

D0063S | E0063S | V0063S

Message Format

x0063S: Size constraint violated, length of value = value

Message Cause

  • The encoder/decoder was passed a value whose length exceeds that set either by a size constraint for the type or by the type definition.
  • This error can also occur for ASN.1 types with fixed non-variable sizes when the passed value has a length smaller than expected. In the following example:
    Payload-location ::=   OCTET STRING(SIZE(16))
    the (SIZE(16)) constraint specifies that the OCTET STRING is sixteen bytes long. So a Payload-location value with a length of 5 bytes would cause this error.
  • When the old (incorrect) size-constrained UTF8String C-representation is implied by the -compat charutf8string compiler option, the error could occur for valid type values that do not fit that representation.

Possible Solutions

  • Correct the encoder/decoder input to be within the allowed length range.
  • If the problem is caused by a fixed size constraint, change it to a variable size constraint, as shown in the following example:
    Payload-location ::=   OCTET STRING(SIZE(1..16))
    The (SIZE(16)) constraint specifies that the OCTET STRING can be between one and sixteen bytes long.
  • Similar errors can result when a specification is ASN.1-compiled with the wrong asn1dflt file. When your ASN.1 compiler runs on a platform different from your target (runtime) platform, use the ASN.1 compiler with the correct asn1dflt file to generate output compatible with your target platform. Specify the asn1dflt file on the command-line before any other input files. Also, on Windows and similar platforms, be sure to use the asn1dflt file that matches the data packing and alignment option (e.g., /zp4, /a8) used to C or C++ compile.

D0064S | E0064S | V0064S

Message Format

x0064S: Permitted alphabet constraint violated, bad character:

Message Cause

The encoder/decoder found a permitted alphabet constraint violation for a character string type.

Possible Solutions

  • Provide decoder input containing values that satisfy the constraint.
  • Pass the NOCONSTRAIN flag to the decoder using the ossSetFlags() function before attempting to process the invalid value.
  • Apply the OSS.NoConstrain compiler directive to the problematic type.
  • Compile your ASN.1 syntax with the -noConstrain option specified. This will disable constraint checking for all PDUs in the input.

NOTE: When encoding/decoding multilingual characters, use the BMPString (2-octets per character) or UniversalString ASN.1 type (4-octets per character).


D0065S | E0065S | V0065S

Message Format

x0065S: Absence constraint violated

Message Cause

The constraint checker found that a component marked ABSENT in a WITH COMPONENTS is present in the input.

Possible Solutions

  • Provide input to the decoder containing values that satisfy the specified constraint.
  • Turn on the NOCONSTRAIN flag using the ossSetFlags() function.

D0066S | E0066S | V0066S

Message Format

x0066S: Presence constraint violated

Message Cause

The constraint checker found that a component marked PRESENT in a WITH COMPONENTS is absent from the input.

Possible Solutions

  • Provide input to the encoder/decoder containing values that satisfy the specified constraint.
  • Turn on the NOCONSTRAIN flag using the ossSetFlags() function.

D0067S | E0067S

Message Format

x0067S: Error in copying an open type

Message Cause

The ossCmpValue() or ossCpyValue() function encountered an error while copying an open type.

Possible Solution

Make sure that the open type was decoded correctly.


D0068S | E0068S | V0068S

Message Format

x0068S: Table constraint violated

Message Cause

The encoder/decoder found an information object table constraint violation in the input.

Possible Solution

Provide encoder/decoder input containing values that satisfy the specified constraint.


D0069S | E0069S | V0069S

Message Format

  1. x0069S: Component relation constraint violated
  2. x0069S: Component relation constraint violated for extensible object set because the field does not belong
            to information objects with any UNIQUE field values.

Message Cause

  1. The encoder/decoder or constraint checker found a component relation constraint violation for an information object.
  2. A component relation constraint for an extensible object set was violated when a UNIQUE field value was found in the object set. This is in accordance with ITU-T Recommendation X.681 Annex E.2.

Possible Solution

Provide encoder/decoder input containing values that satisfy the specified constraint.


D0071S | E0071S

Message Format

x0071S: Value not among the ENUMERATED: value

Message Cause

The encoder/decoder found an ENUMERATED type with a value that does not match any of the declared enumerators.

Possible Solution

Provide encoder/decoder input containing values that conform to the enumerators declared in the ASN.1 specification. Use the ASN.1 compiler-generated named-enumerators for this purpose.


E0072E

Message Format

E0072E: Length of encoded component unexpectedly 0, field field

Message Cause

The encoder found a zero length field specified for a SET, SEQUENCE, CHARACTER STRING, or EMBEDDED PDV type.

Possible Solution

Specify a non-zero length for the problematic field.


D0073S | E0073S

Message Format

x0073S: Attempt made to pass a NULL control table pointer

Message Cause

The Time-Optimized BER/PER/XER/E-XER/OER Encoder/Decoder found a passed code file pointer that is NULL.

Possible Solutions

  • Make certain that a non-NULL code-file pointer is passed to the ossinit() function.
  • Do not manually modify the OssGlobal structure's reserved fields.

D0074S | E0074S

Message Format

x0074S: NULL function pointer in the control table

Message Cause

The Time-Optimized BER/PER/XER/E-XER Encoder/Decoder found a NULL pointer contained in the OssGlobal structure where a non-NULL function pointer was expected.

Possible Solutions

  • Make certain that a non-NULL code-file pointer is passed to the ossinit() function.
  • Do not manually modify the OssGlobal structure's reserved fields.

D0075S | E0075S

Message Format

x0075S: The control table appears to have been corrupted

Message Cause

The encoder/decoder found that the OssGlobal structure points to a corrupt control table.

Possible Solution

Do not manually modify the OssGlobal structure's reserved fields.


D0076S

Message Format

D0076S: A negative unsigned integer encountered

Message Cause

The decoder found an unsigned INTEGER value whose bits resemble a negative number.

Possible Solutions

  • Fix the invalid value.
  • Specify the RELAXBER runtime flag using the ossSetFlags() function.

D0077S | E0077S

Message Format

x0077S: Size constraint violated, number of SET OF/SEQUENCE OF components = number

Message Cause

The encoder/decoder found a SET OF or SEQUENCE OF type with more elements than is allowed by a SIZE constraint in the ASN.1 specification.

Possible Solutions

  • Reduce the number of elements to comply with the SIZE constraint.
  • Make sure the address of the encoding/decoding structure, not the actual structure, is passed as the third argument to ossEncode() or ossDecode().

D0078S | E0078S

Message Format

x0078S: Type constraint violated, PDU number = number

Message Cause

The encoder/decoder found a type constraint violation in the input.

Possible Solution

Provide constraint-compliant input to the encoder/decoder.


D0079S | E0079S

Message Format

x0079S: User-defined open type user-field-handling function returned a non-zero error code

Message Cause

ossCmpValue() or ossCpyValue() called your user-defined OpenType.userField checking function, set using the ossSetUserFieldCpyCmp() function, but your function returned a non-zero error code.

Possible Solution

Pass two NULL pointers as the second and third arguments to the ossSetUserFieldCpyCmp() function.


D0080E

Message Format

D0080E: Bit string value too long for local representation

Message Cause

The decoder found a value for a BIT STRING type that is too large to fit in the local C/C++ representation.

Possible Solution

Use the OSS.UNBOUNDED directive to achieve a representation of the BIT STRING type that can be arbitrarily large.


D0081S

Message Format

D0081S: End of input reached before message was fully decoded

Message Cause

The decoder encountered the end of the input buffer before the PDU under process was fully decoded.

Possible Solution

Make sure that the length field of the input OssBuf variable is correctly set to the full length of the input buffer.


D0083S | E0083S

Message Format

x0083S: Zero bytes of memory requested

Message Cause

The encoder/decoder memory manager received a request for zero bytes of memory.

Possible Solution

Make sure your input to the encoder/decoder is valid. Call the ossPrintPDU() function on data to be immediately encoded before calling the encoder to ensure that the PDU contains what is expected. Additionally, if you wrote your own memory manger, make sure it contains no such error.


D0084S | E0084S

Message Format

x0084S: Attempt made to allocate a block of memory greater than 'ossblock'; bytes requested = number of bytes

Message Cause

The encoder/decoder memory manager received a request to allocate a block of memory greater than either the limit set by OssGlobal.ossblock or LONG_MAX bytes.

Possible Solution

If the ossblock field of the OssGlobal structure is too small to accommodate the size of the chunk that to be allocated by the memory manager, then increase it. This error could also occur if the encoded data is corrupt.

Note

The C compiler for Alpha/OSF has an issue that could make this error message falsely appear in some cases.


D0085S | E0085S

Message Format

x0085S: Memory allocation failed; bytes requested = number of bytes

Message Cause

The encoder/decoder memory manager received an "out of memory" signal from the operating system.

Possible Solution

Increase your application stack size.


D0086S | E0086S

Message Format

x0086S: Unrecognized memory object, address = address

Message Cause

The encoder/decoder memory manager was passed a memory object that fails the check-bounds test.

Possible Solutions

  • Make sure that the input to the encoder/decoder is valid.
  • This error can also occur if you pre-allocate the output buffer for the encoder but then fail to set OssBuf.length to the length in bytes of your pre-allocated buffer before calling the encoder. To have the encoder allocate memory for the output automatically, set OssBuf.value to NULL and OssBuf.length to zero before calling the encoder.

D0087S | E0087S

Message Format

x0087S: Undefined memory-management error error-code-number

Message Cause

The encoder/decoder memory manager received one of the following errors:

TYPE OF ERROR                   ERROR CODE
------------------------------------------
cantOpenInputFile                    1
cantCloseInputFile                   2
cantOpenOutputFile                   3
cantCloseOutputFile                  4
errorWritingToFile                   5
errorReadingFromFile                 6
cantOpenTemporaryFile                7
cantCloseTemporaryFile               8
cantRemoveTemporaryFile              9
unknownObject                       10
deferedValueInInitialBuffer         11
incorrectOffsetToDeferedValue       12
endOfInputFile                      13
errorWritingToSocket                14
errorReadingFromSocket              15
cantLoadSocketDLL                   16
cantGetProcAddress                  17
invalidSocketHandle                 18

Possible Solutions

  • Fix the error described by the error code.
  • When encoding a value from a file, make sure that the length of the data you specify is correct. This error message is issued when the length you specify is larger than the size of the encoder input file.
  • If you are trying to use the file or socket memory manager, make sure that you specify the OSS Nokalva file or socket memory manager library file on your linker command line before you specify the encoder/decoder library file.
  • The errorReadingFromSocket or errorWritingToSocket error is sometimes returned when the encoder/decoder experiences a socket timeout error. Use the ossSetTimeout() OSS API function to change the maximum allowed socket wait time.
  • When using Microsoft VC++ on Windows (see note) with the file or socket memory manager DLL, make sure that you C-compile your application with the /MD option and not the /MT option. If working in a multi-threaded environment, make sure that you do not call ossterm() in a thread from which you wish to later encode/decode data to/from a socket/file.

NOTE: The Windows socket routines also return error-failure codes:

  WSAEACCES (10013)     WSAEADDRINUSE (10048)     WSAEADDRNOTAVAIL (10049)  
  WSAEAFNOSUPPORT (10047)     WSAEALREADY(10037)     WSAECONNABORTED (10053)  
  WSAECONNREFUSED (10061  )   WSAECONNRESET (10054)     WSAEDESTADDRREQ (10039)  
  WSAEFAULT (10014)     WSAEHOSTDOWN (10064)     WSAEHOSTUNREACH (10065)  
  WSAEINPROGRESS (10036)     WSAEINTR (10004  )   WSAEINVAL (10022)  
  WSAEISCONN (10056)     WSAEMFILE (10024)     WSAEMSGSIZE (10040)  
  WSAENETDOWN (10050)     WSAENETRESET (10052)     WSAENETUNREACH (10051)  
  WSAENOBUFS (10055)     WSAENOPROTOOPT (10042)     WSAENOTCONN (10057)  
  WSAENOTSOCK (10038)     WSAEOPNOTSUPP (10045)     WSAEPFNOSUPPORT (10046)  
  WSAEPROCLIM (10067)     WSAEPROTONOSUPPORT (10043)     WSAEPROTOTYPE (10041)  
  WSAESHUTDOWN (10058)     WSAESOCKTNOSUPPORT (10044)     WSAETIMEDOUT (10060)  
  WSATYPE_NOT_FOUND (10109)     WSAEWOULDBLOCK (10035)     WSAHOST_NOT_FOUND (11001)  
  WSANOTINITIALISED (10093)     WSANO_DATA (11004)     WSANO_RECOVERY (11003)  
  WSAPROVIDERFAILEDINIT (OS dependent)     WSASYSNOTREADY (10091)     WSATRY_AGAIN (11002)  
  WSAVERNOTSUPPORTED (10092)     WSAEDISCON (10094)  

Refer to a list of WinSock error messages to learn the significance of these codes. Then try to figure out what went wrong. For example, if a 10038 error code is returned (socket not available), it probably means that you are trying to read from a socket that has either not been opened or has been prematurely closed.


D0089E | E0089E

Message Format

x0089E: Length of encoded data of ANY is 0

Message Cause

The decoder found an ANY type whose encoding was found to have a length of zero.

Possible Solutions

  • If you are manually encoding open types or ANY types, make sure that you initialize the encoded and length fields to the encoded value and the length in bytes of the encoded value.
  • If decoding, check the encoding application for errors.

D0090E | E0090E

Message Format

x0090E: Length of encoded data of OpenType is 0

Message Cause

The decoder found an open type whose encoding was found to have a length of zero.

Other Causes

  • You are trying to automatically encode/decode an open type but forgot to set the AUTOMATIC_ENCDEC runtime flag.
  • You are trying to automatically encode/decode an ASN1.DeferDecoding open type. Open types created using the ASN1.DeferDecoding directive can only be manually encoded/decoded separate from their containing structures (unless the IGNOR_DEFER_DECODING runtime flag was specified).
  • You are trying to automatically encode/decode an open type that has no component relation constraint applied to it in the ASN.1 specification. Only open types with component relation constraints can be encoded/decoded automatically.
  • You are manually encoding/decoding an open type but forgot to set the encoding and length fields to reference the manually-encoded data and its length.
  • You compiled your ASN.1 specification with the -noConstrain option specified or set the NOCONSTRAIN flag of the encoder/decoder (unless you also specified the -autoEncDec ASN.1 compiler command- line option).

Possible Solutions

  • Check the encoding application for errors.
  • Make sure you are following the correct steps to encode/decode open types.

D0091E | E0091E

Message Format

x0091E: Invalid decimal REAL

Message Cause

The encoder encountered a REAL type stored in DECIMAL representation and found the contents of the character string containing the REAL value was invalid.

Possible Solution

Make sure the character string containing the decimal value to be encoded holds a valid value.


D0092E | E0092E

Message Format

x0092E: Invalid MixedReal, kind = description

Message Cause

The encoder found a REAL type with a MIXED representation; its value did not match either the decimal or binary representation of a REAL type.

Possible Solution

Make sure the REAL type is stored as either a decimal value or a regular binary number.


D0093E | E0093E

Message Format

x0093E: Too many optional fields in extension group

Message Cause

The PER decoder found a preamble, which indicates the presence and absence of optional PDU fields, to be more than 800 bits long.

Possible Solution

Reduce the number of optional fields so the preamble is less than 800 bits long.

NOTE: The decoder could issue this error when handed a corrupt PER encoding.


x0094E

Message Format

x0094E: Fatal error when encoding extension addition:

Message Cause

The encoder/decoder detected that an extension group in a SET or SEQUENCE type was missing a non-optional field.

Possible Solution

Check the encoding application for errors.


x0095S

Message Format

x0095S: Mandatory field is not present in extension group:

Message Cause

The encoder/decoder memory manager received an "out of memory" signal from the operating system.

Possible Solution

Increase your application stack size.


x0096S

Note

This error code is currently not in use.


D0097S | E0097S

Message Format

x0097S: Stack overflow. Provided buffer is too small; requested size:

Message Cause

The encoder/decoder memory manager received an "out of memory" signal from the operating system.

Possible Solution

Increase your application stack size.


D0098S | E0098S

Message Format

x0098S: Stack internal inconsistency had been detected

Message Cause

The encoder/decoder memory manager detected that a required buffer was locked.

Possible Solution

Do not call allocStack() manually until the required buffer is unlocked.


D0099E

Message Format

D0099E: Real value too large for local representation

Message Causes

  • The decoder found a REAL type value that is too large to fit in the chosen local representation for that type.
  • This message is also issued when the value to be decoded is a special REAL value (NONE or MINUS-ZERO) that is not supported on the platform.

Possible Solutions

  • Apply the OSS.DECIMAL or OSS.MIXED directive to the problematic type to obtain a representation for the REAL type that can hold a larger value.
  • Specify the OSS_RELAXED encoder/decoder runtime flag to decode NONE and MINUS-ZERO special values as zero.

D0100S | E0100S

Message Format

x0100S: Unknown encoding rules were requested, use BER/DER/CER/PER/XER/CXER/E-XER/OER only.

Message Cause

The encoder/decoder found a specified set of encoding rules was invalid.

Possible Solution

Use the ossSetEncodingRules() function to set the encoding rules and pass one of the following literals as the second argument: OSS_BER, OSS_DER, OSS_PER_ALIGNED, OSS_PER_UNALIGNED, OSS_CER, OSS_XER, OSS_CXER, OSS_EXER, OSS_OER.


x0101x

Note

This message number is not issued for the full commercial version of the OSS ASN.1 Tools.


x0102x

Note

This message number is not issued for the full commercial version of the OSS ASN.1 Tools.


D0103S | E0103S

Message Format

x0103S: The requested encoding rules were not linked: theER

Message Cause

The encoder/decoder detected that the specified encoding rules were not included on the ASN.1 compiler command line when the input syntax was ASN.1-compiled.

Possible Solutions

  • Re-ASN.1-compile your input syntax with the compiler option for the desired set of encoding rules specified on the command line (-ber, -cer, -der, -per, -uper, -xer, -cxer, -exer, -oer, or -coer).
  • Make sure that the second argument to ossinit()/ossWinit() actually references the control-table or code-file to be used. NOTE: When using the OSS ASN.1 Tools for Java or C++, instantiate the correct Coder environment that corresponds to the encoding rules to be used.

D0104S | E0104S

Message Format

x0104S: Control table mismatch in ...

Message Cause

Different, incompatible versions of the ASN.1/C++ Runtime and the ASN.1/C++ Compiler were used.

Possible Solution

Use the Runtime version that is the same as the ASN.1 Compiler version used to compile the input specification.


D0105S | E0105S

Note

This error code is currently not in use.


D0106S | E0106S

Note

This error code is currently not in use.


D0107S | E0107S

Message Format

x0107S: REAL DLL failed:

Message Cause

The encoder/decoder could not access the OSS Nokalva dynamic library containing the routines needed for encoding/decoding REAL types.

Possible Solution

Make sure the OSS Nokalva DLLs are in your executable search path.


D0109S | E0109S

Message Format

x0109S: Constraint checker DLL failed:

Message Cause

The encoder/decoder could not access the OSS Nokalva dynamic library containing the routines needed for performing constraint checking on the input ASN.1 types.

Possible Solution

Make sure the OSS Nokalva DLLs are in your executable search path.


D0110S | E0110S

Message Format

x0110S: Value comparator DLL failed:

Message Cause

The encoder/decoder could not access the OSS Nokalva dynamic library containing the routines needed for comparing and copying decoded PDUs.

Possible Solution

Make sure the OSS Nokalva DLLs are in your executable search path.


D0111S | E0111S

Message Format

x0111S: Value comparator code not linked or initialized

Message Cause

The encoder/decoder could not find the value comparator routines in the target executable code.

Possible Solution

Re-link the application object code with the OSS Nokalva value comparator function library.


D0112S | E0112S

Message Format

x0112S: REAL code not linked or initialized

Message Cause

The encoder/decoder could not find the REAL type-handling routines in the target executable code.

Possible Solution

Re-link the application object code with the OSS Nokalva REAL type-handling function library.


D0113S | E0113S

Message Format

x0113S: Tracing code not linked or initialized

Message Cause

The encoder/decoder memory manager received an "out of memory" signal from the operating system.

Possible Solution

Increase your application stack size.


D0114S | E0114S

Note

This message number is currently not in use.


D0115S | E0115S

Message Format

x0115S: OBJECT IDENTIFIER converter DLL failed:

Message Cause

The encoder/decoder could not access the OSS Nokalva dynamic library containing OBJECT IDENTIFIER value conversion routines.

Possible Solution

Make sure the OSS Nokalva DLLs are in your executable search path.


D0116S | E0116S

Message Format

x0116S: Data type is not supported by DER time-optimized encoder

Message Cause

The DER encoder/decoder detected an unsupported ASN.1 type representation. The following representations are not currently supported:

DLINKED SEQUENCE OF
DLINKED SET OF
PADDED character string
NULLTERM LINKED character string
NULLTERM DLNKED character string
UNBOUNDED DLINKED ANY
UNBOUNDED LINKED BIT STRING
UNBOUNDED DLINKED BIT STRING
UNBOUNDED LINKED character string
UNBOUNDED DLINKED character string
UNBOUNDED LINKED OCTET STRING
UNBOUNDED DLINKED OCTET STRING
VARYING LINKED BIT STRING
VARYING DLINKED BIT STRING
VARYING LINKED character string
VARYING DLINKED character string
VARYING LINKED OCTET STRING
VARYING DLINKED OCTET STRING

Possible Solution

Remove the unsupported representation from the ASN.1 input.


D0117S

Message Format

D0117S: Expected definite length, found indefinite length DER encoding

Message Cause

The decoder found a DER encoding in which a component was encoded using the indefinite length form. This is invalid; by definition DER only uses the definite length form.

Possible Solution

Check the encoding application for errors.


D0118S | E0118S

Message Format

x0118S: The encoder/decoder was generated without support for selected encoding rules:

Message Cause

The encoder/decoder detected that the specified encoding rules were not included on the ASN.1 compiler command line when the input syntax was ASN.1-compiled.

Possible Solution

Re-ASN.1-compile your input syntax with the compiler option for the desired set of encoding rules specified on the command line (-ber, -cer, -der, -per, -uper, -xer, -cxer, -exer, -oer, or -coer).


D0119S | E0119S

Message Format

x0119S: Error converting character to UTF8 format at position

Message Cause

The encoder/decoder could not find a valid UTF8String character to map to when converting a UCS-4 or UCS-2 string to a UTF8String.

Possible Solutions

Design a filtering mechanism to remove invalid characters before they get to the encoder/decoder.


D0120S | E0120S

Message Format

x0120S: Incorrect sequence of octets in UTF8String

Message Cause

The encoder/decoder found an invalid character in a UTF8String, probably from converting a UCS-4 or UCS-2 string to a UTF8String.

Possible Solution

Design a filtering mechanism to remove invalid characters before they get to the encoder/decoder.


D0121E | D0121S | E0121E | E0121S

Message Format

x121E/S: Encoding contains a value for a removed field

Message Cause

The decoder found a component value marked with the ASN1.Remove compiler directive in the original ASN.1 specification.

Possible Solution

Delete the ASN1.Remove compiler directive from the problematic field.


D0122S | E0122S

Message Format

x0122S: End of input reached before PDU was fully decoded; additional bytes expected:

Message Cause

The decoder found that the input encoding ended prematurely, before all the mandatory fields of a PDU were decoded.

Possible Solution

Check the encoding application or the transmission method for errors.


D0123S | E0123S

Message Format

x0123S: PER tracing DLL failed:

Message Cause

The encoder/decoder could not find the PER trace routines dynamic library.

Possible Solution

Make sure that the OSS Nokalva DLLs are in your operating system's search path.


E0124S

Message Format

E0124S: Unable to relay unknown extension: relay-safe encoding has not been enabled

Message Cause

This message occurs if the -relaySafe compiler option was not specified and the input PDU contains an extensible CHOICE or an extensible ENUMERATED whose value is an unknown extension. The bits of the unknown extension are not stored for future use if the -relaySafe option is not specified.

Possible Solution

Specify the -relaySafe compiler option or obtain the updated versions of your .asn files that match the protocol version of the binary data.


Message Format

E0124S: Unable to relay unknown extension: the extension was decoded by the <Coder1> but is relayed by the <Coder2>

Message Cause

This message occurs if the -relaySafe compiler option was specified for an input PDU that contains unknown extension data, and the current encoding rules are different from the ones used while decoding. For example, the error message occurs when the PER encoder detects an unknown extension that was stored while decoding a BER-encoded message.

Example Message

E0124S: Unable to relay unknown extension: the extension was decoded by the Packed Encoding Rules (PER - Aligned) Coder but is relayed by the Basic Encoding Rules (BER) Coder

Possible Solution

Make sure the -relaySafe compiler option is not specified or obtain the updated versions of your .asn files that match the protocol version of the binary data.


D0125I

Message Format

D0125I: End of input file detected; no PDU was decoded from:

Message Cause

The Space-Optimized decoder detected that the file pointer passed to it was set beyond the end of the decoder input file. If you attempt to continue decoding after processing the last concatenated PDU on a file, this error code could result. The decoder returns EOF_INPUT_FILE when issuing this message.

Possible Solution

Stop calling the decoder after the last PDU on the file has been decoded.


D0126S | E0126S | V0126S

Message Format

x0126S: Value does not satisfy its subtype constraints

Message Cause

The Java Tools encoder/decoder found that an ASN.1 type value does not satisfy an applied subtype constraint.

Possible Solution

Correct the value to comply with the subtype constraint.


D0127S | E0127S

Message Format

x0127S: Coder error when automatically encoding/decoding open type

Message Cause

The Java Tools encoder/decoder experienced an error when trying to automatically encode/decode an open type.

Possible Solution

Make sure that the open type you want to encode/decode can be automatically encoded/decoded accurately.


D0128S | E0128S | V0128S

Message Format

x0128S: Unexpected exception

Message Cause

The Java Tools encoder/decoder found a thrown exception that did not have pre-defined error-handling.

Possible Solution

Make sure that you are not using the ASN.1 Tools components incorrectly.


D0129S | E0129S

Message Format

x0129S: Invalid REAL NaN in input

Message Cause

The Java Tools encoder/decoder encountered a REAL type component value that is not a number.

Possible Solution

Store only numerical data in a REAL type representation.


D0130S | E0130S

Message Format

x0130S: internal error

Message Cause

The Java Tools encoder/decoder encountered an internal error.

Possible Solution

Contact OSS Nokalva Support.


D0131S | E0131S

Message Format

x0131S: Can not open input file: filename

Message Cause

The encoder/decoder encountered an access error when trying to open the input data file.

Possible Solution

Make sure that the process running your application has read permission for the file to be opened.


D0132S

Message Format

D0132S: Buffer provided for temporary memory is too small; Bytes requested: number

Message Cause

The Time-Optimized Decoder found that the size of the temporary memory buffer specified with the ossSetTemporaryBuffer() function is too small.

Possible Solution

Call the ossSetTemporaryBuffer() function with a pre-allocated buffer large enough to accommodate the number of bytes requested. The memory required is about 5 to 10 kilobytes more than the actual memory needed, so plan accordingly.


D0133S

Message Format

D0133S: Internal error: Problem with temporary buffer. Please contact OSS.

Message Cause

The Time-Optimized Decoder encountered a problem freeing the memory associated with the temporary memory buffer in use.

Possible Solution

Contact OSS Nokalva Support.


D0134S | E0134S

Message Format

x0134S: Your trial period has expired

Message Cause

You are using a TRIAL version of the ASN.1 Tools that has expired.

Possible Solution

Contact OSS Nokalva Sales to request an extension of your trial.


D0135S | E0135S

Message Format

x0135S: Unrecoverable error

x0135: An invalid use of the ossinfo file has been detected. Contact support@oss.com for further help.

x0135: This evaluation version of the OSS ASN.1/Java tools will only work on the machine where the software is installed. Please check that the license checker DLL is in your PATH or LD_LIBRARY_PATH. If you need additional help, please contact support@oss.com.

Message Cause

The runtime failed to validate your license.

Possible Solution

Perform any actions described in the error message text. Contact OSS Nokalva Support if you still get the error message.


D0136E

Message Format

D0136E: Length not a multiple of character width, length: length

Message Cause

The decoder found a multi-byte-character string type value with a length in bytes that is not a multiple of the string's individual character width. For example, a length of 5 bytes for a string made of two-byte characters is invalid.

Possible Solutions

  • Check the encoding application for errors.
  • Make sure that your compiler alignment options are set properly.

D0137E

Message Format

D0137E: Encoding of an object identifier must be primitive:

Message Cause

The BER/DER decoder encountered an OBJECT IDENTIFIER type encoding in constructed form. All OBJECT IDENTIFIER values must be encoded in primitive form according to the ASN.1 standard.

Possible Solutions

  • Check the encoding application for errors.
  • Make sure that the data is aligned properly in the decoder input buffer.

P0138S

Message Format

P0138S: User print function reported an exception

Message Cause

The user used the Printable interface to override the default printing method while decoded data was printing, causing the the user-defined printing method to raise an exception.

Possible Solution

None: this error was generated by the user's own code.


x0139S

Message Format

x0139S: Control table shared library failed to load:

Message Cause

The ossUinit() function could not load a control table or code file compiled as a DLL into memory at runtime.

Possible Solution

Make sure that the specified DLL name is correct and has the proper read or execute permission set.


x0140S

Message Format

x0140S: Control table shared library failed to unload:

Message Cause

The ossUterm() function could not unload a control table or code file compiled as a DLL from memory at runtime.

Possible Solution

Make sure that the memory stack was not corrupted during runtime.


E0141E

Message Format

E0141E: The 'decoded' and 'pduNum' fields were initialized but the AUTOMATIC_ENCDEC flag was not specified

Message Cause

The encoder was handed an OpenType structure for automatic encoding with all the necessary fields initialized but the user did not set the AUTOMATIC_ENCDEC flag.

Possible Solution

Use the ossSetFlags() function to add AUTOMATIC_ENCDEC to the list of runtime flags you set. NOTE: If using the OSS ASN.1 Tools for Java or C++, call enableAutomaticEncoding()to enable automatic encoding/decoding of open types.


E0142E

Message Format

E0142E: The 'decoded' field and AUTOMATIC_ENCDEC flag are specified but the 'pduNum' field was not initialized

Message Cause

The encoder was handed an OpenType structure with the AUTOMATIC_ENCDEC flag set and the decoded field initialized but the pduNum field was not set to the corresponding PDU's #defined identification number.

Possible Solution

Set the OpenType structure's pduNum field to the #defined constant (declared in the ASN.1-compiler-generated header file) that matches the data type contained in the open type.


E0143E

Message Format

E0143E: The DeferDecoding directive was used but the 'length' field was not initialized

Message Cause

The encoder was handed an OpenType structure (created using the ASN1.DeferDecoding directive) for encoding, but the encoded field length was not specified.

Possible Solution

Set the OpenType structure's length field to the length (in bytes) of the pre-encoded data to be contained by the open type and referenced by the encoded field.


D0144E | E0144E

Message Format

x0144E: Integer or enumerated value too long: length = length

Message Causes

  • The decoder found an integer or enumerated type value that is too large to fit in the chosen local representation for that type.
  • This message is also issued when the size of a HUGE integer value exceeds the implementation limit.

Possible Solution

Check the encoding application for errors.


E0145E

Message Format

E0145E: DER encoding for HugeSetOf not implemented

Message Cause

The --<ASN1.ValueInFile>-- directive is applied to a SET OF type in the input ASN.1. This directive is used to support huge SET OF values having many components that cannot be stored in memory, so file storage is needed to represent them. Encoding such huge values using DER is not supported.

Possible Solution

Consider using SEQUENCE OF instead of SET OF when you need to support huge values with DER.


E0146E

Note

This error code is currently not in use.


D0147E

Message Format

D0147E: XML attribute 'form' repeated; value used: value

Message Cause

The decoder found two form attributes in a single XML encoding. Only one such form attribute is used per encoding.

Possible Solution

Check the encoding application for errors.


D0148E

Message Format

D0148E: XML attribute name and/or value is incorrect: name or value

Message Cause

The decoder found an unrecognized or unsupported form attribute in the input XER encoding.

Possible Solution

Check the encoding application for errors.


D0149E

Message Format

D0149E: Expecting XML start-tag

Message Cause

The XER decoder expected an XML start-tag (e.g., at the beginning of the encoding of a type), but encountered something else in the input encoding.

Possible Solution

Check the encoding application for errors.


D0150E

Message Format

D0150E: Expecting XML start-tag or empty-tag

Message Cause

The EXTENDED-XER decoder expected an XML start-tag or empty-tag after the XML document prolog, but encountered something else in the input encoding.

Possible Solution

Check the encoding application for errors.


D0151E

Message Format

D0151E: XML tag name does not match PDU number: tag

Message Cause

The decoder found an XML tag mismatch between the sent encoding and the PDU to be decoded.

Possible Solution

Make sure that the PDU number passed to the decoder matches the PDU of the input encoding.


D0152E

Message Format

D0152E: Unrecognized or ambiguous PDU name: name

Message Cause

A zero PDU number was passed to the XER/CXER/E-XER decoder; the decoder could not clearly determine the PDU number from the PDU start tag.

Possible Solution

If the start tag does not match any PDU in the input syntax then check the encoding application for errors. Otherwise, try to avoid the ambiguity entirely by using the OSS.NOPDU compiler directive to eliminate unused PDUs. If the ambiguity is unavoidable then set the PDU number equal to the compiler-generated #defined PDU identification constant matching the type to be decoded.


D0153E

Message Format

D0153E: XML end-tag name does not match XML start-tag name: tag

Message Cause

The decoder found an XER end tag that does not match the type of the previous XER start tag.

Possible Solution

Check the encoding application for errors.


D0154E

Message Format

D0154E: Expecting XML end-tag

Message Cause

The decoder encountered the end of an XER encoding before an end tag was found.

Possible Solutions

  • Check the encoding application for errors.
  • Be sure to specify the correct length (in bytes) of the sent XER encoding.

D0155E

Message Format

D0155E: Expecting XML value of type

Message Cause

The decoder found a missing value in the sent XER encoding.

Possible Solution

Make sure that the sent encoding matches the schema set by the input ASN.1 definition for the type.


D0156E

Message Format

D0156E: Expecting <TRUE/> or <FALSE/>

Message Cause

The decoder found an XER BOOLEAN type whose value was other than the allowed <TRUE/> and <FALSE/> values defined by the XER standard.

Possible Solutions

  • Check the encoding application for errors.
  • Be sure to specify the correct PDU number if the value does not contain a BOOLEAN type.

D0157E

Message Format

D0157E: Expecting value for a component of SET / SEQUENCE / CHOICE but XML tag name does not match any component identifier: tag name

Message Cause

The decoder found a complex structured type value that is improperly built. The XER encoding is missing a mandatory field or contains an invalid field.

Possible Solutions

  • Check the encoding application for errors.
  • Be sure to specify the correct PDU number that matches the value to be decoded.

D0158E

Message Format

D0158E: Expecting XML empty-element tag for the named value but XML tag name does not match any named value: tag name

Message Cause

The decoder found a complex structured type value that is improperly built. The XER encoding does not have an empty tag for an optional field or contains an invalid field.

Possible Solutions

  • Check the encoding application for errors.
  • Be sure to specify the correct PDU number that matches the value to be decoded.

D0159E

Message Format

D0159E: Expecting mandatory whitespace between SET OF / SEQUENCE OF element values of space-separated list

Message Cause

The decoder found values for items in a SET OF or SEQUENCE OF type are not separated by white space as specified by the XER standard.

Possible Solutions

  • Check the encoding application for errors.
  • Be sure to specify the correct length, in bytes, of the sent XER encoding.

D0160E | E0160

Message Format

x0160E: Control table is not usable by XER

Message Cause

The encoder/decoder found that the ASN.1-compiler produced control table lacked debugging information critical to handling XER encodings.

Possible Solution

When ASN.1-compiling the input specification, be sure to specify the -xer option and to not specify the -noDebug option.


D0161E

Message Format

D0161E: Illegal UCS-4 character found: character

Message Cause

The decoder found a character following a UCS-4 escape sequence is not a valid character.

Possible Solution

Check the encoding application for errors.


D0162S | E0162S | V0162S

Message Format

x0162S: Pattern constraint violated, value = string value

Message Cause

The encoder/decoder detected a PATTERN constraint violation in a restricted character string type value.

Possible Solution

Modify the value to conform to the PATTERN constraint specified in the input ASN.1 specification.


D0163S | E0163S

Message Format

x0163S: Pattern constraint checker not linked or initialized

Message Cause

The encoder/decoder found a request to check a PATTERN constraint value but the ASN.1 compiler did not generate a pattern constraint link function in the output file.

Possible Solution

Recompile the ASN.1 specification with the PATTERN constraint specified. Do not specify the -noConstraint option.


D0164S | E0164S

Message Format

x0164S: This configuration of the runtime does not support this operation

Message Cause

The osslean.jar lean runtime library does not support automatic encoding and decoding of contained values. Contained values are values carried inside a BIT STRING or OCTET STRING type value; the CONTAINING clause constrains the type content.

Possible Solution

Either manually decode/encode the contained values or use oss.jar, the full runtime library.


D0165S | E0165S

Message Format

x0165S: The OSS.OBJHANDLE directive was applied to an item that has fragmented encoding

Message Cause

The encoder/decoder found that a fragmented type was sent for encoding/decoding. For example, CER requires string values to be encoded as constructed encodings when more than 1000 contents octets are required. So, for the following specification

A ::= OCTET STRING --<NOCOPY>--

If the value of type A above contains more than 1000 octets the x0165S runtime error will occur.

Possible Solution

Recompile the ASN.1 specification without the OSS.OBJHANDLE or OSS.NOCOPY directive applied.


D0166E

Message Format

D0166E: XML tag name expected

Message Cause

The decoder found an XER message containing an opening bracket (e.g., "<" or "</") without a following XML tag name.

Possible Solution

Use the line number and position in the diagnostic error message to locate the error in the XER encoding, then fix the encoding application accordingly.


D0167E

Message Format

D0167E: Invalid syntax for XML tag

Message Cause

The decoder found an XER message that has a tag with a syntax error, such as multiple front slashes in a closing tag (e.g., "</tag-name/>") or a missing closing angle bracket (e.g., "<tag-name").

Possible Solution

Use the line number and position in the diagnostic error message to locate the error in the XER encoding, then fix the encoding application accordingly.


D0168E

Message Format

D0168E: Invalid XML tag name 'name'

Message Cause

The decoder found an XML tag name that violates standard conventions. For example, it contains characters forbidden by the X.693 standard.

Possible Solution

Use the line number and position in the diagnostic error message to locate the error in the XER encoding, then fix the encoding application accordingly.


D0169E

Message Format

D0169E: XML tag name too long

Message Cause

The decoder found an XML tag name longer than 256 characters, which is the maximum length permitted by the decoder.

Possible Solution

Use the line number and position in the diagnostic error message to locate the error in the XER encoding, then fix the encoding application accordingly. If you require support for such long identifiers, contact OSS Nokalva Support.


D0170E

Message Format

D0170E: XML comment expected

Message Cause

The XER decoder found an XML comment start token ("<!") but the ensuing characters violate the guidelines for XML comments set in the W3C XML standard.

XML comments are forbidden within XER encodings as defined by the ASN.1:2015 standard, but OSS has relaxed this restriction in the decoder for your convenience. Thus, comments are never produced by the XER encoder and are silently ignored by the XER Space-Optimized (but not Time-Optimized) Decoder. Contact OSS Nokalva Support if you need XML comment support while using the Time-Optimized Decoder.

Possible Solution

Use the line number and position in the diagnostic error message to locate the error in the XER encoding, then fix the encoding application accordingly.


D0171E

Message Format

D0171E: Illegal XML escape sequence found

Message Cause

An XML escape sequence of form "&[escape-pattern];" was found in the XER input but the value of the specified escape-pattern is not valid (e.g., is not an "amp"/"lt"/"gt"/[number]/x[hex_number]).

Possible Solution

Use the line number and position in the diagnostic error message to find the exact location of the error in the XER encoding and fix the encoding application accordingly.


D0172E

Message Format

D0172E: Unexpected XML comment

Message Cause

The decoder encountered an XML comment within a component of an XER encoding that does not allow such (e.g., inside of an XML tag).

Possible Solution

Use the line number and position in the diagnostic error message to find the exact location of the error in the XER encoding and fix the encoding application accordingly.


D0173E

Message Format

D0173E: Typereference expected, conflicting PDU: pdu_number

Message Cause

This error message is now obsolete and should not be issued.


D0174E

Message Format

D0174E: Canonical XER restrictions violated: 'message'

Message Cause

The Canonical XER decoder encountered a standards violation in the input encoding.

Example Messages

D0174E: Canonical XER restrictions are violated: 'XML encoding for Contained types should have been used'; check PDU #1 'A' at line 1 position 4.

This message is issued for incorrect contained type encodings.

Some other possible error messages are listed below, along with the exact clause in X.693 that was violated.

'XML prolog not allowed'

(9.1.1) <?xml ... ?> is not allowed at the beginning of the encoded data.

'whitespace not allowed'

(9.1.2) No unnecessary white space characters are allowed.

'invalid characters sequence'

(9.1.3) "&#...;" and "&#x...;" character sequences are not allowed.

'empty-element tag expected'

(9.1.4) Empty-element encoding was possible, but was not used.

'REAL zero must consist of single digit 0'

(9.2.1) A real zero value must contain a single digit 0.

'integer part of REAL must consist of a single non-zero digit'
'REAL value must contain decimal point'
'REAL value must contain fractional part'
'REAL value may not contain trailing zeroes in fractional part'

(9.2.3) The restrictions listed above represent different situations from this clause.

'REAL value must contain capital E followed by exponent'

Clause 9.2.4 is violated.

'REAL value may not contain plus sign(s)'

Clause 9.2.5 is violated.

'no trailing zeroes allowed for this BIT STRING type'

(9.3.2) Trailing zero bits are forbidden in the encoding of BIT STRINGs with named bits.

'default value encoding should have been present'

(9.5, 9.6.3) All components of a SET or SEQUENCE having DEFAULT values, with abstract values set to those DEFAULTs, shall always have the encoding of the default values textually present.

'number form of OBJECT IDENTIFIER should have been used'

(9.8) 'name' and 'name(number)' representations are not allowed for OBJECT IDENTIFIER components; use a numeric representation only.

'time type value must end with Z'

Clause 9.10.1 or 9.11.1 is violated.

'seconds should have been present'

Clause 9.10.2 or 9.11.2 is violated.

'invalid midnight representation'

Clause 9.10.5 or 9.11.3 is violated.

'decimal point should have been used to separate fractal portions of seconds'

Clause 9.10.4 is violated.

'seconds fraction should not contain trailing zeroes'

Clause 9.10.3 is violated.

'XML encoding for contained types should have been used'

For BIT STRING and OCTET STRING types with contents constraints, the CXER standard requires XMLTypedValue form to be present whenever possible.

Possible Solutions

  • Use the line number and position in the diagnostic error message to find the exact location of the error in the XER encoding and fix the encoding application accordingly.
  • Switch to Basic XER if your application does not require unique encodings to be produced.

D0175E

Message Format

D0175E: Illegal character in XML character string: char_code

Message Cause

The XER decoder detected a forbidden character in an XML character string: either a literal UTF-8 character or an escape sequence representing that character. Note that only characters in the range of #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] are permitted according to the XML and XER standards.

Possible Solution

Use the line number and position in the diagnostic error message to find the exact location of the error in the XER encoding and fix the encoding application accordingly.


D0176E

Message Format

D0176E: XML tag name does not match SET OF / SEQUENCE OF element type: name

Message Cause

The decoder found an XML tag in the XER encoding of a SET OF or SEQUENCE OF type but its name does not match the expected name of the contained type. It is possible that the XML tag name in the encoding is not the same as the type defined in the SET OF / SEQUENCE OF or that there is a typographical error in the encoding.

Example

M1 DEFINITIONS ::= BEGIN
S ::= SEQUENCE OF myInt INTEGER
-- correct sample encoding:
--     <S><myInt>123</myInt></S>
END

Incorrect XER encoding for this type:

<S><INTEGER>123</INTEGER></S>

Message for Example

D0176E: XML tag name does not match SET OF / SEQUENCE OF element type: 'INTEGER'; check element #1 (type: myInt) of PDU #1 'S' at line 1 position 12.

Possible Solution

Use the line number and position in the diagnostic error message to find the exact location of the error in the XER encoding and fix the encoding application accordingly.


D0177E

Message Format

D0177E: Expecting XML empty-tag

Message Cause

The XER decoder failed to find an XML empty-tag where its presence is mandatory (e.g., XER encodings for an empty-element ENUMERATED type (after skipping the enclosing XML tags)).

Possible Solution

Use the line number and position in the diagnostic error message to find the exact location of the error in the XER encoding and fix the encoding application accordingly.


E0178E

Message Format

E0178E: The number of bits is not multiple of eight in the bit string's segment #number

Message Cause

The encoder input data contains a linked BIT STRING with two or more segments where a segment (which is not the last segment) contains a number of bits which is not a multiple of eight.

Possible Solution

Rearrange the BIT STRING list so that each segment (excluding the possibly the last segment) contains a number of bits which is a multiple of eight.


D0179E

Message Format

D0179E: Invalid number

Message Cause

The error occurs when decoding integer data using the XML encoding rules: XER, CXER or E XER.

Possible Solution

Check the encoding application for errors.


D0180E

Message Format

D0180E: Invalid hex digit in xmlhstring

Message Cause

The Java decoder found an invalid digit in an hexadecimal string contained within an XER encoding.

Possible Solution

Check encoding applications for errors.


D0181E

Message Format

D0181E: Invalid binary digit in xmlbstring

Message Cause

The Java decoder found an invalid digit in a binary string contained within an XER encoding.

Possible Solution

Check encoding applications for errors.


D0182E

Message Format

D0182E: Invalid object identifier

Message Cause

The Java decoder found an invalid object identifier value contained within an XER encoding.

Possible Solution

Check encoding applications for errors.


E0183E

Message Format

E0183E: XER coding for the data type has not been implemented yet

Message Cause

The Java encoder was passed a type for XER encoding which still has not been implemented.

Possible Solution

Contact OSS Nokalva Support to explain your requirements.


D0184E

Message Format

D0184E: The nesting level of constructed string encodings exceeded the limitation

Message Cause

The decoder received a constructed encoding with a number of successively nested encodings past the maximum allowed nest level.

Possible Solution

Either change the encoding application to produce encodings with lower nest levels or call the ossSetConstructedNestingLimit() routine to set a higher nesting limit.


D0185E

Message Format

D0185E: The nesting level of encoding of SET, SEQUENCE, SET OF, SEQUENCE OF or CHOICE exceeded the limitation

Message Cause

The decoder received an encoding of a complex type with a number of successively nested subtypes past the maximum allowed nest level.

Possible Solution

Either change the encoding application to produce encodings with lower nest levels or call the ossSetConstructedNestingLimit() routine to set a higher nesting limit.


E0186S

Message Format

E0186S: Constraints applied to FixedTypeValueSetFields or VariableTypeValueSetFields are not currently supported.

Message Cause

The input ASN.1 specification contains a constraint applies to a fixed type value set field or a variably type value set field whereas this type of constraint is currently not supported.

Possible Solution

Remove the unsupported constraint.


D0187E

Message Format

D0187E: Invalid XML tag attribute

Message Cause

The decoder detected invalid XML tag attribute syntax in the source encoding.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first attr=>&myName;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0187E: Invalid XML tag attribute; check field #0 of PDU #1 'S' at line 8 position 17.

Possible Solution

Check the encoding application for errors.


D0188E

Message Format

D0188E: Equal sign '=' after XML tag attribute expected

Message Cause

The decoder did not find an equal sign after the name of an XML tag attribute in the source encoding.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first attr>&myName;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0188E: Equal sign '=' after XML tag attribute expected; check field #0 of PDU #1 'S' at line 8 position 15.

Possible Solution

Check the encoding application for errors.


D0189S

Message Format

D0189S: Illegal character in XML character reference: character

Message Cause

The EXTENDED-XER decoder found a non-numeric character in an XML decimal character reference (&#num;) or a non-hexadecimal character in an XML hexadecimal character reference (&#xnum;).

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&#2x2;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0189S: Illegal character in XML character reference: 'x'; check field #0 of PDU #1 'S' at line 8 position 14.

Possible Solution

Check the encoding application for errors.


D0190S

Message Format

D0190S: Illegal XML character reference

Message Cause

The EXTENDED-XER decoder found an XML character reference that refers to a character forbidden in XML documents.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&#x11FFFF;Michael</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0190S: Illegal XML character reference; check field #0 of PDU #1 'S' at line 8 position 19.

Possible Solution

Check the encoding application for errors.


D0191S

Message Format

D0191S: Reference to unknown entity: entity name

Message Cause

The EXTENDED-XER decoder found an XML entity reference that is not a predefined entity and has not been declared in the local DTD section of the input XML document.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName2;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0191S: Reference to unknown entity: 'myName2'; check field #0 of PDU #1 'S' at line 8 position 11.

Possible Solution

Check the encoding application for errors.


D0192S

Message Format

D0192S: Illegal entity reference

Message Cause

The EXTENDED-XER decoder found an incorrectly formed XML entity reference (e.g., illegal characters are present between «&» and «;»).

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&my&#2;ame;</first>
  <last>Doe</last>
  <middle>N/A</middle>
</S>

Message for Example

D0192S: Illegal entity reference; check field #0 of PDU #1 'S' at line 7 position 14.

Possible Solution

Check the encoding application for errors.


D0193S

Message Format

D0193S: Undefined namespace prefix encountered: name

Message Cause

The EXTENDED-XER decoder encountered a qualified name, but the namespace prefix of this name has not been declared in any namespace attribute of any XML element that contains this name.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <pre:first>&myName;</pre:first>
  <last>Doe</last>
  <middle>N/A</middle>
</S>

Message for Example

D0193S: Undefined namespace prefix encountered: 'pre:first'; check field #0 of PDU #1 'S' at line 7 position 4.

Possible Solution

Check the encoding application for errors.


D0194S

Message Format

D0194S: CDATA section not finished

Message Cause

The EXTENDED-XER decoder encountered the end of the source document while reading a CDATA section.

Possible Solutions

  • Check the encoding application for errors.
  • Make sure that the correct length of the source encoding is specified in bytes.

D0195S

Message Format

D0195S: CDATA section expected

Message Cause

The EXTENDED-XER decoder found what seemed to be the start of a CDATA section but then detected incorrect syntax.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <last>
    <![CDATA Doe  ]>
  </last>
  <middle>N/A</middle>
</S>

Message for Example

D0195S: CDATA section expected; check field 'last' of PDU #1 'S' at line 9 position 14.

Possible Solution

Check the encoding application for errors.


D0196S

Message Format

D0196S: Illegal character in XML document: character

Message Cause

The EXTENDED-XER decoder found a character that is forbidden in XML documents, such as one with a code greater than 0x10FFFF.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "&#x1;">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <last>&#xE001;</last>
  <middle>M</middle>
</S>

Message for Example

D0196S: Illegal character in XML document: {0,0,0,1}; check field #0 of PDU #1 'S' at line 3 position 25.

Possible Solution

Check the encoding application for errors.


D0197S

Message Format

D0197S: Too complex XML document - probably recursive or deeply nested internal entities

Message Cause

The EXTENDED-XER decoder exceeded its internal recursion limit. This is most likely to occur when the document contains a recursive entity definition. It could also occur with complicated source specifications that use constraints extensively and the compiler cannot decipher tags in complex situations. In these situations, the decoder tries every possible alternative until one succeeds. When the specification contains many such constructs that are deeply nested, the decoder could also exceed the internal limit.

Possible Solution

Check the encoding application for errors.


D0198S

Message Format

D0198S: This type of entity is not supported yet

Message Cause

The EXTENDED-XER decoder found an entity definition or reference that is not currently supported (e.g., a parameter entity definition).

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY % children '(A,B,C)'>
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>Michael</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0198S: This type of entity is not supported yet at line 3 position 13.

Possible Solutions

  • Check the encoding application for errors.
  • Make certain that the encoding application does not produce XML documents using parameter, external, or unparsed entities.

D0199S

Message Format

D0199S: The buffer is too small for the encoded value

Message Cause

This message occurs when an XML element is being copied to the decoded value in the encoded form (this is done, for example, for open types or fields with the ANY-ELEMENT instructions specified), but the size of the user-provided buffer is too small to hold the entire value.

Possible Solutions

  • Increase the size of the destination buffer.
  • Decode the value in a buffer automatically allocated by the decoder, instead of one user-provided.

D0200S

Message Format

D0200S: Ill formed entity: entity name

Message Cause

The EXTENDED-XER decoder encountered an entity definition that is syntactically incorrect.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName &#x1;">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0200S: Ill formed entity: 'myName' at line 3 position 12.

Possible Solution

Check the encoding application for errors.


D0202S

Message Format

D0201S: Entity does not contain well-formed XML

Message Cause

The EXTENDED-XER decoder detected that an entity's start-tags and end-tags do not match. This error is detected during entity reference processing.

Possible Solution

Check the encoding application for errors.


D0203S

Message Format

D0203S: Illegal DTD

Message Cause

The EXTENDED-XER decoder encountered an incorrect DTD construct.

Possible Solution

Check the encoding application for errors.


D0204S

Message Format

D0204S: Duplicate DTD

Message Cause

The EXTENDED-XER decoder encountered more than one document type definition in a single document.

Possible Solution

Check the encoding application for errors.


D0205S

Message Format

D0205S: Invalid notation definition

Message Cause

The EXTENDED-XER decoder detected a syntax error in a notation definition (in the document type definition).

Possible Solution

Check the encoding application for errors.


D0206S

Message Format

D0206S: Invalid character in a name: name

Message Cause

The EXTENDED-XER decoder encountered an illegal character in a name, such as a tag or attribute name, in the input document.

Possible Solution

Check the encoding application for errors.


D0207S

Message Format

D0207S: UTF8 continuation byte without start byte in a name: name

Message Cause

The EXTENDED-XER decoder detected a UTF-8 continuation byte in a name (such as a tag or attribute name) without a preceding start byte in the input document. This is a violation of the UTF-8 encoding rules.

Possible Solution

Check the encoding application for errors.


D0208S

Message Format

D0208S: Unfinished UTF8 multi-byte sequence in a name: name

Message Cause

The EXTENDED-XER decoder detected an unfinished UTF-8 multi-byte sequence in a name (such as a tag or attribute name) in the input document. This is a violation of the UTF-8 encoding rules.

Possible Solution

Check the encoding application for errors.


D0209S

Message Format

D0209S: Missing local part of a QName: name

Message Cause

The EXTENDED-XER decoder encountered a qualified name (such as a tag or attribute name) that has no local part, that is, a colon is the last character.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <last>Doe</last>
  <middle>N/A</middle>
</S>

Message for Example

D0209S: Missing local part of a QName: 'first:'; check field #0 of PDU #1 'S' at line 7 position 4.

Possible Solution

Check the encoding application for errors.


D0210S

Message Format

D0210S: Missing prefix in a QName: name

Message Cause

The EXTENDED-XER decoder encountered a qualified name (such as a tag or attribute name) that has a colon as the first character.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<abc:S xmlns:abc="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <:first>&myName;</:first>
  <abc:last>Doe</abc:last>
  <abc:middle>N/A</abc:middle>
</abc:S>

Message for Example

D0210S: Missing prefix in a QName: ':first'; check field #0 of PDU #1 'S' at line 7 position 4.

Possible Solution

Check the encoding application for errors.


D0211S

Message Format

D0211S: Local part of a QName contain colon(s): name

Message Cause

The EXTENDED-XER decoder encountered a qualified name (such as a tag or attribute name) that has more than one colon in it.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<abc:S xmlns:abc="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <abc:first:second>&myName;</abc:first>
  <abc:last>Doe</abc:last>
  <abc:middle>N/A</abc:middle>
</abc:S>

Message for Example

D0211S: Local part of a QName contains a colon: 'abc:first:second'; check field #0 of PDU #1 'S' at line 7 position 4.

Possible Solution

Check the encoding application for errors.


D0212S

Message Format

D0212S: Namespace prefix defined twice: prefix

Message Cause

The EXTENDED-XER decoder encountered a tag that contains two namespace declaration attributes for the same prefix.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<abc:S xmlns:abc="http://www.example.org/data"  
          xmlns:abc="http://www.example.org/data/b"
          xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <abc:last>Doe</abc:last>
  <abc:middle>M</abc:middle>
</abc:S>

Message for Example

D0212S: Namespace prefix defined twice: 'abc' at line 7 position 43.

Possible Solution

Check the encoding application for errors.


D0213S

Message Format

D0213S: Default namespace defined twice

Message Cause

The EXTENDED-XER decoder encountered a tag that contains two namespace declaration attributes for the default namespace.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<abc xmlns="http://www.example.org/data"  
     xmlns="http://www.example.org/data/b"
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0213S: Default namespace defined twice at line 7 position 39.

Possible Solution

Check the encoding application for errors.


D0214S

Message Format

D0214S: XML tag expected

Message Cause

An XML tag was expected at the specified location but something else was found.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
  <!ENTITY myName "John">
]>

<S xmlns="http://www.example.org/data"  
     xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0214S: Expecting XML tag; check field #0 of PDU #1 'S' at line 8 position 4.

Possible Solution

Check the encoding application for errors.


D0215S

Message Format

D0215S: The named value is not recognized : value

Message Cause

The named value was not recognized and not found among the legal names defined in the specification.

Possible Solution

Check the encoding application for errors.


D0216S

Message Format

D0216S: A named value is forbidden for this type

Message Cause

Named values are not legal for this type because they are not specified in the description.

Possible Solution

Check the encoding application for errors.


D0217S

Message Format

D0217S: The BOOLEAN value is not recognized : value

Message Cause

The value of a BOOLEAN type is not in a valid format.

Possible Solution

Check the encoding application for errors.


D0218S

Message Format

D0218S: The name of attribute is repeated : name

Message Cause

The attribute was defined more than once.

Possible Solution

Check the encoding application for errors.


D0219S

Message Format

D0219S: The plus sign is forbidden without GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword

Message Cause

A "+" sign was encountered in an integer or real value without a preceding MODIFIED-ENCODINGS instruction.

Possible Solution

Check the encoding application for errors.


D0220S

Message Format

D0220S: Negative zero (-0) is forbidden without GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword

Message Cause

A '-0' value was encountered for an integer without a preceding MODIFIED-ENCODINGS instruction.

Possible Solution

Check the encoding application for errors.


D0221S

Message Format

D0221S: Leading zeros are forbidden without GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword

Message Cause

The decoder encountered leading zeros for an integer without a preceding MODIFIED-ENCODINGS instruction.

Possible Solution

Check the encoding application for errors.


D0222S

Message Format

D0222S: Whitespaces are found in BASE64 component of LIST value encoding

Message Cause

The decoder encountered "whitespaces" inside a BASE64 encoding line with the LIST instruction set.

Possible Solution

Check the encoding application for errors.


D0223S

Message Format

D0223S: Too many named values for BIT STRING : number

Message Cause

The number of named bits exceeds the total number of names; they are probably repeated in the encoding.

Possible Solution

Check the encoding application for errors.


D0224S

Message Format

D0224S: Incorrect sequence of octets in BASE64 encodings

Message Cause

The decoder encountered an incorrectly encoded BASE64 encoding. Illegal characters or inappropriate lengths were found.

Possible Solution

Check the encoding application for errors.


D0225S

Message Format

D0225S: Unexpected character in the attribute encoding

Message Cause

An unexpected character was encountered in the attribute encoding.

Possible Solution

Check the encoding application for errors.


D0227S

Message Format

D0227S: The length of time value is too long

Message Cause

The encoding length for a time value is too long or the value was encoded incorrectly.

Possible Solution

Check the encoding application for errors.


D0228S

Message Format

D0228S: Value of the 'nil' attribute is not either true/false or 1/0

Message Cause

The decoder found an invalid value for the nil attribute. The legal values for nil are true/false or 1/0.

Possible Solution

Check the encoding application for errors.


D0229S

Message Format

D0229S: Unknown attribute : name

Message Cause

An unknown attribute was encountered.

Possible Solution

Check the encoding application for errors.


D0230S

Message Format

E0230S: Invalid URI value encountered : value

Message Cause

An invalid URI value was encountered when encoding an ANY-ATTRIBUTES construct.

Possible Solution

Check and correct the encoded value.


D0231S

Message Format

E0231S: Wrong URI value encountered : value

Message Cause

A syntactically incorrect URI value was encountered.

Possible Solution

Check and correct the encoded value.


D0232S

Message Format

E0232S: Wrong prefix value encountered : value

Message Cause

A syntactically incorrect prefix value was encountered.

Possible Solution

Check the encoding application for errors.


D0233S

Message Format

E0233S: Wrong unprefixed name encountered : name

Message Cause

A syntactically incorrect unprefixed name was encountered.

Possible Solution

Check and correct the encoded value.


D0234S

Message Format

E0234S: Size constraint on sequence of embedded values violated; number of components =

Message Cause

The number of values embedded in a sequence does not satisfy the restriction in ITU-T Rec. X.693 | ISO/IEC 8825-4, clause 25.

Possible Solution

Check and correct the encoded value.


D0235S

Message Format

E0235S: The name of the alternative of the enclosed [USE-UNION]CHOICE to be encoded is in conflict with the name of alternative of the enclosing [USE-TYPE] CHOICE

Message Cause

The alternate name of a CHOICE with USE-UNION applied, to be encoded as a type attribute, conflicts with the alternate name of the enclosing CHOICE with USE-TYPE applied.

Example

Module-E0235S DEFINITIONS 
XER INSTRUCTIONS AUTOMATIC TAGS ::=
BEGIN

VS ::= VisibleString
I ::= INTEGER

Ch1 ::= [USE-TYPE] CHOICE {
        a1 BOOLEAN,
        a2 [USE-UNION] CHOICE {
                z1 [NAME AS "z1"] VS,
                a1 [NAME AS "a1"] I
        }
}
ch1 Ch1 ::=  a2: a1: 1

Ch2 ::= [USE-TYPE] CHOICE {
        a1 BOOLEAN,
        a2 [USE-UNION] CHOICE {
                z1 [NAME AS "z1"] VS,
                a2 [NAME AS "a2"] I
        }
}
ch2 Ch2 ::=  a2: a2: 1

Ch3 ::= [USE-TYPE] CHOICE {
        a1 [USE-UNION] CHOICE {
                z1 [NAME AS "z1"] I,
                z2 [NAME AS "z2"] VS
        },
        a2 [USE-UNION] CHOICE {
                z1 [NAME AS "z1"] VS,
                z2 [NAME AS "z2"] I
        }
}
ch3 Ch3 ::=  a2: z2: 1

ENCODING-CONTROL XER
    GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END

Message(s) for Example

E0235S: Name of alternative of the enclosed [USE-UNION]CHOICE to be encoded is in conflict with the name of alternative of the enclosing [USE-TYPE] CHOICE : 'a1'; check PDU #1 'Ch1'.
E0235S: Name of alternative of the enclosed [USE-UNION]CHOICE to be encoded is in conflict with the name of alternative of the enclosing [USE-TYPE] CHOICE : 'a2'; check PDU #2 'Ch2'.
E0235S: Name of alternative of the enclosed [USE-UNION]CHOICE to be encoded is in conflict with the name of alternative of the enclosing [USE-TYPE] CHOICE : 'z2'; check PDU #3 'Ch3'.

Possible Solution

Check and correct the E-XER specification or the encoded value.


D0236S

Message Format

E0236S: An encoded value with DEFAULT-FOR-EMPTY instruction applied should not be empty

Message Cause

The E-XER encoder encountered inconsistent values for data in the input. The input value was encoded as empty but does not match the corresponding value from the DEFAULT-FOR-EMPTY instruction. In the example below, the empty string for the Telephone PDU should not be passed to the encoder since it is not equal to undef.

Example

Module-E0236S DEFINITIONS 
XER INSTRUCTIONS ::= BEGIN

  Telephone ::= [DEFAULT-FOR-EMPTY AS "undef"]    
                VisibleString
  
  t Telephone ::= ""

ENCODING-CONTROL XER
    GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END

Message for Example

E0236S: The encoded value with DEFAULT-FOR-EMPTY instruction applied should not be empty; check PDU #1 'Telephone'.

Possible Solution

Check and correct the E-XER specification or the pre-encoded value.


D0237S

Message Format

E0237S: Encoding of list item should not be empty

Message Cause

The E-XER encoder encountered inconsistent values for data in the input. A pre-encoded value contains a list item that produces an empty encoding. The value of a list item must not be encoded into an empty encoding according to the ASN.1 standard. (ITU-T Rec. X.693 | ISO/IEC 8825-4, clause 27.2.2).

Possible Solution

Check and correct the E-XER specification or the pre-encoded value.


D0238S

Message Format

E0238S: Whitespaces are not allowed in LIST value encoding

Message Cause

The E-XER encoder encountered inconsistent values for data in the input. A pre-encoded value contains a list item that produces an encoding with "whitespaces". (ITU-T Rec. X.693 | ISO/IEC 8825-4, clause 27.2.2).

Possible Solution

Check and correct the encoded value.


D0239S

Message Format

E0239S: Sequence of ordered values indicates unknown or absent field to be encoded

Message Cause

A missing field or one that does not belong to the sequence for which it is listed was encountered in the encoding list.

Possible Solution

Check and correct the encoded value.


D0240S

Message Format

E0240S: Size constraint on sequence of ordered values violated; number of components = num

Message Cause

The number of values in the list that sets the encoding order of sequence fields does not satisfy an applied size constraint (ref: ITU-T Rec. X.693 | ISO/IEC 8825-4, clause 36).

Possible Solution

Check and correct the encoded value.


D0241S

Message Format

D0241S: EmptyElementReal is forbidden with GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword applied

Message Cause

An XMLSpecialRealValue in the form of an empty-tag was encountered with the MODIFIED-ENCODINGS instruction applied.

Possible Solution

Check the encoding application for errors.


D0242S | E0242S

Message Format

x0242S: Exponential notation is forbidden if DECIMAL instruction is applied

Message Cause

The exponential representation of REAL is forbidden when the DECIMAL instruction is applied.

Possible Solution

Check and correct the encoded value or check the encoding application for errors.


D0243S

Message Format

E0243S: Negative zero (-0) is forbidden if DECIMAL instruction is applied

Message Cause

The signed representation of zero (-0) is forbidden when the DECIMAL instruction is applied.

Possible Solution

Check and correct the encoded value.


D0244S | E0244S

Message Format

x0244S: Plus/minus infinity and not-a-number are forbidden if DECIMAL encoding instruction is applied

Message Cause

REAL representations of plus or minus infinity and not-a-number (NaN) are forbidden when the DECIMAL instruction is applied.

Possible Solution

Check and correct the encoded value or check the encoding application for errors.


D0245E

Message Format

D0245E: Leading zeros are forbidden in exponent if GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword is not applied

Message Cause

A REAL representation with leading zeros in the exponent is forbidden when the MODIFIED-ENCODING instruction is not applied.

Possible Solution

Check the encoding application for errors.


D0246S

Message Format

E0246S: Duplicate values are present in the sequence of ordered values : value

Message Cause

The encoder encountered two identical values in a sequence that sets the number order of the encoded fields.

Possible Solution

Check and correct the encoded value.


D0247S

Message Format

E0247S: Value does not conform to 'AnyAttributeFormat' : value

Message Cause

This message occurs when an encoded XML attribute contained in a pre-encoded value does not conform to the ANY-ATTRIBUTE format.

    Possible causes
  • Absent attribute name
  • Absent "=" sign
  • Absent opening quote
  • Absent matching closing quote
  • Presence of non-whitespace characters after the closing quote

Possible Solution

Check and correct the encoded value.


D0248S

Message Format

E0248S: XML name expected

Message Cause

The EXTENDED-XER decoder expected an XML name but encountered something else.

Example

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE S [
  <!ENTITY "John">
]>

<S xmlns="http://www.example.org/data" 
   xmlns:asn1="urn:oid:2.1.5.2.0.1">
  <first>&myName;</first>
  <last>Doe</last>
  <middle>M</middle>
</S>

Message for Example

D0248S: XML name expected at line 3 position 12.
(The entity name is missing from the entity definition.)

Possible Solution

Check the encoding application for errors.


D0249S

Message Format

E0249S: The value of the character string type with a WHITESPACE COLLAPSE instruction applied should not contain leading or trailing spaces or multiple adjacent spaces

Message Cause

The EXTENDED-XER encoder encountered a character string type value with WHITESPACE COLLAPSE applied that contains leading, trailing, or multiple adjacent spaces.

Possible Solution

Check and correct the pre-encoded value.


D0250S

Message Format

D0250S: Illegal character in the encoding: character

Message Cause

The EXTENDED-XER decoder encountered a character that is forbidden for the type being decoded.

Possible Solution

Check the encoding application for errors.


D0251S

Message Format

D0251S: A nil identification attribute is not allowed for this type : type

Message Cause

The EXTENDED-XER decoder encountered a nil attribute in the tag of a type without the USE-NIL instruction applied.

Possible Solution

Check the encoding application for errors.


D0252S

Message Format

D0252S: A type identification attribute with an unexpected value is found : type

Message Cause

The EXTENDED-XER decoder encountered an identification attribute value that does not match any USE-UNION choice alternative.

Possible Solution

Check the encoding application for errors.


D0253S

Message Format

D0253S: The prefix 'xml' cannot be bound to any namespace other than XML namespace; no other prefix may be bound to this namespace: prefix

Message Cause

The EXTENDED-XER decoder encountered an XML namespace prefix definition attribute that attempts to define the "xml" prefix. The "xml" namespace prefix is by definition bound to the XML namespace (see www.w3.org/XML/1998/namespace) and cannot be bound to any other namespace. Also, the same error is returned if an XML namespace prefix definition attribute attempts to bind the XML namespace to any other prefix.

Possible Solution

Check the encoding application for errors.


D0254S | E0254S

Message Format

x0254S: Compression/decompression code not linked or initialized

Message Cause

There is an attempt to use compression functionality but either the -compress option was not used during ASN.1 compilation or the custom compression codecs are not installed.

Possible Solution

Either use the -compress ASN.1 compiler option or install custom compression codecs. Alternatively, disable the USE_COMPRESSION runtime flag.


D0255S | E0255S

Message Format

x0255S: Encoding compression/decompression error, code number

Message Cause

The compression/decompression function, either one Zlib-based from the OSS SOED library or a custom codec, returned an error. A negative error code number is given in the error message body.

Possible Solution

Refer to the Zlib documentation for the list of Zlib error codes. Check your custom codec if custom compression is used. You may need to install a custom compressed-size-estimation function.


D0256S

Message Format

E0256S: Value does not conform to the 'AnyElementFormat' : value

Message Cause

The EXTENDED-XER encoder found that the value of a type with XER ANY-ELEMENT applied is not a syntactically correct XML element, as defined in W3C XML 1.0 and W3C XML Namespaces.

Possible Solution

Make sure that the value of the type passed to the encoder contains a complete XML element that is syntactically correct.


R0257E | R0257W

Message Format

R0257E: Applications built with the TRIAL version of the OSS ASN.1 Tools can be executed only on the machine on which you run the OSS ASN.1 compiler.

Message Cause

You are running an application built with a TRIAL version of the OSS ASN.1 Tools on a different machine from that used to generate the files used in your application. TRIAL versions are restricted to run only on the same machine on which the ASN.1 Compiler was run.

Possible Solution

Execute your application on the same machine on which you ran the ASN.1 Compiler. If you need a trial that will compile and run on different machines, contact info@oss.com.

NOTE: Prior to version 10.0 of the ASN.1/C Tools and version 6.0 of the ASN.1/C++ Tools, the following warning message was issued instead, whenever an application built with a trial license was run.

Message Format

R0257W: This is a TRIAL version of the OSS ASN.1 Tools. Applications built with this software may only execute on the machine on which you run the ASN.1 compiler and only for the time period of the trial.

Message Cause

This message warns you that you are running an application built with a TRIAL version of the OSS ASN.1 Tools. TRIAL versions are restricted to run only on the same machine on which the ASN.1 Compiler was run.


D0258E

Message Format

D0258E: Fragments within a PER encoding are not grouped correctly

Message Cause

The input encoding is fragmented incorrectly. Refer to section 11.9.3.8 in the X.691 standard for details.

Possible solutions

  • Check the sending application for errors.
  • Check that the correct PDU number was passed to the decoder; it must correspond to the data structure that you want to decode.
  • To disable this error, turn off the STRICT_ENCODING_DECODING_RULES flag using the ossSetFlags() function.

D0259S

Message Format

E0259S: User application reported an error, error code: value

Message Cause

A user-defined function such as an XER encoding formatter or some other callback function has reported an error (a positive return code). The encoding process was terminated.

Possible solution

Verify that the value to be encoded is wrong concerning the application-specific requirements tracked by the callback function and that the error is expected. If the value is valid and the error is unexpected then the callback function needs repair.


D0260S

Message Format

D0260E: Length of encoded data of ContentsConstraint is 0.

Message Cause

The decoder could not continue decoding a contents constraint because it has a zero length. A proper contents constraint encoding is at least 1-byte in length.

Possible Solution

Check the encoding application for errors.


D0261S

Message Format

D0261E: Character code too long.

Message Cause

The decoder could not convert a UTF8String character to a UCS-4 (UCS-2) string character because the UTF8String character code is too big to fit in the local C-representation.

Possible Solutions

  • Design a filtering mechanism to remove such characters before they get to the encoder/decoder.
  • Consider using compiler directives to change the C-representation.

D0262S

Message Format

D0262S: Encoding of a TIME type consists of more than one fragment

Message Cause

The input time type (UTCTime, GeneralizedTime) PER encoding is fragmented. This error is reported by the LED runtime library.

Possible Solution

Turn off the STRICT_ENCODING_DECODING runtime flag to suppress this error.


D0263E

Message Format

D0263E: The padding bits are not zero.

Message Cause

The decoder found that the padding bits of a PER-Aligned encoding are not zero.

Possible Solutions

  • Check the encoding application for errors.
  • Do not specify the STRICT_ENCODING_DECODING_RULES runtime flag so the decoder does not check that padding bits are zero.

Example

M DEFINITIONS ::= BEGIN
 I ::= INTEGER (0..65599)
 E ::= ENUMERATED {
    red(0),
    green(1),
    blue(2)
 }
S ::= SEQUENCE {
    a INTEGER,
    b BOOLEAN,
      ...
 }
END

With an incorrect encoding for the I PDU: 48FDE8

value I ::=  65000
  --length: <.01>
  --padding: <001000>
  --contents: <.11111101 .11101000>

I PDU Message

D0263E: The padding bits after the length encoding are not zero; check PDU #1 'I'.

Or with an incorrect encoding for the E PDU: 4F

value E ::=  green
  --contents: <.01>
  --PDU padding: <111111>

E PDU Message

D0263E: The padding bits after the PDU are not zero; check PDU #2.

Or with an incorrect encoding for the S PDU: 7F010100

value S ::=
{
  --extension flag: <.0>
  a 1,
    --padding: <1111111>
    --length: <.00000001>
    --contents: <.00000001>
  b FALSE
    --contents: <.0>
}
--PDU padding: <0000000>

S PDU Message

D0263E: The padding bits are not zero; check the data before field 'a' (type: INTEGER) of PDU #3 'S'.

D0325E

Message Format

D0325E: None of CHOICE type's alternatives fits the encoded value.

Message Cause

The E-XER decoder detected an erroneous element of [USE-UNION] CHOICE and the element value fits none of the alternatives.

Example

M DEFINITIONS XER INSTRUCTIONS ::= BEGIN
    U ::= [USE-UNION] CHOICE {
        i INTEGER (0..20),
        b BOOLEAN
    }

ENCODING-CONTROL XER
   GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END

With an incorrect encoding for the U PDU:

<U>21</U>

Message for Example

D0325E: The encoded value fits none of the alternatives of CHOICE type; check PDU #1 'U' at line 1 position 8 (encoding position: 8.0).

Possible Solution

Check the encoding application for errors.


E0326S | D0326S | V0326S

Message Format

x0326E: PropertySettings constraint violated

Message Cause

The encoder, decoder, or constraint checker detected a property settings constraint violation in a time type value.

Possible Solution

Change the time value to conform to the specified constraint, or disable runtime constraint checking by using the ossSetFlags() function to set the NOCONSTRAIN runtime flag. In ASN.1/Java, call the disableEncoderConstraints() or disableDecoderConstraints() method.


E0327S | D0327S | V0327S

Message Format

x0327E: Duration range constraint violated, value

Message Cause

The encoder, decoder, or constraint checker detected a duration range constraint violation in a time type value.

Possible Solution

Change the time value to conform to the specified constraint, or disable runtime constraint checking by using the ossSetFlags() function to set the NOCONSTRAIN runtime flag. In ASN.1/Java, call the disableEncoderConstraints() or disableDecoderConstraints() method.


E0328S | D0328S | V0328S

Message Format

x0328E: TimePoint range constraint violated, value

Message Cause

The encoder, decoder, or constraint checker detected a time point range constraint violation in a time type value.

Possible Solution

Change the time value to conform to the specified constraint, or disable runtime constraint checking by using the ossSetFlags() function to set the NOCONSTRAIN runtime flag. In ASN.1/Java, call the disableEncoderConstraints() or disableDecoderConstraints() method.


E0329S | D0329S | V0329S

Message Format

x0329E: Recurrence range constraint violated, number of recurrences

Message Cause

The encoder, decoder, or constraint checker detected a recurrence range constraint violation in a time type value.

Possible Solution

Change the time value to conform to the specified constraint, or disable runtime constraint checking by using the ossSetFlags() function to set the NOCONSTRAIN runtime flag. In ASN.1/Java, call the disableEncoderConstraints() or disableDecoderConstraints() method.


E0330E | D0330E | V0330S

Message Format

x0330E: Invalid canonical form of time value: 'message'

Message Cause

The canonical encoding XER decoder detected a standards violation in the input encoding.

Messages for Example

Possible error messages are listed below along with the clause in X.693 that was violated.

"full stops should be used as decimal signs", clause 9.13 a) is violated.

"the minutes digits for all time difference components that are an integral number of hours shall be removed", clause 9.13 b) is violated.

"the time difference component of the end point should be removed if it is the same as the time difference component of start point", clause 9.13 c) is violated.

"all zero time components except the least significant time component of the duration value should have been removed", clause 9.13 d) is violated.

Possible Solutions

  • Use the line number and position in the diagnostic error message to find the exact location of the error in the XER encoding and fix the encoding application accordingly.
  • Switch to Basic XER if your application does not require the production of unique encodings.

D0331E

Message Format

D0331E: The name of the root element does not match the name in the DTD: tag name

Message Cause

The decoder found a root element name that does not match the name in the document type declaration.

Possible Solution

Check the encoding application for errors.


D0333E

Message Format

D0333E: Unsupported XML encoding format was detected. Please contact OSS Nokalva, support@oss.com, if you need support for this format: unknown format

Message Cause

The decoder found a XML declaration with an unsupported XML encoding format.

Possible Solution

Convert the instance to UTF-8 encoding and either change the XML declaration accordingly or specify the OSS_RELAXED encoder/decoder runtime flag so the encoding declaration is ignored.


D0334E | E0334E

Message Format

x0334E: Invalid OID internationalized resource identifier value: [foundValue]; check ...

Message Cause

The encoder/decoder found an empty ArcIdentifier in an OID-IRI/RELATIVE-OID-IRI value, for example:

  • ""
  • "/"
  • "/ISO/Registration-Authority//19785.CBEFF"
  • "/ISO/Registration-Authority/"

Possible Solution

Check the encoding application for errors.


V0334E

Message Format

V0334E: Element of SET OF / SEQUENCE OF must not be null

Message Cause

A SET OF or SEQUENCE OF value contains an element that is null. Elements of SET OF and SEQUENCE OF cannot be null references.

Message for Example

"Validation failed with a code of com.oss.asn1.ValidateFailedException: V0334E: Element of SET OF / SEQUENCE OF must not be null: element #1 is null; check PDU 'SequenceOfSeqType'"

Possible Solution

Assign a proper (non-null) object reference to the element that is null.


D0335E | E0335E

Message Format

x0335E: Invalid arc in the OID internationalized resource identifier value: [foundArc]; check ...

Message Cause

The encoder/decoder detected one of the following problems:

  • The FirstArcIdentifier is invalid, for example: "/iso/Registration-Authority/19785.CBEFF"
  • The SecondArcIdentifier is invalid, for example: "/ISO/RegistrationAuthority/19785.CBEFF"
  • The ArcIdentifier violates the X.660 (Clause 7.2) standard's restrictions, for example:
    • "/ISO/Registration-Authority/third arc"
    • /0/01"
    • "/0/40"

Possible Solution

Check the encoding application for errors.


V0335E

Message Format

V0335E: Value for a component of SET / SEQUENCE / CHOICE must not be null

Message Cause

A SET or SEQUENCE is missing a mandatory field, or a CHOICE alternative is null.

Message for Example

"Validation failed with a code of com.oss.asn1.ValidateFailedException: V0335E: Value for a component of SET / SEQUENCE / CHOICE must not be null: a; check field 'a' (type: INTEGER) of PDU 'SeqType'"

Possible Solution

Assign values for all SET and SEQUENCE mandatory fields.
Assign a non-null object reference as a CHOICE value.


D0336S

Message Format

D0336S: Non-PER encoding rules were requested for ossPrintPER.

Message Cause

ossPrintPER detected that an invalid set of encoding rules was specified.

Possible Solution

Use the ossSetEncodingRules() function to set the proper encoding rules. Pass one of the following literals as the second argument: OSS_PER_ALIGNED, OSS_PER_UNALIGNED.


R0337S

Message Format

R0337S: Licensing error. Please contact OSS Nokalva, Inc.

Message Cause

The check on your license failed.

Possible Solution

Contact info@oss.com for detailed information.


D0338S | E0338S

Message Format

x0338S: This version of the OER encoder/decoder does not support 'requested feature'.

Message Cause

Your version of the runtime library does not support the requested feature.

Example Message

E0338S: This version of the OER encoder/decoder does not support 'ContentsConstraint with ENCODED BY'.

Possible Solution

Contact OSS Nokalva, support@oss.com, if you require this feature.


D0339S | E0339S

Message Format

x0339S: Cannot close input file.

Message Cause

The OSS memory manager cannot close the input file.

Example Message

E0339S: Cannot close input file.

Possible Solution

Check the permissions on the work and temporary directories.


D0340S | E0340S

Message Format

x0340S: Cannot open output file.

Message Cause

The OSS memory manager cannot open the output file.

Example Message

E0340S: Cannot open output file.

Possible Solution

Check the permissions on the work and temporary directories.


D0341S | E0341S

Message Format

x0341S: Cannot close output file.

Message Cause

The OSS memory manager cannot close the output file.

Example Message

E0341S: Cannot close output file.

Possible Solution

Check the permissions on the work and temporary directories.


D0342S | E0342S

Message Format

x0342S: Error writing to file.

Message Cause

The OSS memory manager detected a file write error.

Example Message

E0342S: Error writing to file.

Possible Solution

Check the permissions on the work and temporary directories.


D0342S | E0343S

Message Format

x0343S: Error reading from file.

Message Cause

The OSS memory manager detected a file read error.

Example Message

E0343S: Error reading from file.

Possible Solution

Check the permissions on the work and temporary directories.


D0344S | E0344S

Message Format

x0344S: Cannot open temporary file.

Message Cause

The OSS memory manager cannot open a temporary file.

Example Message

E0344S: Cannot open temporary file.

Possible Solution

Check the permissions on the work and temporary directories.


D0345S | E0345S

Message Format

x0345S: The part of deferred value is in the initial buffer.

Message Cause

The OSS memory manager detected part of the deferred value in the initial buffer.

Example Message

D0345S: The part of deferred value is in the initial buffer.

Possible Solution

Check the application for errors.


D0346S | E0346S

Message Format

x0346S: Incorrect deferred value in the initial buffer.

Message Cause

The OSS memory manager detected an incorrect deferred value in the initial buffer.

Example Message

D0346S: Incorrect deferred value in the initial buffer.

Possible Solution

Check the application for errors.


D0347S | E0347S

Message Format

x0347S: Error writing to socket.

Message Cause

The OSS memory manager detected a socket write error.

Example Message

E0347S: Error writing to socket.

Possible Solution

Check the application for errors.


D0348S | E0348S

Message Format

x0348S: Error reading from socket.

Message Cause

The OSS memory manager detected a socket read error.

Example Message

D0348S: Error reading from socket.

Possible Solution

Check the application for errors.


D0349S | E0349S

Message Format

x0349S: Cannot load socket DLL.

Message Cause

The OSS memory manager could not access the socket dynamic library.

Example Message

D0349S: Cannot load socket DLL.

Possible Solution

Make sure that there is a socket DLL in your executable search path.


D0350S | E0350S

Message Format

x0350S: Cannot get a procedure address.

Message Cause

The socket DLL does not provide the required functions.

Example Message

D0350S: Cannot get a procedure address.

Possible Solution

Check that the correct socket DLL is used.


D0351S | E0351S

Message Format

x0351S: Invalid socket handle.

Message Cause

The OSS memory manager detected an invalid socket handle.

Example Message

D0351S: Invalid socket handle.

Possible Solution

Check the application for errors.


D0352S | E0352S

Message Format

x0352S: Timeout expired while writing to the socket.

Message Cause

The timeout expired while writing to the socket.

Example Message

E0352S: Timeout expired while writing to the socket.

Possible Solution

Check the application for errors.


D0353S | E0353S

Message Format

x0353S: Timeout expired while reading from the socket.

Message Cause

The timeout expired while reading from the socket.

Example Message

D0353S: Timeout expired while reading from the socket.

Possible Solution

Check the application for errors.


D0354S | E0354S

Message Format

x0354S: Unknown marked object.

Message Cause

The OSS memory manager detected an unknown marked memory object.

Example Message

D0354S: Unknown marked object.

Possible Solution

Check the application for errors.


D0355S

Message Format

D0355S: The length of the containing BIT/OCTET STRING does not match the length of the encoding it contains. Either the encoding is too short or it ends with unwanted pad bits.

Message Cause

The decoder found that the container length does not match the length of the encoding it contains.

Example Message

D0355S: The length of the containing BIT/OCTET STRING does not match the length of the encoding it contains. Either the encoding is too short or it ends with unwanted pad bits.

Possible Solution

Check the encoding application for errors.


D0356S

Message Format

D0356S: Value of DURATION misencoded.

Message Cause

The decoder encountered an invalid encoding of a DURATION type. Following are possible causes:

  • The week component is present and the year, month, day, hour, minute, or second component is also present.
  • All components are absent or only the fractional part is present.
  • The zero time component is not the last one specified.

Example Message

D0356S: Value of DURATION misencoded.

Possible Solution

Check the encoding application for errors.


D0357S

Message Format

0357S: The XER/CXER/E-XER/JSON decoders do not support ossPartialDecode().

Message Cause

The ossPartialDecode() function was called while the TOED XER/CXER/E-XER/JSON encoding rules were in use.

Example Message

0357S: The XER/CXER/E-XER/JSON decoders do not support ossPartialDecode().

Possible Solution

Do not use the ossPartialDecode() function with the TOED XER/CXER/E-XER/JSON encoding rules.


D0358S

Message Format

0358S: Partial decoding stopped by user callback return code #N.

Message Cause

The code returned by the user callback function differs from OSS_CONTINUE_DECODING and OSS_SKIP_TO_PDU_END. It immediately terminates the decoding.

Example Message

0358S: Partial decoding stopped by user callback return code 1025.

Possible Solution

If the decoding must not be immediately terminated, consider the OSS_SKIP_TO_PDU_END or OSS_CONTINUE_DECODING return code.


D0359S

Message Format

0359S: ossDecode() is disabled by the -partialDecodeOnly option.

Message Cause

The ossDecode() function was called for a specification that was ASN.1-compiled with the -partialDecodeOnly option.

Example Message

0359S: ossDecode() is disabled by the -partialDecodeOnly option.

Possible Solution

Do not use the ossDecode() function or do not specify the -partialDecodeOnly option.


D0360S | E0360S

Message Format

x0360S: Encoding/decoding is supported for PDUs only. Consider using the OSS.PDU directive to enable encoding/decoding of this type.

Message Cause

The Java Tools Time-Optimized Encoder/Decoder (TOED) is attempting to encode or decode ASN.1 types that are not PDUs. Only ASN.1 types that are considered PDUs can be encoded or decoded.

Example Message

D0356S: Value of DURATION misencoded.

Possible Solution

Apply the --<OSS.PDU [absoluteReference]>-- directive to the ASN.1 type. Caution: if you apply the OSS.PDU directive without the absoluteReference parameter, all ASN.1 types are marked as PDUs and a large amount of code is generated.


D0361S

Message Format

D0361S: Unknown token found, expecting 'token1'.

Message Cause

An unexpected token was encountered.

Example Message

D0361S: Unknown token found, expecting'}' or '"'.

D0361S: Unknown token found, expecting '{'.

Possible Solution

Check the JSON encoding and add the expected token.


D0362S

Message Format

D0362S: Unknown member name: 'name'.

Message Cause

An unknown ASN.1 component name or unexpected standard member name ("length", "value", etc.) was encountered in the input JSON encoding.

Example Message

D0362S: Unknown member name: 'givenName'.

Possible Solution

Check the JSON encoding and remove or replace the unknown member name.


D0363S

Message Format

D0363S: Length of the item is too long: item.

Message Cause

The JSON decoder found that the length of one of the following tokens exceeds the implementation limit of 255 bytes:

  • Member name
  • Object identifier node
  • REAL value
  • UTCTime value
  • GeneralizedTime value

Example Message

D0363S: Length of the item is too long: alternative name.

D0363S: Length of the item is too long: ENUMERATED name.

D0363S: Length of the item is too long: OBJECT IDENTIFIER.

Possible Solution

Change the ASN.1 specification to fit the implementation restriction or contact Technical Support ‹support@oss.com› if you need support for longer tokens.


D0364S

Message Format

D03654S: Invalid encoding of item.

Message Cause

The JSON decoder encountered an invalid encoding of 'item'.

Example Message

D03654S: Invalid encoding of hexadecimal string.

D03645S: Invalid encoding of JSON number.

D03645S: Invalid encoding of BIT STRING.

Possible Solution

Check the encoding application for errors.


D0365S

Message Format

D0365S: Invalid ENUMERATED identifier: 'name'.

Message Cause

The enumerator with the specified name does not exist in the corresponding ENUMERATED type.

Example Message

D0365S: Invalid ENUMERATED identifier: 'x'.

Possible Solution

Check the encoding application for errors.


D0366S

Message Format

D0366S: message.

Message Cause

The decoder encountered some inconsistency in the input JSON encoding.

Example Message

D0366S: Unknown token.

D0366S: Illegal surrogate pair.

D0366S: Illegal escape sequence.

Possible Solution

Check the encoding application for errors.


D0367S

Message Format

D0367S: Bad Unicode value: {value}.

Message Cause

The JSON encoder encountered an invalid Unicode character value.

Example Message

D0367S: Bad Unicode value: {0,0,255,255}.

Possible Solution

Check the input value.



Lean Runtime-Specific Messages

D1001S

Message Format

D1001S
or
D1001S: Requested type is not linked or not supported by PER decoder

Message Cause

The data type is not supported by the Lean PER decoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


E1002S

Message Format

E1002S
or
E1002S: Requested type is not linked or not supported by PER encoder

Message Cause

The data type is not supported by the Lean PER encoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


D1003S

Message Format

D1003S
or
D1003S: Requested type is not linked or not supported by BER decoder

Message Cause

The data type is not supported by the Lean BER decoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


E1004S

Message Format

E1004S
or
E1004S: Requested type is not linked or not supported by BER encoder

Message Cause

The data type is not supported by the Lean BER encoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


D1005S

Message Format

D1005S
or
D1005S: BER decoder not linked or initialized

Message Cause

The requested BER decoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –ber or -der option.


E1006S

Message Format

E1006S
or
E1006S: BER encoder not linked or initialized

Message Cause

The requested BER encoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –ber or -der option.


D1007S

Message Format

D1007S
or
D1007S: PER decoder not linked or initialized

Message Cause

The requested PER decoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –per or -uper option.


E1008S

Message Format

E1008S
or
E1008S: PER encoder not linked or initialized

Message Cause

The requested PER encoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –per or -uper option.


D1009S

Message Format

D1009S
or
D1009S: Requested type is not linked or not supported by XER decoder

Message Cause

The data type is not supported by the Lean XER decoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


E1010S

Message Format

E1010S
or
E1010S: Requested type is not linked or not supported by XER encoder

Message Cause

The data type is not supported by the Lean XER encoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


D1011S

Message Format

D1011S
or
D10011S: XER decoder not linked or initialized

Message Cause

The requested XER decoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –xer or -cxer option.


E1012S

Message Format

E1012S
or
E1012S: XER encoder not linked or initialized

Message Cause

The requested XER encoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –xer or -cxer option.


D1013S

Message Format

D1013S
or
D10013S: EXER decoder not linked or initialized

Message Cause

The requested E-XER decoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –exer option.


E1014S

Message Format

E1014S
or
E1014S: EXER encoder not linked or initialized

Message Cause

The requested E-XER encoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –exer option.


D1015S

Message Format

D1015S
or
D1015S: Requested type is not linked or not supported by EXER decoder

Message Cause

The data type is not supported by the Lean E-XER decoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


E1016S

Message Format

E1016S
or
E1016S: Requested type is not linked or not supported by EXER encoder

Message Cause

The data type is not supported by the Lean E-XER encoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


D1017S | E1017S

Message Format

x1017S
or
x1017S: Requested encoding rules not supported by the LEAN runtime

Message Cause

The requested encoding rules are not supported by the Lean runtime.

Possible Solution

Re-ASN.1-compile your input syntax with your choice of the -ber, -der, -per, -uper, -xer, -cxer, –exer, -oer, -coer, or -json encoding rules compiler option.


D1018S | E1018S

Message Format

x1018S
or
x1018S: Length of the OBJECT IDENTIFIER is greater than 16K or equals to zero

Message Cause

The Lean encoder/decoder found that the value of an OBJECT IDENTIFIER type violates length restrictions.

Possible Solution

Check the encoding application for errors.


D1019S

Message Format

E1016S
or
E1016S: Requested type is not linked or not supported by EXER encoder

Message Cause

The data type is not supported by the Lean E-XER encoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


E1020S

Message Format

E1020S
or
E1020S: Requested type is not linked or not supported by OER encoder

Message Cause

The Lean OER encoder does not support the ASN1.DeferDecoding directive.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


D1021S

Message Format

D1021S
or
D1021S: OER decoding rules not linked or initialized

Message Cause

The requested OER decoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –oer or -coer options.


E1022S

Message Format

D1022S
or
D1022S: OER encoding rules not linked or initialized

Message Cause

The requested OER encoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –oer or -coer option.


D1023S

Message Format

D1023S
or
D1023S: Requested type is not linked or not supported by JSON decoder

Message Cause

The data type is not supported by the Lean JSON decoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


E1024S

Message Format

E1024S
or
E1024S: Requested type is not linked or not supported by JSON encoder

Message Cause

The data type is not supported by the Lean JSON encoder.

Possible Solution

Remove the unsupported representation from the ASN.1 input.


D1025S

Message Format

D1025S
or
D1025S: JSON decoder not linked or initialized

Message Cause

The requested JSON decoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –json option.


E1026S

Message Format

E1026S
or
E1026S: JSON encoder not linked or initialized

Message Cause

The requested JSON encoder is not linked or initialized.

Possible Solution

Re-ASN.1-compile your input syntax with the –json option.


D1027S

Message Format

D1027S
or
D1027S: Unexpected token found

Message Cause

An unexpected token was encountered.

Possible Solution

Check the JSON encoding and add the expected token.


D1028S

Message Format

D1028S
or
D1028S: Illegal escape sequence

Message Cause

The decoder encountered an escape sequence that is not valid.

Possible Solution

Check the encoding application for errors.


D1029S

Message Format

D1029S
or
D1029S: Illegal surrogate pair

Message Cause

The decoder encountered a surrogate pair that is not valid.

Possible Solution

Check the encoding application for errors.


D1030S

Message Format

D1030S: Duplicated member name in [UNWRAPPED] CHOICE encoding.

Message Cause

The decoder encountered a duplicated member name in [UNWRAPPED] CHOICE encoding.

Possible Solution

Check the encoding application for errors.


D1031S

Message Format

D1031S: Unrecognized alternative of [UNWRAPPED] CHOICE.

Message Cause

The decoder failed to determine the alternative of [UNWRAPPED] CHOICE.

Possible Solution

Check the encoding application for errors.



This documentation applies to the latest versions of the OSS® ASN.1 Tools software.

Copyright © 2017 OSS Nokalva, Inc. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means electronic, mechanical, photocopying, recording or otherwise, without the prior permission of OSS Nokalva, Inc.
Every distributed copy of the OSS® ASN.1 Tools is associated with a specific license and related unique license number. That license determines, among other things, what functions of the OSS ASN.1 Tools are available to you.