TOP

Compiler Errors Reference (1300-9999)

C1300E

Message Format

C1300E: The time-optimized OER encoder/decoder does not support <feature>.

Message Cause

<feature> is not supported for the time-optimized OER encoder/decoder.

Example

BP ::= BIT STRING (SIZE (0..11)) (CONTAINING INTEGER (0..10) ENCODED BY
 {joint-iso-itu-t(2) asn1(1) packed-encoding(3) basic(0) aligned(0)})

Error Message

"bcc.asn", line 3 (BCC): C1300W: The time-optimized OER encoder/decoder does not support ContentsConstraint with ENCODED BY.

Possible Solution

Remove the directive or the type.

C1301E

Message Format

C1301E: Size constraint is always violated because size of OER encoding is a multiple of eight bits.

Message Cause

The size constraint of BIT STRING with CONTAINING is not a multiple of eight bits.

Example

	B ::= BIT STRING (SIZE (11)) (CONTAINING INTEGER (0..10))

Error Message

"bcc.asn", line 2 (BCC): C1301W: Size constraint is always violated because size of OER encoding is a multiple of eight bits.

Possible Solution

Change the size constraint.

C1305E

Message Format

C1305E: The asn1dflt configuration file must be the first input file.

Message Cause

An asn1dflt configuration file is preceded by other ASN.1 files on the command line. The asn1dflt must be the first input file.

Example

   asn1 -ber z.asn asn1dflt.x86

Error Message

"z.asn" (): C1305E: The asn1dflt configuration file must be the first input file.

Possible Solution

Make sure the configuration file is the first input file.

L1306W

Message Format

L1306W: OER encoding rules are not currently supported by <runtime>, therefore -oer option is ignored. Please contact OSS Nokalva (info@oss.com), if you are interested in OER support for this runtime.

Message Cause

You have specified the -lean, –soed, and –oer compiler options, but OER encoding rules are not supported by the ASN.1/C Lean Encoder/Decoder.

Example

  asn1 –soed –lean –oer test.asn

Error Message

L1306W: OER encoding rules are not currently supported by the ASN.1/C Lean Encoder/Decoder, therefore -oer option is ignored. Please contact OSS Nokalva (info@oss.com), if you are interested in OER support for this runtime.

Possible Solution

Compile the generated files using –DOSS_USE_FULL_SOED_ONLY and link with the SOED runtime. For information about OER support for the LEAN runtime, contact Technical Support ‹support@oss.com›.

NOTE: This error message is deprecated as of release 10.1.

C1307W

Message Format

C1307W: The value 'value reference' of the 'type reference' type is truncated to count elements to satisfy the size constraints applied to the type.

C1307W: The value of the 'type reference' type nested in 'value reference' is truncated to count elements to satisfy the size constraints applied to the type.

Message Cause

An ASN.1 value does not conform to a size constraint applied to SEQUENCE OF or SET OF in the value type and it will be truncated.

Example 1

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   A ::= SEQUENCE (SIZE (1..2)) OF INTEGER
   val A ::= {1, 2, 3}
END

Error Message

"sof1.asn", line 3 (M): C1307W: The value 'val' of the 'A' type is truncated to 2 elements to satisfy the size constraints applied to the type.

Example 2

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   S ::= SEQUENCE {
   b SEQUENCE (SIZE(0..1)) OF INTEGER
   }
   sv S ::= { b { 1, 2, 3 } }
END

Error Message

"sof2.asn", line 6 (M): C1307W: The value of the SEQUENCE OF type nested in 'sv' is truncated to 1 elements to satisfy the size constraints applied to the type.

Possible Solution

Make sure the value falls within the minimum and maximum values of the size constraint.

C1308W

Message Format

C1308W: The value for ''value reference' is being added with zero octets to satisfy the constraints.

Message Cause

An ASN.1 value of OCTET STRING with the PADDED directive applied does not conform to a fixed size constraint.

Example

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   O ::= OCTET STRING (SIZE (3)) --<PADDED>--
   val O ::= '0011'H
END

Error Message

"foct.asn", line 3 (M): C1308W: The value for 'val' is being added with zero octets to satisfy the constraints.

Possible Solution

Make sure the value falls within the fixed size constraint.

C1309W

Message Format

C1309W: The PADDED directive is not supported for type reference types with the -lean option and will be ignored.

