We stand with Ukraine D0001S: Output buffer too small; total buffer size:
or
D0001S: Output buffer too small; total bytes requested:
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:
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: Output buffer too small; total buffer size:
or
E0001S: Output buffer too small; total bytes requested:
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.
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: Data type has not been implemented yet
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:
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: Data type has not been implemented yet
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.
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.
x0003S: PDU number not in range:
The encoder/decoder was passed a PDU identification number that is greater than the highest PDU number assigned by the ASN.1 compiler.
x0004S: Version number of control table differs from that of encoder/decoder
The encoder/decoder library file is incompatible with the ASN.1 compiler in use. The two components are of different versions.
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.
x0005S: Global data access serialization error
The encoder/decoder experienced a serialization error when modifying the OssGlobal structure or another global variable.
When using multiple simultaneous threads in your application, allocate and initialize a separate OssGlobal structure for each thread.
x0006S: Unexpected NULL pointer as argument to encoder/decoder
The encoder/decoder's third argument is NULL, when it should contain the input address.
x0007S: The files generated by the ASN.1 compiler are incompatible with the runtime library version.
This error can occur in any of these situations:
x0008S: Out of memory; bytes requested:
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.
Free up some system resources before using the encoder/decoder. Try the following suggestions:
E0009S: Out-of-range CHOICE selector:
In a PDU generated to represent a CHOICE, the encoder found that the value of the choice field exceeded the maximum allowed selector value.
D0009S: Out-of-range CHOICE selector:
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.
Confirm that the encoding and decoding applications use the same ASN.1 notation.
x0010S: Bad OBJECT IDENTIFIER: problematic sub-identifier number
The encoder/decoder found an OBJECT IDENTIFIER value that violates the ASN.1 standard. Any of the following input conditions could cause this error:
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: Unexpected NULL pointer in input
The encoder found a NULL pointered field in a PDU when the address of a value was expected.
Change the pointered field to hold the address of a valid value for the appropriate ASN.1 type.
This error can also occur when
x0012S: Out-of-range value in time type
All encoders and decoders.
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
Change the component value to fall within the range set by the ASN.1 standard.
x0013S: Time value must be in universal coordinated time format and must end with 'Z'
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.
Change the format of the violating time value to conform with the restrictions on DER-encoded time values in the ASN.1 standard.
x0014S: A memory-violation error occurred, signal number
The encoder/decoder received an error signal from the memory manager when trying to store some piece of data.
D0015E: Object identifier has too many subidentifiers:
The decoder encountered an OBJECT IDENTIFIER value with more than forty sub-identifiers, which is the maximum allowed.
Reduce the number of sub-identifiers in the OBJECT IDENTIFIER value.
x0016S: Size constraint exceeded, length of value = length
The BER/XER/E-XER/OER encoder/decoder or the constraint checker encountered inconsistent values in the input data.
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.
x0017E: Encoded object identifier value too long for local representation:
The encoder/decoder encountered an OBJECT IDENTIFIER value that is too large to fit in the local representation.
Use the OSS.ENCODED compiler directive to create a representation of the OBJECT IDENTIFIER type that can accommodate the large value.
D0018E: Tag needlessly long
The BER/DER decoder found a needlessly long tag encoding.
Specify the OSS_RELAXED encoder/decoder runtime flag to allow such long tags.
D0019E: Tag too long: tag
The BER/DER decoder found a tag encoding that occupies more than 14 encoded bits.
Reduce the value of the tag to be less than 16,383.
D0020E: Exponent needlessly long
The decoder found an exponent for a REAL type that has nine leading 1's or 0's.
Correct the faulty encoding or specify the OSS_RELAXED encoder/decoder runtime flag to allow such exponents.
D0021E: Exponent too long: exponent
The decoder found an exponent for a REAL type that is too large to fit in a platform-dependent representation of REAL types.
Use the OSS.DECIMAL compiler directive to choose a REAL type representation that can accommodate the limitations of your particular platform.
D0022E: Integer or enumerated value needlessly long
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.
D0023E: Integer or enumerated value too long: value
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.
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: Sub-identifier needlessly long
While decoding an OBJECT IDENTIFIER value, the decoder found a sub-identifier with seven leading 0-bits, which violates the ASN.1 standard.
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: Sub-identifier too long: value
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.
Use the OSS.OBJECTID or OSS.ENCODED compiler directive to create an OBJECT IDENTIFIER type representation that can handle larger sub-identifier values.
x0026S: Length too long: length
The encoder or decoder found that the length field of a data type was too long to fit in an unsigned long int.
D0027S: Size too long: size
While decoding, the decoder found a size field that exceeds the bounds set for a data type in your C-compiler limits.h file.
Change the representation of the size field.
D0028E: Non-standard EOC octets
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.
Check the encoding application for errors.
x0029E: Too many OPTIONAL fields:.
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.
x0030S: Unknown size
The encoder/decoder found a data item in the generated .c file whose size exceeds what the runtime version in use supports.
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: Inconsistent lengths
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.
Check the encoding application for errors.
D0032E: Too many extension additions:
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.
Reduce the number of extension additions.
D0033E: Tag mismatch or tag not expected: [foundTag] (expected tag [tag]); check field 'fieldName' (type: typeName) of PDU #n 'e'.
This error has three common causes:
Check the encoding application for errors.
D0034E: PDU number and input tags do not match:
The decoder found that the tags in the input encoding do not match the expected tags of the PDU to be decoded.
Check that the PDU number passed to the decoder conforms to the data structure to be decoded.
D0035E: The first octet is not in the range 0-7
The decoder found a BER/OER encoded BIT STRING type whose trailing bits do not end on an octet boundary.
Check the encoding application for errors.
x0036E: The first octet is not 0
The encoder/decoder found trailing bits from the last encoding that are improperly aligned on an octet boundary.
Check the encoding application for errors.
x0037E: Value misencoded or length wrong for value
The encoder/decoder found one of the following abnormalities:
D0038E: Expected digits in mantissa
The decoder found an encoding of a REAL type that lacks a mantissa value.
Check the encoding application for errors.
D0039E: Expected digits in exponent
The decoder found an encoding of a REAL type that lacks an exponent value.
Check the encoding application for errors.
D0040E: Invalid NR1 (real) encoding
The decoder found an encoding of a REAL type that violates the ISO 6093 NR1 format.
Check the encoding application for errors.
D0041E: Invalid NR2 (real) encoding
The decoder found an encoding of a REAL type that violates the ISO 6093 NR2 format.
Check the encoding application for errors.
D0042E: Invalid NR3 (real) encoding
The decoder found an encoding of a REAL type that violates the ISO 6093 NR3 format.
Check the encoding application for errors.
D0043E: REAL 0 with contents found
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.
Check the encoding application for errors.
D0044E: Reserved real encoding
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 (2021) for more details.
Change the encoding application to use an encoding format that is not reserved by the ASN.1 standard.
D0045E: Too many values in input; skipped
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.
Check the encoding application for errors.
D0046E: Found NULL embedded in null-terminated STRING
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.
Try using the UNBOUNDED representation; it allows any size string without needing a NULL to terminate it.
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: Tag not recognized: [foundTag]; check field 'fieldName' (type: typeName) of PDU #n 'pduname'.
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.
D0048E: Field repeated
The decoder found an encoding of a SET type that contains two or more values for the same type.
Check the encoding application for errors.
D0049E: Field omitted
The decoder could not find a mandatory SET or SEQUENCE component in its encoding.
Check the encoding application for errors.
D0050S: Expected EOC octets
The decoder found too few end-of-contents octets at the end of a SET OF or SEQUENCE OF type.
Check the encoding application for errors.
Found primitive encoding with indefinite length
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.
Check the encoding application for errors.
D0052S: Expected constructed type but found primitive
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.
Check the encoding application for errors.
D0053S: Expected primitive type but found constructed
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.
Check the encoding application for errors.
D0054S: PDU tag not recognized:
The decoder found an encoding of a PDU whose tag is not listed in the generated control-table or code file.
ossSetEncodingRules(world, OSS_PER_ALIGNED);
This error code is currently not in use.
D0056S: This error cannot happen; inform OSS, code = number
The decoder encountered an unknown exception error.
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: Decoder argument for length is negative; length = negative number
The user provided a pre-allocated output buffer for the decoder, but its specified length is negative.
D0058E: Expected tag, found EOC octets
The decoder found an end-of-contents octet where a tag for an ASN.1 type was expected.
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: The value is not an encoding of a single ASN.1 type.
The decoder found an ANY or open type encoding that contains more than one value. Both types can contain only one value.
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: User constraint function returns error
The decoder called a user-defined constraint function to check a type value; the function returned a non-zero error code.
D0061S: Single value constraint violated, value = value
The decoder detected a single value constraint violation for an INTEGER, REAL, or character string type.
D0062S: Value range constraint violated, value = value
The decoder detected a value range constraint violation for an INTEGER or REAL type.
x0063S: Size constraint violated, length of value = value
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.
Payload-location ::= OCTET STRING(SIZE(1..16))The (SIZE(16)) constraint specifies that the OCTET STRING can be between one and sixteen bytes long.
x0064S: Permitted alphabet constraint violated, bad character:
The encoder/decoder found a permitted alphabet constraint violation for a character string type.
NOTE: When encoding/decoding multilingual characters, use the BMPString (2-octets per character) or UniversalString ASN.1 type (4-octets per character).
x0065S: Absence constraint violated
The constraint checker found that a component marked ABSENT in a WITH COMPONENTS is present in the input.
x0066S: Presence constraint violated
The constraint checker found that a component marked PRESENT in a WITH COMPONENTS is absent from the input.
x0067S: Error in copying an open type
The ossCmpValue() or ossCpyValue() function encountered an error while copying an open type.
Make sure that the open type was decoded correctly.
x0068S: Table constraint violated
The encoder/decoder found an information object table constraint violation in the input.
Provide encoder/decoder input containing values that satisfy the specified constraint.
Provide encoder/decoder input containing values that satisfy the specified constraint.
x0071S: Value not among the ENUMERATED: value
The encoder/decoder found an ENUMERATED type with a value that does not match any of the declared enumerators.
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: Length of encoded component unexpectedly 0, field field
The encoder found a zero length field specified for a SET, SEQUENCE, CHARACTER STRING, or EMBEDDED PDV type.
Specify a non-zero length for the problematic field.
x0073S: Attempt made to pass a NULL control table pointer
The Time-Optimized BER/PER/XER/E-XER/OER Encoder/Decoder found a passed code file pointer that is NULL.
x0074S: NULL function pointer in the control table
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.
x0075S: The control table appears to have been corrupted
The encoder/decoder found that the OssGlobal structure points to a corrupt control table.
Do not manually modify the OssGlobal structure's reserved fields.
D0076S: A negative unsigned integer encountered
The decoder found an unsigned INTEGER value whose bits resemble a negative number.
x0077S: Size constraint violated, number of SET OF/SEQUENCE OF components = number
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.
x0078S: Type constraint violated, PDU number = number
The encoder/decoder found a type constraint violation in the input.
Provide constraint-compliant input to the encoder/decoder.
x0079S: User-defined open type user-field-handling function returned a non-zero error code
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.
Pass two NULL pointers as the second and third arguments to the ossSetUserFieldCpyCmp() function.
D0080E: Bit string value too long for local representation
The decoder found a value for a BIT STRING type that is too large to fit in the local C/C++ representation.
Use the OSS.UNBOUNDED directive to achieve a representation of the BIT STRING type that can be arbitrarily large.
D0081S: End of input reached before message was fully decoded
The decoder encountered the end of the input buffer before the PDU under process was fully decoded.
Make sure that the length field of the input OssBuf variable is correctly set to the full length of the input buffer.
x0083S: Zero bytes of memory requested
The encoder/decoder memory manager received a request for zero bytes of memory.
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.
x0084S: Attempt made to allocate a block of memory greater than 'ossblock'; bytes requested = number of bytes
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.
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.
The C compiler for Alpha/OSF has an issue that could make this error message falsely appear in some cases.
x0085S: Memory allocation failed; bytes requested = number of bytes
The encoder/decoder memory manager received an "out of memory" signal from the operating system.
Increase your application stack size.
x0086S: Unrecognized memory object, address = address
The encoder/decoder memory manager was passed a memory object that fails the check-bounds test.
x0087S: Undefined memory-management error error-code-number
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
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.
x0089E: Length of encoded data of ANY is 0
The decoder found an ANY type whose encoding was found to have a length of zero.
x0090E: Length of encoded data of OpenType is 0
The decoder found an open type whose encoding was found to have a length of zero.
Other Causes
x0091E: Invalid decimal REAL
The encoder encountered a REAL type stored in DECIMAL representation and found the contents of the character string containing the REAL value was invalid.
Make sure the character string containing the decimal value to be encoded holds a valid value.
x0092E: Invalid MixedReal, kind = description
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.
Make sure the REAL type is stored as either a decimal value or a regular binary number.
x0093E: Too many optional fields in extension group
The PER decoder found a preamble, which indicates the presence and absence of optional PDU fields, to be more than 800 bits long.
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: Fatal error when encoding extension addition:
The encoder/decoder detected that an extension group in a SET or SEQUENCE type was missing a non-optional field.
Check the encoding application for errors.
x0095S: Mandatory field is not present in extension group:
The encoder/decoder memory manager received an "out of memory" signal from the operating system.
Increase your application stack size.
This error code is currently not in use.
x0097S: Stack overflow. Provided buffer is too small; requested size:
The encoder/decoder memory manager received an "out of memory" signal from the operating system.
Increase your application stack size.
x0098S: Stack internal inconsistency had been detected
The encoder/decoder memory manager detected that a required buffer was locked.
Do not call allocStack() manually until the required buffer is unlocked.
D0099E: Real value too large for local representation
x0100S: Unknown encoding rules were requested, use BER/DER/CER/PER/XER/CXER/E-XER/OER only.
The encoder/decoder found a specified set of encoding rules was invalid.
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.
This message number is not issued for the full commercial version of the OSS ASN.1 Tools.
This message number is not issued for the full commercial version of the OSS ASN.1 Tools.
x0103S: The requested encoding rules were not linked: theER
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.
x0104S: Control table mismatch in ...
Different, incompatible versions of the ASN.1/C++ Runtime and the ASN.1/C++ Compiler were used.
Use the Runtime version that is the same as the ASN.1 Compiler version used to compile the input specification.
This error code is currently not in use.
This error code is currently not in use.
x0107S: REAL DLL failed:
The encoder/decoder could not access the OSS Nokalva dynamic library containing the routines needed for encoding/decoding REAL types.
Make sure the OSS Nokalva DLLs are in your executable search path.
x0109S: Constraint checker DLL failed:
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.
Make sure the OSS Nokalva DLLs are in your executable search path.
x0110S: Value comparator DLL failed:
The encoder/decoder could not access the OSS Nokalva dynamic library containing the routines needed for comparing and copying decoded PDUs.
Make sure the OSS Nokalva DLLs are in your executable search path.
x0111S: Value comparator code not linked or initialized
The encoder/decoder could not find the value comparator routines in the target executable code.
Re-link the application object code with the OSS Nokalva value comparator function library.
x0112S: REAL code not linked or initialized
The encoder/decoder could not find the REAL type-handling routines in the target executable code.
Re-link the application object code with the OSS Nokalva REAL type-handling function library.
x0113S: Tracing code not linked or initialized
The encoder/decoder memory manager received an "out of memory" signal from the operating system.
Increase your application stack size.
This message number is currently not in use.
x0115S: OBJECT IDENTIFIER converter DLL failed:
The encoder/decoder could not access the OSS Nokalva dynamic library containing OBJECT IDENTIFIER value conversion routines.
Make sure the OSS Nokalva DLLs are in your executable search path.
x0116S: Data type is not supported by DER time-optimized encoder
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
Remove the unsupported representation from the ASN.1 input.
D0117S: Expected definite length, found indefinite length DER encoding
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.
Check the encoding application for errors.
x0118S: The encoder/decoder was generated without support for selected encoding rules:
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.
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).
x0119S: Error converting character to UTF8 format at position
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.
Design a filtering mechanism to remove invalid characters before they get to the encoder/decoder.
x0120S: Incorrect sequence of octets in UTF8String
The encoder/decoder found an invalid character in a UTF8String, probably from converting a UCS-4 or UCS-2 string to a UTF8String.
Design a filtering mechanism to remove invalid characters before they get to the encoder/decoder.
x121E/S: Encoding contains a value for a removed field
The decoder found a component value marked with the ASN1.Remove compiler directive in the original ASN.1 specification.
Delete the ASN1.Remove compiler directive from the problematic field.
x0122S: End of input reached before PDU was fully decoded; additional bytes expected:
The decoder found that the input encoding ended prematurely, before all the mandatory fields of a PDU were decoded.
Check the encoding application or the transmission method for errors.
x0123S: PER tracing DLL failed:
The encoder/decoder could not find the PER trace routines dynamic library.
Make sure that the OSS Nokalva DLLs are in your operating system's search path.
E0124S: Unable to relay unknown extension: relay-safe encoding has not been enabled
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.
Specify the -relaySafe compiler option or obtain the updated versions of your .asn files that match the protocol version of the binary data.
E0124S: Unable to relay unknown extension: the extension was decoded by the <Coder1> but is relayed by the <Coder2>
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.
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
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: End of input file detected; no PDU was decoded from:
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.
Stop calling the decoder after the last PDU on the file has been decoded.
x0126S: Value does not satisfy its subtype constraints
The Java Tools encoder/decoder found that an ASN.1 type value does not satisfy an applied subtype constraint.
Correct the value to comply with the subtype constraint.
x0127S: Coder error when automatically encoding/decoding open type
The Java Tools encoder/decoder experienced an error when trying to automatically encode/decode an open type.
Make sure that the open type you want to encode/decode can be automatically encoded/decoded accurately.
x0128S: Unexpected exception
The Java Tools encoder/decoder found a thrown exception that did not have pre-defined error-handling.
Make sure that you are not using the ASN.1 Tools components incorrectly.
x0129S: Invalid REAL NaN in input
The Java Tools encoder/decoder encountered a REAL type component value that is not a number.
Store only numerical data in a REAL type representation.
x0130S: internal error
The Java Tools encoder/decoder encountered an internal error.
Contact OSS Nokalva Support.
x0131S: Can not open input file: filename
The encoder/decoder encountered an access error when trying to open the input data file.
Make sure that the process running your application has read permission for the file to be opened.
D0132S: Buffer provided for temporary memory is too small; Bytes requested: number
The Time-Optimized Decoder found that the size of the temporary memory buffer specified with the ossSetTemporaryBuffer() function is too small.
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: Internal error: Problem with temporary buffer. Please contact OSS.
The Time-Optimized Decoder encountered a problem freeing the memory associated with the temporary memory buffer in use.
Contact OSS Nokalva Support.
x0134S: Your trial period has expired
You are using a TRIAL version of the ASN.1 Tools that has expired.
Contact OSS Nokalva Sales to request an extension of your trial.
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.
The runtime failed to validate your license.
Perform any actions described in the error message text. Contact OSS Nokalva Support if you still get the error message.
D0136E: Length not a multiple of character width, length: length
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.
D0137E: Encoding of an object identifier must be primitive:
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.
P0138S: User print function reported an exception
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.
None: this error was generated by the user's own code.
x0139S: Control table shared library failed to load:
The ossUinit() function could not load a control table or code file compiled as a DLL into memory at runtime.
Make sure that the specified DLL name is correct and has the proper read or execute permission set.
x0140S: Control table shared library failed to unload:
The ossUterm() function could not unload a control table or code file compiled as a DLL from memory at runtime.
Make sure that the memory stack was not corrupted during runtime.
E0141E: The 'decoded' and 'pduNum' fields were initialized but the AUTOMATIC_ENCDEC flag was not specified
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.
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: The 'decoded' field and AUTOMATIC_ENCDEC flag are specified but the 'pduNum' field was not initialized
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.
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: The DeferDecoding directive was used but the 'length' field
was not initialized
The encoder was handed an OpenType structure (created using the ASN1.DeferDecoding directive) for encoding, but the encoded field length was not specified.
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.
x0144E: Integer or enumerated value too long: length = length
Check the encoding application for errors.
E0145E: DER encoding for HugeSetOf not implemented
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.
Consider using SEQUENCE OF instead of SET OF when you need to support huge values with DER.
This error code is currently not in use.
D0147E: XML attribute 'form' repeated; value used: value
The decoder found two form attributes in a single XML encoding. Only one such form attribute is used per encoding.
Check the encoding application for errors.
D0148E: XML attribute name and/or value is incorrect: name or value
The decoder found an unrecognized or unsupported form attribute in the input XER encoding.
Check the encoding application for errors.
D0149E: Expecting XML start-tag
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.
Check the encoding application for errors.
D0150E: Expecting XML start-tag or empty-tag
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.
Check the encoding application for errors.
D0151E: XML tag name does not match PDU number: tag
The decoder found an XML tag mismatch between the sent encoding and the PDU to be decoded.
Make sure that the PDU number passed to the decoder matches the PDU of the input encoding.
D0152E: Unrecognized or ambiguous PDU name: name
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.
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: XML end-tag name does not match XML start-tag name: tag
The decoder found an XER end tag that does not match the type of the previous XER start tag.
Check the encoding application for errors.
D0154E: Expecting XML end-tag
The decoder encountered the end of an XER encoding before an end tag was found.
D0155E: Expecting XML value of type
The decoder found a missing value in the sent XER encoding.
Make sure that the sent encoding matches the schema set by the input ASN.1 definition for the type.
D0156E: Expecting <TRUE/> or <FALSE/>
The decoder found an XER BOOLEAN type whose value was other than the allowed <TRUE/> and <FALSE/> values defined by the XER standard.
D0157E: Expecting value for a component of SET / SEQUENCE / CHOICE but XML tag name does not match any component identifier: tag name
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.
D0158E: Expecting XML empty-element tag for the named value but XML tag name does not match any named value: tag name
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.
D0159E: Expecting mandatory whitespace between SET OF / SEQUENCE OF element values of space-separated list
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.
x0160E: Control table is not usable by XER
The encoder/decoder found that the ASN.1-compiler produced control table lacked debugging information critical to handling XER encodings.
When ASN.1-compiling the input specification, be sure to specify the -xer option and to not specify the -noDebug option.
D0161E: Illegal UCS-4 character found: character
The decoder found a character following a UCS-4 escape sequence is not a valid character.
Check the encoding application for errors.
x0162S: Pattern constraint violated, value = string value
The encoder/decoder detected a PATTERN constraint violation in a restricted character string type value.
Modify the value to conform to the PATTERN constraint specified in the input ASN.1 specification.
x0163S: Pattern constraint checker not linked or initialized
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.
Recompile the ASN.1 specification with the PATTERN constraint specified. Do not specify the -noConstraint option.
x0164S: This configuration of the runtime does not support this operation
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.
Either manually decode/encode the contained values or use oss.jar, the full runtime library.
x0165S: The OSS.OBJHANDLE directive was applied to an item that has fragmented encoding
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.
Recompile the ASN.1 specification without the OSS.OBJHANDLE or OSS.NOCOPY directive applied.
D0166E: XML tag name expected
The decoder found an XER message containing an opening bracket (e.g., "<" or "</") without a following XML tag name.
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: Invalid syntax for XML tag
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").
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: Invalid XML tag name 'name'
The decoder found an XML tag name that violates standard conventions. For example, it contains characters forbidden by the X.693 standard.
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: XML tag name too long
The decoder found an XML tag name longer than 256 characters, which is the maximum length permitted by the decoder.
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: XML comment expected
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:2021 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.
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: Illegal XML escape sequence found
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]).
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: Unexpected XML comment
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).
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: Typereference expected, conflicting PDU: pdu_number
This error message is now obsolete and should not be issued.
D0174E: Canonical XER restrictions violated: 'message'
The Canonical XER decoder encountered a standards violation in the input encoding.
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.
D0175E: Illegal character in XML character string: char_code
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.
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: XML tag name does not match SET OF / SEQUENCE OF element type: name
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.
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>
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.
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: Expecting XML empty-tag
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)).
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: The number of bits is not multiple of eight in the bit string's segment #number
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.
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: Invalid number
The error occurs when decoding integer data using the XML encoding rules: XER, CXER or E XER.
Check the encoding application for errors.
D0180E: Invalid hex digit in xmlhstring
The Java decoder found an invalid digit in an hexadecimal string contained within an XER encoding.
Check encoding applications for errors.
D0181E: Invalid binary digit in xmlbstring
The Java decoder found an invalid digit in a binary string contained within an XER encoding.
Check encoding applications for errors.
D0182E: Invalid object identifier
The Java decoder found an invalid object identifier value contained within an XER encoding.
Check encoding applications for errors.
E0183E: XER coding for the data type has not been implemented yet
The Java encoder was passed a type for XER encoding which still has not been implemented.
Contact OSS Nokalva Support to explain your requirements.
D0184E: The nesting level of constructed string encodings exceeded the limitation
The decoder received a constructed encoding with a number of successively nested encodings past the maximum allowed nest level.
Either change the encoding application to produce encodings with lower nest levels or call the ossSetConstructedNestingLimit() routine to set a higher nesting limit.
D0185E: The nesting level of encoding of SET, SEQUENCE, SET OF, SEQUENCE OF or CHOICE exceeded the limitation
The decoder received an encoding of a complex type with a number of successively nested subtypes past the maximum allowed nest level.
Either change the encoding application to produce encodings with lower nest levels or call the ossSetConstructedNestingLimit() routine to set a higher nesting limit.
E0186S: Constraints applied to FixedTypeValueSetFields or VariableTypeValueSetFields are not currently supported.
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.
Remove the unsupported constraint.
D0187E: Invalid XML tag attribute
The decoder detected invalid XML tag attribute syntax in the source encoding.
<?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>
D0187E: Invalid XML tag attribute; check field #0 of PDU #1 'S' at line 8 position 17.
Check the encoding application for errors.
D0188E: Equal sign '=' after XML tag attribute expected
The decoder did not find an equal sign after the name of an XML tag attribute in the source encoding.
<?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>
D0188E: Equal sign '=' after XML tag attribute expected; check field #0 of PDU #1 'S' at line 8 position 15.
Check the encoding application for errors.
D0189S: Illegal character in XML character reference: character
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;).
<?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>x2;</first>
<last>Doe</last>
<middle>M</middle>
</S>
D0189S: Illegal character in XML character reference: 'x'; check field #0 of PDU #1 'S' at line 8 position 14.
Check the encoding application for errors.
D0190S: Illegal XML character reference
The EXTENDED-XER decoder found an XML character reference that refers to a character forbidden in XML documents.
<?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>�Michael</first>
<last>Doe</last>
<middle>M</middle>
</S>
D0190S: Illegal XML character reference; check field #0 of PDU #1 'S' at line 8 position 19.
Check the encoding application for errors.
D0191S: Reference to unknown entity: entity name
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.
<?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>
D0191S: Reference to unknown entity: 'myName2'; check field #0 of PDU #1 'S' at line 8 position 11.
Check the encoding application for errors.
D0192S: Illegal entity reference
The EXTENDED-XER decoder found an incorrectly formed XML entity reference (e.g., illegal characters are present between "&" and ";").
<?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>&myame;</first>
<last>Doe</last>
<middle>N/A</middle>
</S>
D0192S: Illegal entity reference; check field #0 of PDU #1 'S' at line 7 position 14.
Check the encoding application for errors.
D0193S: Undefined namespace prefix encountered: name
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.
<?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>
D0193S: Undefined namespace prefix encountered: 'pre:first'; check field #0 of PDU #1 'S' at line 7 position 4.
Check the encoding application for errors.
D0194S: CDATA section not finished
The EXTENDED-XER decoder encountered the end of the source document while reading a CDATA section.
D0195S: CDATA section expected
The EXTENDED-XER decoder found what seemed to be the start of a CDATA section but then detected incorrect syntax.
<?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>
D0195S: CDATA section expected; check field 'last' of PDU #1 'S' at line 9 position 14.
Check the encoding application for errors.
D0196S: Illegal character in XML document: character
The EXTENDED-XER decoder found a character that is forbidden in XML documents, such as one with a code greater than 0x10FFFF.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
<!ENTITY myName "">
]>
<S xmlns="http://www.example.org/data"
xmlns:asn1="urn:oid:2.1.5.2.0.1">
<first>&myName;</first>
<last></last>
<middle>M</middle>
</S>
D0196S: Illegal character in XML document: {0,0,0,1}; check field #0 of PDU #1 'S' at line 3 position 25.
Check the encoding application for errors.
D0197S: Too complex XML document - probably recursive or deeply nested internal entities
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.
Check the encoding application for errors.
D0198S: This type of entity is not supported yet
The EXTENDED-XER decoder found an entity definition or reference that is not currently supported (e.g., a parameter entity definition).
<?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>
D0198S: This type of entity is not supported yet at line 3 position 13.
D0199S: The buffer is too small for the encoded value
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.
D0200S: Ill formed entity: entity name
The EXTENDED-XER decoder encountered an entity definition that is syntactically incorrect.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE A [
<!ENTITY myName ">
]>
<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>
D0200S: Ill formed entity: 'myName' at line 3 position 12.
Check the encoding application for errors.
D0201S: Entity does not contain well-formed XML
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.
Check the encoding application for errors.
D0203S: Illegal DTD
The EXTENDED-XER decoder encountered an incorrect DTD construct.
Check the encoding application for errors.
D0204S: Duplicate DTD
The EXTENDED-XER decoder encountered more than one document type definition in a single document.
Check the encoding application for errors.
D0205S: Invalid notation definition
The EXTENDED-XER decoder detected a syntax error in a notation definition (in the document type definition).
Check the encoding application for errors.
D0206S: Invalid character in a name: name
The EXTENDED-XER decoder encountered an illegal character in a name, such as a tag or attribute name, in the input document.
Check the encoding application for errors.
D0207S: UTF8 continuation byte without start byte in a name: name
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.
Check the encoding application for errors.
D0208S: Unfinished UTF8 multi-byte sequence in a name: name
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.
Check the encoding application for errors.
D0209S: Missing local part of a QName: name
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.
<?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>
D0209S: Missing local part of a QName: 'first:'; check field #0 of PDU #1 'S' at line 7 position 4.
Check the encoding application for errors.
D0210S: Missing prefix in a QName: name
The EXTENDED-XER decoder encountered a qualified name (such as a tag or attribute name) that has a colon as the first character.
<?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>
D0210S: Missing prefix in a QName: ':first'; check field #0 of PDU #1 'S' at line 7 position 4.
Check the encoding application for errors.
D0211S: Local part of a QName contain colon(s): name
The EXTENDED-XER decoder encountered a qualified name (such as a tag or attribute name) that has more than one colon in it.
<?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>
D0211S: Local part of a QName contains a colon: 'abc:first:second'; check field #0 of PDU #1 'S' at line 7 position 4.
Check the encoding application for errors.
D0212S: Namespace prefix defined twice: prefix
The EXTENDED-XER decoder encountered a tag that contains two namespace declaration attributes for the same prefix.
<?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>
D0212S: Namespace prefix defined twice: 'abc' at line 7 position 43.
Check the encoding application for errors.
D0213S: Default namespace defined twice
The EXTENDED-XER decoder encountered a tag that contains two namespace declaration attributes for the default namespace.
<?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>
D0213S: Default namespace defined twice at line 7 position 39.
Check the encoding application for errors.
D0214S: XML tag expected
An XML tag was expected at the specified location but something else was found.
<?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>
D0214S: Expecting XML tag; check field #0 of PDU #1 'S' at line 8 position 4.
Check the encoding application for errors.
D0215S: The named value is not recognized : value
The named value was not recognized and not found among the legal names defined in the specification.
Check the encoding application for errors.
D0216S: A named value is forbidden for this type
Named values are not legal for this type because they are not specified in the description.
Check the encoding application for errors.
D0217S: The BOOLEAN value is not recognized : value
The value of a BOOLEAN type is not in a valid format.
Check the encoding application for errors.
D0218S: The name of attribute is repeated : name
The attribute was defined more than once.
Check the encoding application for errors.
D0219S: The plus sign is forbidden without GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword
A "+" sign was encountered in an integer or real value without a preceding MODIFIED-ENCODINGS instruction.
Check the encoding application for errors.
D0220S: Negative zero (-0) is forbidden without GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword
A '-0' value was encountered for an integer without a preceding MODIFIED-ENCODINGS instruction.
Check the encoding application for errors.
D0221S: Leading zeros are forbidden without GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword
The decoder encountered leading zeros for an integer without a preceding MODIFIED-ENCODINGS instruction.
Check the encoding application for errors.
D0222S: Whitespaces are found in BASE64 component of LIST value encoding
The decoder encountered "whitespaces" inside a BASE64 encoding line with the LIST instruction set.
Check the encoding application for errors.
D0223S: Too many named values for BIT STRING : number
The number of named bits exceeds the total number of names; they are probably repeated in the encoding.
Check the encoding application for errors.
D0224S: Incorrect sequence of octets in BASE64 encodings
The decoder encountered an incorrectly encoded BASE64 encoding. Illegal characters or inappropriate lengths were found.
Check the encoding application for errors.
D0225S: Unexpected character in the attribute encoding
An unexpected character was encountered in the attribute encoding.
Check the encoding application for errors.
D0227S: The length of time value is too long
The encoding length for a time value is too long or the value was encoded incorrectly.
Check the encoding application for errors.
D0228S: Value of the 'nil' attribute is not either true/false or 1/0
The decoder found an invalid value for the nil attribute. The legal values for nil are true/false or 1/0.
Check the encoding application for errors.
D0229S: Unknown attribute : name
An unknown attribute was encountered.
Check the encoding application for errors.
E0230S: Invalid URI value encountered : value
An invalid URI value was encountered when encoding an ANY-ATTRIBUTES construct.
Check and correct the encoded value.
E0231S: Wrong URI value encountered : value
A syntactically incorrect URI value was encountered.
Check and correct the encoded value.
E0232S: Wrong prefix value encountered : value
A syntactically incorrect prefix value was encountered.
Check the encoding application for errors.
E0233S: Wrong unprefixed name encountered : name
A syntactically incorrect unprefixed name was encountered.
Check and correct the encoded value.
E0234S: Size constraint on sequence of embedded values violated; number of components =
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.
Check and correct the encoded value.
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
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.
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
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'.
Check and correct the E-XER specification or the encoded value.
E0236S: An encoded value with DEFAULT-FOR-EMPTY instruction applied should not be empty
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.
Module-E0236S DEFINITIONS
XER INSTRUCTIONS ::= BEGIN
Telephone ::= [DEFAULT-FOR-EMPTY AS "undef"]
VisibleString
t Telephone ::= ""
ENCODING-CONTROL XER
GLOBAL-DEFAULTS MODIFIED-ENCODINGS
END
E0236S: The encoded value with DEFAULT-FOR-EMPTY instruction applied should not be empty; check PDU #1 'Telephone'.
Check and correct the E-XER specification or the pre-encoded value.
E0237S: Encoding of list item should not be empty
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).
Check and correct the E-XER specification or the pre-encoded value.
E0238S: Whitespaces are not allowed in LIST value encoding
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).
Check and correct the encoded value.
E0239S: Sequence of ordered values indicates unknown or absent field to be encoded
A missing field or one that does not belong to the sequence for which it is listed was encountered in the encoding list.
Check and correct the encoded value.
E0240S: Size constraint on sequence of ordered values violated; number of components = num
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).
Check and correct the encoded value.
D0241S: EmptyElementReal is forbidden with GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword applied
An XMLSpecialRealValue in the form of an empty-tag was encountered with the MODIFIED-ENCODINGS instruction applied.
Check the encoding application for errors.
x0242S: Exponential notation is forbidden if DECIMAL instruction is applied
The exponential representation of REAL is forbidden when the DECIMAL instruction is applied.
Check and correct the encoded value or check the encoding application for errors.
E0243S: Negative zero (-0) is forbidden if DECIMAL instruction is applied
The signed representation of zero (-0) is forbidden when the DECIMAL instruction is applied.
Check and correct the encoded value.
x0244S: Plus/minus infinity and not-a-number are forbidden if DECIMAL encoding instruction is applied
REAL representations of plus or minus infinity and not-a-number (NaN) are forbidden when the DECIMAL instruction is applied.
Check and correct the encoded value or check the encoding application for errors.
D0245E: Leading zeros are forbidden in exponent if GLOBAL-DEFAULTS encoding instruction with MODIFIED-ENCODINGS keyword is not applied
A REAL representation with leading zeros in the exponent is forbidden when the MODIFIED-ENCODING instruction is not applied.
Check the encoding application for errors.
E0246S: Duplicate values are present in the sequence of ordered values : value
The encoder encountered two identical values in a sequence that sets the number order of the encoded fields.
Check and correct the encoded value.
E0247S: Value does not conform to 'AnyAttributeFormat' : value
This message occurs when an encoded XML attribute contained in a pre-encoded value does not conform to the ANY-ATTRIBUTE format. Possible causes:
Check and correct the encoded value.
E0248S: XML name expected
The EXTENDED-XER decoder expected an XML name but encountered something else.
<?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>
D0248S: XML name expected at line 3 position 12.
(The entity name is missing from the entity definition.)
Check the encoding application for errors.
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
The EXTENDED-XER encoder encountered a character string type value with WHITESPACE COLLAPSE applied that contains leading, trailing, or multiple adjacent spaces.
Check and correct the pre-encoded value.
D0250S: Illegal character in the encoding: character
The EXTENDED-XER decoder encountered a character that is forbidden for the type being decoded.
Check the encoding application for errors.
D0251S: A nil identification attribute is not allowed for this type : type
The EXTENDED-XER decoder encountered a nil attribute in the tag of a type without the USE-NIL instruction applied.
Check the encoding application for errors.
D0252S: A type identification attribute with an unexpected value is found : type
The EXTENDED-XER decoder encountered an identification attribute value that does not match any USE-UNION choice alternative.
Check the encoding application for errors.
D0253S: The prefix 'xml' cannot be bound to any namespace other than XML namespace; no other prefix may be bound to this namespace: prefix
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.
Check the encoding application for errors.
x0254S: Compression/decompression code not linked or initialized
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.
Either use the -compress ASN.1 compiler option or install custom compression codecs. Alternatively, disable the USE_COMPRESSION runtime flag.
x0255S: Encoding compression/decompression error, code number
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.
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.
E0256S: Value does not conform to the 'AnyElementFormat' : value
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.
Make sure that the value of the type passed to the encoder contains a complete XML element that is syntactically correct.
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.
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.
Execute your application on the same machine on which you ran the ASN.1 Compiler. You can download a new trial to run on a different machine.
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.
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.
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: Fragments within a PER encoding are not grouped correctly
The input encoding is fragmented incorrectly. Refer to section 11.9.3.8 in the X.691 standard for details.
E0259S: User application reported an error, error code: value
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.
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.
D0260E: Length of encoded data of ContentsConstraint is 0.
The encoder or decoder could not continue encoding or decoding a contents constraint because it has a zero length. A proper contents constraint encoding is at least 1-byte in length.
Check the encoding application for errors.
D0261E: Character code too long.
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.
D0262S: Encoding of a TIME type consists of more than one fragment
The input time type (UTCTime, GeneralizedTime) PER encoding is fragmented. This error is reported by the LED runtime library.
Turn off the STRICT_ENCODING_DECODING runtime flag to suppress this error.
D0263E: The padding bits are not zero.
The decoder found that the padding bits of a PER-Aligned encoding are not zero.
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: None of CHOICE type's alternatives fits the encoded value.
The E-XER decoder detected an erroneous element of [USE-UNION] CHOICE and the element value fits none of the alternatives.
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>
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).
Check the encoding application for errors.
x0326E: PropertySettings constraint violated
The encoder, decoder, or constraint checker detected a property settings constraint violation in a time type value.
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.
x0327E: Duration range constraint violated, value
The encoder, decoder, or constraint checker detected a duration range constraint violation in a time type value.
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.
x0328E: TimePoint range constraint violated, value
The encoder, decoder, or constraint checker detected a time point range constraint violation in a time type value.
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.
x0329E: Recurrence range constraint violated, number of recurrences
The encoder, decoder, or constraint checker detected a recurrence range constraint violation in a time type value.
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.
x0330E: Invalid canonical form of time value: 'message'
The canonical encoding XER decoder detected a standards violation in the input encoding.
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.
D0331E: The name of the root element does not match the name in the DTD: tag name
The decoder found a root element name that does not match the name in the document type declaration.
Check the encoding application for errors.
D0333E: Unsupported XML encoding format was detected. Please contact OSS Nokalva, support@oss.com, if you need support for this format: unknown format
The decoder found a XML declaration with an unsupported XML encoding format.
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.
x0334E: Invalid OID internationalized resource identifier value:
[foundValue]; check ...
The encoder/decoder found an empty ArcIdentifier in an OID-IRI/RELATIVE-OID-IRI value, for example:
Check the encoding application for errors.
V0334E: Element of SET OF / SEQUENCE OF must not be null
A SET OF or SEQUENCE OF value contains an element that is null. Elements of SET OF and SEQUENCE OF cannot be null references.
"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'"
Assign a proper (non-null) object reference to the element that is null.
x0335E: Invalid arc in the OID internationalized resource identifier value:
[foundArc]; check ...
The encoder/decoder detected one of the following problems:
Check the encoding application for errors.
V0335E: Value for a component of SET / SEQUENCE / CHOICE must not be null
A SET or SEQUENCE is missing a mandatory field, or a CHOICE alternative is null.
"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'"
Assign values for all SET and SEQUENCE mandatory fields.
Assign a non-null object reference as a CHOICE value.
D0336S: Non-PER encoding rules were requested for ossPrintPER.
ossPrintPER detected that an invalid set of encoding rules was specified.
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: Licensing error. Please contact OSS Nokalva, Inc.
The check on your license failed.
Contact info@oss.com for detailed information.
x0338S: This version of the OER encoder/decoder does not support 'requested feature'.
Your version of the runtime library does not support the requested feature.
E0338S: This version of the OER encoder/decoder does not support 'ContentsConstraint with ENCODED BY'.
Contact OSS Nokalva, support@oss.com, if you require this feature.
x0339S: Cannot close input file.
The OSS memory manager cannot close the input file.
E0339S: Cannot close input file.
Check the permissions on the work and temporary directories.
x0340S: Cannot open output file.
The OSS memory manager cannot open the output file.
E0340S: Cannot open output file.
Check the permissions on the work and temporary directories.
x0341S: Cannot close output file.
The OSS memory manager cannot close the output file.
E0341S: Cannot close output file.
Check the permissions on the work and temporary directories.
x0342S: Error writing to file.
The OSS memory manager detected a file write error.
E0342S: Error writing to file.
Check the permissions on the work and temporary directories.
x0343S: Error reading from file.
The OSS memory manager detected a file read error.
E0343S: Error reading from file.
Check the permissions on the work and temporary directories.
x0344S: Cannot open temporary file.
The OSS memory manager cannot open a temporary file.
E0344S: Cannot open temporary file.
Check the permissions on the work and temporary directories.
x0345S: The part of deferred value is in the initial buffer.
The OSS memory manager detected part of the deferred value in the initial buffer.
D0345S: The part of deferred value is in the initial buffer.
Check the application for errors.
x0346S: Incorrect deferred value in the initial buffer.
The OSS memory manager detected an incorrect deferred value in the initial buffer.
D0346S: Incorrect deferred value in the initial buffer.
Check the application for errors.
x0347S: Error writing to socket.
The OSS memory manager detected a socket write error.
E0347S: Error writing to socket.
Check the application for errors.
x0348S: Error reading from socket.
The OSS memory manager detected a socket read error.
D0348S: Error reading from socket.
Check the application for errors.
x0349S: Cannot load socket DLL.
The OSS memory manager could not access the socket dynamic library.
D0349S: Cannot load socket DLL.
Make sure that there is a socket DLL in your executable search path.
x0350S: Cannot get a procedure address.
The socket DLL does not provide the required functions.
D0350S: Cannot get a procedure address.
Check that the correct socket DLL is used.
x0351S: Invalid socket handle.
The OSS memory manager detected an invalid socket handle.
D0351S: Invalid socket handle.
Check the application for errors.
x0352S: Timeout expired while writing to the socket.
The timeout expired while writing to the socket.
E0352S: Timeout expired while writing to the socket.
Check the application for errors.
x0353S: Timeout expired while reading from the socket.
The timeout expired while reading from the socket.
D0353S: Timeout expired while reading from the socket.
Check the application for errors.
x0354S: Unknown marked object.
The OSS memory manager detected an unknown marked memory object.
D0354S: Unknown marked object.
Check the application for errors.
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.
The decoder found that the container length does not match the length of the encoding it contains.
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.
Check the encoding application for errors.
D0356S: Value of DURATION misencoded.
The decoder encountered an invalid encoding of a DURATION type. Following are possible causes:
D0356S: Value of DURATION misencoded.
Check the encoding application for errors.
0357S: The XER/CXER/E-XER/JSON decoders do not support ossPartialDecode().
The ossPartialDecode() function was called while the TOED XER/CXER/E-XER/JSON encoding rules were in use.
0357S: The XER/CXER/E-XER/JSON decoders do not support ossPartialDecode().
Do not use the ossPartialDecode() function with the TOED XER/CXER/E-XER/JSON encoding rules.
0358S: Partial decoding stopped by user callback return code #N.
The code returned by the user callback function differs from OSS_CONTINUE_DECODING and OSS_SKIP_TO_PDU_END. It immediately terminates the decoding.
0358S: Partial decoding stopped by user callback return code 1025.
If the decoding must not be immediately terminated, consider the OSS_SKIP_TO_PDU_END or OSS_CONTINUE_DECODING return code.
0359S: ossDecode() is disabled by the -partialDecodeOnly option.
The ossDecode() function was called for a specification that was ASN.1-compiled with the -partialDecodeOnly option.
0359S: ossDecode() is disabled by the -partialDecodeOnly option.
Do not use the ossDecode() function or do not specify the -partialDecodeOnly option.
x0360S: Encoding/decoding is supported for PDUs only. Consider using the OSS.PDU directive to enable encoding/decoding of this type.
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.
D0356S: Value of DURATION misencoded.
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: Unknown token found, expecting 'token1'.
An unexpected token was encountered.
D0361S: Unknown token found, expecting'}' or '"'.
D0361S: Unknown token found, expecting '{'.
Check the JSON encoding and add the expected token.
D0362S: Unknown member name: 'name'.
An unknown ASN.1 component name or unexpected standard member name ("length", "value", etc.) was encountered in the input JSON encoding.
D0362S: Unknown member name: 'givenName'.
Check the JSON encoding and remove or replace the unknown member name.
D0363S: Length of the item is too long: item.
The JSON decoder found that the length of one of the following tokens exceeds the implementation limit of 255 bytes:
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.
Change the ASN.1 specification to fit the implementation restriction or contact Technical Support <support@oss.com> if you need support for longer tokens.
D03654S: Invalid encoding of item.
The JSON decoder encountered an invalid encoding of 'item'.
D03654S: Invalid encoding of hexadecimal string.
D03645S: Invalid encoding of JSON number.
D03645S: Invalid encoding of BIT STRING.
Check the encoding application for errors.
D0365S: Invalid ENUMERATED identifier: 'name'.
The enumerator with the specified name does not exist in the corresponding ENUMERATED type.
D0365S: Invalid ENUMERATED identifier: 'x'.
Check the encoding application for errors.
D0366S: message.
The decoder encountered some inconsistency in the input JSON encoding.
D0366S: Unknown token.
D0366S: Illegal surrogate pair.
D0366S: Illegal escape sequence.
Check the encoding application for errors.
D0367S: Bad Unicode value: {value}.
The JSON encoder encountered an invalid Unicode character value.
D0367S: Bad Unicode value: {0,0,255,255}.
Check the input value.
D0368S: Decoding is impossible due to ASN.1 compiling with the
-encodeOnly option or presence of the OSS.ENCODEONLY directive, check PDU #num.
The PDU could not be decoded because the -encodeOnly compiler option is specified or the OSS.ENCODEONLY directive is applied to the PDU.
D0368S: Decoding is impossible due to ASN.1 compiling with the
-encodeOnly option or presence of the OSS.ENCODEONLY directive, check PDU 1.
Make sure that the -encodeOnly compiler option is not specified and the OSS.ENCODEONLY directive is not applied to the PDU.
E0369S: Encoding is impossible due to ASN.1 compiling with the
-decodeOnly option or presence of the OSS.DECODEONLY directive, check PDU #num.
The PDU could not be encoded because the -decodeOnly compiler option is specified or the OSS.DECODEONLY directive is applied to the PDU.
E0369S: Encoding is impossible due to ASN.1 compiling with the
-decodeOnly option or presence of the OSS.DECODEONLY directive, check PDU 1.
Make sure that the -decodeOnly compiler option is not specified and the OSS.DECODEONLY directive is not applied to the PDU.
x0370S: Canonical PER encoding for SET OF not implemented yet
The Canonical PER encoder/decoder detected that the SET OF ASN.1 type is used. However, this type is currently not supported.
Don't use the SET OF type with Canonical PER. Consider using SEQUENCE OF instead of SET OF.
D0371S: Decoding is impossible due to presence of the OSS.NODECODE directive
The -compactNoDecode option was specified but the decoder detected the presence of an encoding of either a CHOICE alternative or a SEQUENCE or SET field marked with the OSS.NODECODE directive.
Check the encoding application for errors, remove the OSS.NODECODE directive, or ASN.1 recompile without the -compactNoDecode option.
E0372S: Encoding of the CHOICE alternative is prohibited by the OSS.NOENCODE directive
The CHOICE value to be encoded contains an alternative marked with the OSS.NOENCODE directive.
Check the encoding application for errors or remove the OSS.NOENCODE directive.
D0373S: The input message contains an encoding that cannot be converted
The ossBinary2XML(), ossXML2Binary(), ossBinary2JSON(), ossJSON2Binary(), ossBinary2AVN(), and ossAVN2Binary() OSS API functions perform conversion by decoding and then re-encoding the input message. OSS conversion API functions always report this error when a proper conversion is not possible due to any of the following reasons:
Make sure that the input message can be fully decoded.
D0375E: message.
The ossPrintPDU() function encountered an inconsistency in the input PDU value.
D0375E: An invalid PDU number in open type value.
D0375E: Both decoded and encoded values are absent in open type value.
D0375E: Pointer to the value is NULL.
D0375E: Decimal real value implementation limit exceeded.
D0375E: Pointer to the decimal real value is NULL.
D0375E: Bad choice selector.
Check the input PDU value for errors.
E0376S: The input message contains the opaque data that cannot be re-encoded using the other encoding rules
The data that was passed to the encoder contains an encoded fragment that cannot be processed because it uses transfer syntax that is not compatible with the current encoder. For example, this error occurs when a message contains an undecoded open type value that was encoded using BER and an attempt is made to re-encode it using PER.
Make sure that the input message is fully decoded.
D1001S
or
D1001S: Requested type is not linked or not supported by PER decoder
The data type is not supported by the Lean PER decoder.
Remove the unsupported representation from the ASN.1 input.
E1002S
or
E1002S: Requested type is not linked or not supported by PER encoder
The data type is not supported by the Lean PER encoder.
Remove the unsupported representation from the ASN.1 input.
D1003S
or
D1003S: Requested type is not linked or not supported by BER decoder
The data type is not supported by the Lean BER decoder.
Remove the unsupported representation from the ASN.1 input.
E1004S
or
E1004S: Requested type is not linked or not supported by BER encoder
The data type is not supported by the Lean BER encoder.
Remove the unsupported representation from the ASN.1 input.
D1005S
or
D1005S: BER decoder not linked or initialized
The requested BER decoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -ber or -der option.
E1006S
or
E1006S: BER encoder not linked or initialized
The requested BER encoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -ber or -der option.
D1007S
or
D1007S: PER decoder not linked or initialized
The requested PER decoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -per or -uper option.
E1008S
or
E1008S: PER encoder not linked or initialized
The requested PER encoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -per or -uper option.
D1009S
or
D1009S: Requested type is not linked or not supported by XER decoder
The data type is not supported by the Lean XER decoder.
Remove the unsupported representation from the ASN.1 input.
E1010S
or
E1010S: Requested type is not linked or not supported by XER encoder
The data type is not supported by the Lean XER encoder.
Remove the unsupported representation from the ASN.1 input.
D1011S
or
D10011S: XER decoder not linked or initialized
The requested XER decoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -xer or -cxer option.
E1012S
or
E1012S: XER encoder not linked or initialized
The requested XER encoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -xer or -cxer option.
D1013S
or
D10013S: EXER decoder not linked or initialized
The requested E-XER decoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -exer option.
E1014S
or
E1014S: EXER encoder not linked or initialized
The requested E-XER encoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -exer option.
D1015S
or
D1015S: Requested type is not linked or not supported by EXER decoder
The data type is not supported by the Lean E-XER decoder.
Remove the unsupported representation from the ASN.1 input.
E1016S
or
E1016S: Requested type is not linked or not supported by EXER encoder
The data type is not supported by the Lean E-XER encoder.
Remove the unsupported representation from the ASN.1 input.
x1017S
or
x1017S: Requested encoding rules not supported by the LEAN runtime
The requested encoding rules are not supported by the Lean runtime.
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.
x1018S
or
x1018S: Length of the OBJECT IDENTIFIER is greater than 16K or equals to zero
The Lean encoder/decoder found that the value of an OBJECT IDENTIFIER type violates length restrictions.
Check the encoding application for errors.
E1016S
or
E1016S: Requested type is not linked or not supported by EXER encoder
The data type is not supported by the Lean E-XER encoder.
Remove the unsupported representation from the ASN.1 input.
E1020S
or
E1020S: Requested type is not linked or not supported by OER encoder
The Lean OER encoder does not support the ASN1.DeferDecoding directive.
Remove the unsupported representation from the ASN.1 input.
D1021S
or
D1021S: OER decoding rules not linked or initialized
The requested OER decoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -oer or -coer options.
D1022S
or
D1022S: OER encoding rules not linked or initialized
The requested OER encoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -oer or -coer option.
D1023S
or
D1023S: Requested type is not linked or not supported by JSON decoder
The data type is not supported by the Lean JSON decoder.
Remove the unsupported representation from the ASN.1 input.
E1024S
or
E1024S: Requested type is not linked or not supported by JSON encoder
The data type is not supported by the Lean JSON encoder.
Remove the unsupported representation from the ASN.1 input.
D1025S
or
D1025S: JSON decoder not linked or initialized
The requested JSON decoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -json option.
E1026S
or
E1026S: JSON encoder not linked or initialized
The requested JSON encoder is not linked or initialized.
Re-ASN.1-compile your input syntax with the -json option.
D1027S
or
D1027S: Unexpected token found
An unexpected token was encountered.
Check the JSON encoding and add the expected token.
D1028S
or
D1028S: Illegal escape sequence
The decoder encountered an escape sequence that is not valid.
Check the encoding application for errors.
D1029S
or
D1029S: Illegal surrogate pair
The decoder encountered a surrogate pair that is not valid.
Check the encoding application for errors.
D1030S: Duplicated member name in [UNWRAPPED] CHOICE encoding.
The decoder encountered a duplicated member name in [UNWRAPPED] CHOICE encoding.
Check the encoding application for errors.
D1031S: Unrecognized alternative of [UNWRAPPED] CHOICE.
The decoder failed to determine the alternative of [UNWRAPPED] CHOICE.
Check the encoding application for errors.
D1032S: The requested canonical encoding rule is not available.
The Lean encoder/decoder found that the requested canonical encoding rule is not available.
Make sure all encoding rules requested either by the ossSetEncodingRules() API function or by contents constraints with ENCODED BY are specified by the ASN.1 compiler options.
This documentation applies to the latest versions of the OSS® ASN.1 Tools software.
Copyright © 2024 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.