Message Cause

An ASN.1 type definition with the PADDED directive applied is not supported for the LEAN runtime.

Example

M DEFINITIONS AUTOMATIC TAGS ::= BEGIN
   B ::= BIT STRING (SIZE (3)) --<PADDED>--
   val B ::= '011'B
END

Error Message

"bits.asn", line 2 (M): C1309W: The PADDED directive is not supported for BIT STRING types with the -lean option and will be ignored.

Possible Solution

Remove the PADDED directive.

C1310I

Message Format

C1310I: No critical errors found, but message(s) were suppressed due to the compiler's default permissive mode. Compile with -noRelaxedMode to see all messages.

Message Cause

Certain errors or warnings are ignored when using the default relaxed mode.

Example

Module-C1310I DEFINITIONS ::= BEGIN
   My_Type ::= SET OF INTEGER
END

Error Message

C1310I: No critical errors found, but message(s) were suppressed due to the compiler's default permissive mode. Compile with -noRelaxedMode to see all messages.

Possible Solution

The message can be ignored. To enable a more thorough ASN.1 syntax checking, use the -noRelaxedMode option.

A1315E

Message Format

A1315E: The outermost type where the 'fieldname' occurs is not set or sequence.

Message Cause

The 'At notation' is not inside a SET or SEQUENCE type.

Example

Module-A1315 DEFINITIONS ::= BEGIN
   MYCLASS ::= CLASS { &id INTEGER, &Type }
   MySet MYCLASS ::= { ... }

   T ::= CHOICE {
      id  MYCLASS.&id ({MySet}),
      val MYCLASS.&Type ({MySet}{@.id})
   }
END

Error Message

"a1315e0.asn", line 9 (Module-A1315): A1315E: The outermost type where the 'val' occurs is not set or sequence.

Possible Solution

Make sure the component relation constraints are correctly applied.

A1316E

Message Format

A1316E: The exponent of a REAL value after 'e' or 'E' shall not be empty.

Message Cause

The input ASN.1 syntax contains a REAL type value, but the exponent specified in the value is empty.

Example

Module-A1316E DEFINITIONS ::= BEGIN
   SomeType ::= REAL
   value SomeType ::= 1e
END

Error Message

"a1316e.asn", line 3 (Module-A1316E): A1316E: The exponent of a REAL value after 'e' or 'E' shall not be empty.
value SomeType ::= 1e

Possible Solution

Provide the appropriate exponent.

A1317E

Message Format

A1317E: The field 'identifier' is marked DEFAULT with the value that does not satisfy the constraints on its type.

Message Cause

The input ASN.1 syntax contains a SEQUENCE field that is marked as DEFAULT; however, its value does not conform to the constraint applied in the base type.

Example

Module-A1317E DEFINITIONS ::= BEGIN
    S ::= SEQUENCE {
        a IA5String (SIZE(1..10)) DEFAULT "CharacterString"
    }
END

Error Message

"a1317e.asn", line 3 (Module-A1317E): A1317E: The field 'a' is marked DEFAULT with the value that does not satisfy the constraints on its type.

Possible Solution

Make sure the value conforms to the subtype constraints.

C1318E

Message Format

C1318E: The CONTAINING alternative of the value of BIT/OCTET STRING is not supported by the Lean and Micro Encoder/Decoder for Java.

Message Cause

The CONTAINING keyword cannot be used in a value definition when the -lean or the -microEdition compiler option is specified.

Example

CCAC DEFINITIONS ::= BEGIN
   CCaC ::= BIT STRING (
   CONTAINING INTEGER
   )

   cCaC CCaC ::= CONTAINING 255
END

Error Message

"ccac.asn", line 3 (CCAC): C0730W: The type BIT/OCTET STRING with Contents Constraint is not supported by the Lean and Micro Encoder/Decoder for Java.

"ccac.asn", line 7 (CCAC): C1318E: The CONTAINING alternative of the value of BIT/OCTET STRING is not supported by the Lean and Micro Encoder/Decoder for Java.

Possible Solution

When you specify the value notation for a BIT STRING or an OCTET STRING with contents constraints, use the bstring or the hstring alternative.

C1322W

Message Format

C1322W: The character {'number1','number2','number3','number4'} does not fit the current representation for UTF8String. Please consider using the OSS.UNIVERSALSTRING directive.

Message Cause

A UTF8String value contains characters that cannot be represented as code points within the Universal Character Set (UCS) code space. The C# string type (the standard representation of the ASN.1 UTF8String type) does not support these characters.

Example

Module- C1322W DEFINITIONS ::= BEGIN
    A ::= UTF8String
    a A ::= {0,20,0,0}
END

Error Message

"c1322w.asn", line 3 (Module- C1322W): C1322W: The character {0,20,0,0} does not fit the current representation for UTF8String. Please consider using the OSS.UNIVERSALSTRING directive.

Possible Solution

You can either remove the character from the string or apply the OSS.UNIVERSALSTRING directive to the corresponding type.

L1323W

Message Format

L1323W: The -microedition option has been deprecated and will not be available in future versions of the OSS ASN.1 Tools for Java.

Message Cause

The ASN.1 compiler command line contains the -microedition option. The -microedition option is deprecated as of release 6.2 of the OSS ASN.1 Tools for Java.

Possible Solution

Remove the -microedition option.

C1327E

Message Format

C1327E: Name '%s' identifying the %s of %s is not unique due to the '%s' encoding instruction.

Message Cause

There are two causes:

  • The ASN.1 type encoded as a JSON object contains JSON member name strings that are not unique.
  • Strings identifying enumeration items in the ASN.1 ENUMERATED type are not unique.

This occurs when the 'NAME' or the 'TEXT' JER encoding instruction is applied.

C1327E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Seq ::= SEQUENCE { 
		color [NAME AS "shape"] IA5String,
		shape IA5String 
  }
  Enum ::= [TEXT zero AS "one"] ENUMERATED {zero(0), one(1)}
END

Error Message

"c1327e.asn", line 3 (C1327E): C1327E: Name 'shape' identifying the component of Seq is not unique due to the 'NAME' encoding instruction.

"c1327e.asn", line 6 (C1327E): C1327E: Name 'one' identifying the enumeration item of Enum is not unique due to the 'TEXT' encoding instruction.

Possible Solution

Make sure the instruction does not violate uniqueness.

C1328E

Message Format

C1328E: TEXT encoding instruction refers to non-existing enumeration item '%s' in %s.

Message Cause

The identifier in the TEXT JER encoding instruction refers to an enumeration item that is not present in the ENUMERATED type.

C1328E DEFINITIONS JER INSTRUCTIONS  ::= BEGIN
  Enum ::= [TEXT zer AS "Null"] ENUMERATED {zero(0), one(1)}
END

Error Message

"c1328e.asn", line 2 (C1328E): C1328E: TEXT encoding instruction refers to non-existing enumeration item 'zer' in Enum.

Possible Solution

Correct the instruction and recompile.

A1329E

Message Format

A1329E: Duplicate %s in the TEXT encoding instruction applied to %s.

Message Cause

A duplicate identifier was found in the 'TEXT' JER encoding instruction.

A1329E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Enum ::= [TEXT zero AS "Null", zero AS "Zero"] ENUMERATED {zero(0), one(1)}
END

Error Message

"a1329e.asn", line 2 (A1329E): A1329E: Duplicate enumeration identifier 'zero' in the TEXT encoding instruction applied to Enum.

Possible Solution

Correct the instruction and recompile.

C1330E

Message Format

C1330E: The alternative '%s' shall not be %s.

Message Cause

The CHOICE alternative does not satisfy the restrictions imposed by the encoding rules.

C1330E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [UNWRAPPED] CHOICE {
		null NULL,
		...
	}
  }
END

Error Message

"c1330e.asn", line 3 (C1330E): C1330E: The alternative 'a1' shall not be an extensible CHOICE type with a final UNWRAPPED encoding instruction.

Possible Solution

Correct the specification and recompile.

C1331E

Message Format

C1331E: The alternative '%s' shall not produce a JSON value of the same kind as alternative '%s' of the [UNWRAPPED] CHOICE type '%s'.

Message Cause

Two alternatives of an [UNWRAPPED] CHOICE produce a JSON value of the same kind for one or more of their abstract values. The following kinds can be conflicting:

  • The null JSON token
  • The false JSON token
  • The true JSON token
  • A JSON number
  • A JSON string
  • A JSON array
C1331E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [TAG:1] INTEGER,
	a2 [TAG:2] INTEGER
  }
END

Error Message

"c1331e.asn", line 4 (C1331E): C1331E: The alternative 'a2' shall not produce a JSON value of the same kind as alternative 'a1' of the [UNWRAPPED] CHOICE type 'Ch'.

Possible Solution

Correct the specification and recompile.

C1332E

Message Format

C1332E: The alternative '%s' shall not produce a JSON object because it is already produced by alternative '%s' of the [UNWRAPPED] CHOICE type '%s'.

Message Cause

In an [UNWRAPPED] CHOICE there are two alternatives that produce a JSON object for one or more of their abstract values, but the alternative types are not SEQUENCE or SET types.

C1332E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [TAG:1] REAL,
	a2 [TAG:2] REAL
  }
END

Error Message

"c1332e.asn", line 4 (C1332E): C1332E: The alternative 'a2' shall not produce a JSON object because it is already produced by alternative 'a1' of the [UNWRAPPED] CHOICE type 'Ch'.

C1333E

Message Format

C1333E: The alternative '%s' shall be either a SEQUENCE type or a SET type because the [UNWRAPPED] CHOICE type '%s' has two or more alternatives that produce a JSON object.

Message Cause

The [UNWRAPPED] CHOICE type already contains an alternative which is either a SEQUENCE or SET that produces a JSON object for its abstract values. All other alternatives that produce a JSON object for one or more of their abstract values must be SEQUENCE or SET types without an extension marker.

C1333E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 SEQUENCE {
		f1 BOOLEAN
	},
	a2 REAL
  }
END

Error Message

"c1333e.asn", line 6 (C1333E): C1333E: The alternative 'a2' shall be either a SEQUENCE type or a SET type because the [UNWRAPPED] CHOICE type 'Ch' has two or more alternatives that produce a JSON object.

Possible Solution

Correct the specification and recompile.

C1334E

Message Format

C1334E: None of the alternatives '%s' and '%s' of the [UNWRAPPED] CHOICE type '%s' have at least one mandatory component whose JSON member name string differs from the JSON member name strings of all the components of the other.

Message Cause

Two or more [UNWRAPPED] CHOICE alternatives that are either SEQUENCE or SET types produce a JSON object for one or more of their abstract values. For any two such types, one of them must have at least one component that is not marked OPTIONAL or DEFAULT and whose JSON member name string differs from the JSON member name strings of all the components of the other type.

C1334E DEFINITIONS JER INSTRUCTIONS ::= BEGIN
  Ch ::= [UNWRAPPED] CHOICE {
	a1 [TAG:1] SEQUENCE { f1 INTEGER },
	a2 [TAG:2] SEQUENCE { f1 INTEGER }
  }
END

Error Message

"c1334e.asn", line 2 (C1334E): C1334E: None of the alternatives 'a1' and 'a2' of the [UNWRAPPED] CHOICE type 'Ch' have at least one mandatory component whose JSON member name string differs from the JSON member name strings of all the components of the other.

Possible Solution

Correct the specification and recompile.

A1335W

Message Format

A1335W: The -allow BadExplicitAutomaticTagging command line option forces the field 'fieldName' to have explicit automatic tagging. It may cause errors at runtime.

Message Cause

The -allow BadExplicitAutomaticTagging command-line option instructs the compiler to conform to the pre-2002 ASN.1 standard (X.680 clause 31.2.7 c) interpretation and use explicit automatic tagging for untagged and tagged CHOICE types, open types, and "DummyReference" types.

Example

B4114 DEFINITIONS AUTOMATIC TAGS ::= BEGIN
    Seq ::= [65] SEQUENCE { ch Cho }
    Cho ::= [65] CHOICE { b BOOLEAN }
END

Error Message

"b4114.asn", line 2 (B4114): A1335W: The -allow BadExplicitAutomaticTagging command line option forces the field 'ch' to have explicit automatic tagging. It may cause errors at runtime.

Possible Solution

Remove the -allow BadExplicitAutomaticTagging option from the command line.

C9999S

Message Format

C9999S: Porting error. Inform OSS technical support.

Message Cause

The ASN.1 compiler has encountered an error when porting the ASN.1 compiler to your platform.
This error can occur if your ossinfo file is corrupt, is outdated, or is not compatible with your installation set up.

Next Action

Send the exact command line and ASN.1 input used to Technical Support ‹support@oss.com› for review.


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

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