TOP

ASN-1Step Error Messages

Applies to: ASN-1Step 8.2

Messages issued by ASN-1Step can be divided into six categories:

ASN-1Step Informatory Messages

ASN1STEP: An internal memory error occurred.
This message is issued when an unexpected memory error occurred. Contact OSS Technical Support to report this error.
ASN1STEP: List of valid PDU numbers and associated PDU names:
This message is issued when -listPduId is specified. If no PDUs are available for decoding, no table is displayed.
ASN1STEP: List of valid PDU numbers (associated PDU names are not available due to -nodebug):
This message is issued when -listPduId is specified along with -noDebug. In this case, the names of all PDUs are printed as <anonymous>.
ASN1STEP: List of valid valuereferences and associated PDU numbers:
This message is issued when -valueRefTable is specified. If no value references are available for encoding, no table is displayed. Also, see this FAQ.
ASN1STEP: Encoding of valuereference 'name' for PDU #pduId.
This message is issued by ASN-1Step while it is encoding a value.
ASN1STEP: Decoding PDU #pduId from file 'filename':
This message is issued when ASN-1Step is decoding values from input encoding files.
ASN1STEP: Decoding of PDU #pduId failed with the return code 'return code'.
This message is issued when ASN-1Step encounters an error when decoding an input encoding.
ASN1STEP: Encoding of PDU #pduId failed with return code 'return code'.
This message is issued when ASN-1Step encounters an error when encoding a value.
ASN1STEP: Re-encoding of 'value' of the PDU #num:
This informatory message is issued when the -decodePdu option is specified along with one or more encoding rules options (e.g., -ber); that is, when the messages are re-encoded from one encoding format into another. It is printed before the encoder trace information.
ASN1STEP: Running Encoder/Decoder test for valuereference 'name' for PDU #pduId.
This message is issued when the -test option is specified.
ASN1STEP: Tracing is written to the file 'filename'.
This informatory message is issued when the -traceFile option is specified. In this case, no trace information will be displayed.
ASN1STEP: Value notation is written to the file 'filename'.
This informatory message is issued when the -asn1Value option is specified. In this case, the resulting value in ASN.1 value notation format is written to the specified file.
ASN1STEP: Decoding concatenated PDU #num from file 'filename'.
This informatory message is issued when the -decodePdu option is specified and the input file contains concatenated PDUs. It is printed between the trace information of concatenated PDUs.
ASN1STEP: Invalid flag in the <optionName> option: flag.
This message is issued when ASN-1Step finds an unrecognized flag in the -allSampleAsn1Values or -sampleAsn1Value option.

ASN-1Step Error and Warning Messages

S0001S

Message Format

S0001S: An internal memory error occurred.

Message Cause

This message is issued when unexpected memory error occurred. Contact OSS support to report this error.


S0002E

Message Format

S0002E: Invalid PDU identifier: 'pdu_id'. Use the -listPduId option to display the list of valid PDU identifiers.

Message Cause

This message is issued when the -decodePdu argument does not correspond to any PDU available for decoding. Specify the -listPduId option to obtain a list of PDU identifiers and names available for decoding.


S0003E

Message Format

S0003E: Error opening input file 'filename'. error description.

Message Cause

This message is issued when ASN-1Step encounters an error when opening an input file.


S0004E

Message Format

S0004E: Error reading from file 'filename'. error description.

Message Cause

This message is issued when ASN-1Step encounters an error when reading from an input file.


S0005E

Message Format

S0005E: Error opening output file 'filename'. error description.

Message Cause

This message is issued when ASN-1Step encounters an error when opening an output file.


S0006E

Message Format

S0006E: Error writing to file 'filename'. error description.

Message Cause

This message is issued when ASN-1Step encounters an error when writing to the specified output file.


S0007E

Message Format

S0007E: Encoding rule determined by the file extension 'ext' is invalid.

Message Cause

This message is issued when ASN-1Step finds that an input encoding file has an unrecognized filename extension.


S0008E

Message Format

S0008E: Valuereference 'name' has the type that is not a PDU.

Message Cause

This message is issued when ASN-1Step finds a value reference in the input is based on a non-PDU type. A PDU (protocol data unit) is a message that can be encoded/decoded as a complete unit.


S0009E

Message Format

S0009E: No valuereference 'name' whose type is PDU was found in the input syntax.

Message Cause

This message is issued when the -encodeValue argument does not match a value reference available for encoding. Specify the -valueRefTable option to obtain a list of value references available for encoding, for example,

asn1step input.asn -valueRefTable

See Also

FAQ: The value reference I want to encode is not listed when I specify the -valueRefTable option. What's wrong?


S0010E

Message Format

S0010E: Encoding of PDU #pduId failed with return code 'return code'. No data is written to the file 'filename'.

Message Cause

This message is issued when ASN-1Step encounters an error when encoding a value.


S0011W

Message Format

S0011W: The parameter in the '-keyword' option is not valid, the default value 'default value' is used.

Message Cause

This message is issued when ASN-1Step finds an unrecognized parameter for an option that takes an argument.


S0012E

Message Format

S0012E: Decoding of PDU #pduId failed with the return code 'return code'.

Message Cause

This message is issued when ASN-1Step encounters an error when decoding an input encoding.


S0013E

Message Format

S0013E: Printing of PDU #pduId failed with the return code 'return code'.

Message Cause

This message is issued when ASN-1Step encounters an error when printing a PDU value in value notation format.


S0014E

Message Format

S0014E: Printing of PER details failed with the return code 'return code'.

Message Cause

This message is issued when ASN-1Step encounters an error when encoding a value.


S0015E

Message Format

S0015E: Runtime initialization failed with the return code 'return code'.

Message Cause

This message is issued when ASN-1Step was not able to initialize the OSS runtime environment, possibly due to a license error.


S0016E

Message Format

S0016E: No PDUs found in the input abstract syntax.

Message Cause

This message is issued when ASN-1Step is unable to find defined types in the input ASN.1 specification suitable for encoding/decoding.


S0017E

Message Format

S0017E: No valuereferences whose types are PDUs found in the input syntax.

Message Cause

This message is issued when ASN-1Step is unable to find defined value references whose types are PDUs in the input ASN.1 specification.


S0018E

Message Format

S0018E: Invalid flag for '-keyword' option: flag.

Message Cause

This message is issued when the -printPerFlags, -xer, -exer, -flags, -encFlags, -decFlags, or -json option's argument does not correspond to a valid flag name.


S0019E

Message Format

S0019E: No files with encoded PDU was specified.

Message Cause

This message is issued when the -decodePdu option is specified but no input encoding files are listed on the command line.


S0020E

Message Format

S0020E: -lean command line option is not supported.

Message Cause

This message is issued if the -lean option is specified.


S0021E

Message Format

S0021E: A PDU identifier must be specified because PDU tags are not unique.

Message Cause

This message is issued when the -decodePdu argument is missing, or is 0 and PDU tags in the input syntax are not unique.


S0022E

Message Format

S0022E: Invalid flag for XER encoder: flag.

Message Cause

This message is issued when ASN-1Step finds an unrecognized parameter for the -xer option.


S0023W

Message Format

S0023W: XSL/DTD files are ignored because '-encodeValue' is not specified.

Message Cause

This message is issued when ASN-1Step finds .xsl or .dtd files but the -encodeValue option is not specified, which indicates the value to encode.


S0024W

Message Format

S0024W: XSL/DTD files are ignored because selected encoding rules are not XER.

Message Cause

This message is issued when ASN-Step finds .xsl or .dtd files but the XER encoding rules are not in use.


S0025W

Message Format

S0025W: Input XSL/DTD files will be used for valuereference 'name'.

Message Cause

This message is issued when ASN-1Step finds .xsl or .dtd files that it can use when encoding a value with XER.


S0026E

Message Format

S0026E: Missing parameter in '-demo' option, specify 'Bcas' or 'PersonnelRecord'.

Message Cause

This message is issued when the -demo option is specified without a mandatory argument.


S0027E

Message Format

S0027E: Invalid parameter in '-demo' option, specify 'Bcas' or 'PersonnelRecord'.

Message Cause

This message is issued when the specified -demo option parameter is not one of the allowed parameters: Bcas or PersonnelRecord.


S0028E

Message Format

S0028E: The '-option' option is available only with the '-demo <Bcas|PersonnelRecord>' option in trial versions of ASN-1Step.

Message Cause

This message is issued when the -allEncode, -encodeValue, decodePdu, or -test runtime option is specified with the trial version of ASN-1Step. These options are available only in demo mode of the ASN-1Step trial version, that is, when the -demo option is also specified for one of the pre-defined syntaxes: Bcas or PersonnelRecord.


S0029I

Message Format

S0029I: The name 'prefix' specified in the '-output' option will be used as the file name prefix only for the first <re-encoding value|value notation>.

Message Cause

This informatory message is issued when ASN-1Step is used to encode (or re-encode) several values and the -output <prefix> option is specified. In this case, the name specified in the -output option will be used as the prefix of the filename created for the first value only.


S0030E

Message Format

S0030E: The file 'filename' does not contain a valid XER/CXER/EXER/texthexadecimal or text binary format encoding.

Message Cause

An error occurred when reading an encoding from a text file.


S0031W

Message Format

S0031W: The end of the file contains unencoded data.

Message Cause

This message is issued when the -decodePdu option is specified and the end of the input file contains extra data that ASN-1Step does not recognize as a valid concatenated PDU encoding starting point.


S0032E

Message Format

S0032E: Failed to set the structured types nesting limit to limit. Error code 'error_code': 'error description'.

Message Cause

This message is issued when ASN-1Step fails to set the nesting limit specified in -setNestingLimit for decoding SET and SEQUENCE types.


S0033E

Message Format

S0033E: Failed to set the constructed strings encoding nesting limit to limit. Error code 'error_code': 'error description'.

Message Cause

This message is issued when ASN-1Step fails to set the nesting limit specified in -stringNestingLimit for decoding constructed strings.


S0034E

Message Format

S0034E: Failed to determine the PDU identifier from the value notation in the 'textFileName' input file, use the '-encodeValue <pduId>,<fileName>' option.

Message Cause

This message is issued when the text file passed as a parameter to the -encodeValue option does not include value notation in the form

<valueName> <PduTypeName> ::= <value_notation>

from which ASN-1Step can determine the PDU identifier. You must specify the PDU identifier explicitly in the –encodeValue option.


S0035E

Message Format

S0035E: The 'textFileName' file contains at least one invalid value notation.

Message Cause

This message is issued when the text file passed as a parameter to the -encodeValue option does not include valid value notation.


S0036E

Message Format

S0036E: "filename", line num: Failed to parse the value notation. 'error description'.

Message Cause

This message is issued when ASN-1Step detects an error in the value notation in the text file passed as a parameter to the -encodeValue option. The error description is provided at the end of the error message.


S0037W

Message Format

S0037W: The flag flag in the '-keyword' option will be ignored because it implies all of the following: flag1, flag2 [, ...].

Message Cause

This message is issued when the name of the flag is specified by an ambigous prefix.


S0038W

Message Format

S0038W: The flag flag has no effect on <encoding|decoding> and will be ignored.

Message Cause

This message is issued when a decoder flag is specified for the encoder and when an encoder flag is specified for the decoder.


S0039I

Message Format

S0039I: CDR file header detected, skipping 'num' bytes: .

Message Cause

A CDR file header consisting of 50 or 54 bytes was detected and skipped before the first BER-based encoded message, which could include the CDR record header, was encountered. To suppress automatic detection of CDR headers, use the -noCDRHeadersDetection option.


S0040I

Message Format

S0040I: CDR record header detected, skipping 'num' bytes: .

Message Cause

A CDR record header consisting of 4 or 5 bytes was detected and skipped before decoding the BER-based encoded message. To suppress automatic detection of CDR headers, use the -noCDRHeadersDetection option.


S0041W

Message Format

S0041W: Although it was detected, the CDR file header was ignored because the value that was specifed with the -offset option (num1) is different from the value that was detected (num2).

Message Cause

ASN-1Step detected and ignored the CDR file header because the value specified with the -offset option is different from the value that was detected.


S0042W

Message Format

S0042W: Although it was detected, the CDR record header was ignored because the value that was specified with the -recordOffset option (num1) is different from the value that was detected (num2).

Message Cause

ASN-1Step detected and ignored the CDR record header because the value specified with the -recordOffset option is different from the value that was detected.


S0043W

Message Format

S0043W: Unsupported value 'num1' found in the 'Data record format' field of the CDR record header, skipping num2 bytes: <skipped_bytes>.

Message Cause

ASN-1Step failed to determine the encoding rules that should be used to decode the CDR record because the values of the Data Record Format field of the CDR record header do not correspond to any of the following supported encoding rules: BER, Aligned or Unaligned PER, or XER. The record is skipped.


S0044W

Message Format

S0044W: No CDR headers detected in the file 'fileName', attempting decoding using BER...

Message Cause

ASN-1Step failed to determine the CDR headers in the .cdr input file. An attempt is made to decode the file using the Basic Encoding Rules.


S0045E

Message Format

S0045E: A PDU identifier must be specified when decoding using PER, UPER, OER, C-OER, or JSON rules.

Message Cause

This message is issued when the -decode option is specified with an invalid PDU type identifier or with a 0-PDU number and the PER, UPER, OER, C-OER, or JSON rules.


ASN-1Step/IAAPI Messages Related to CSV Conversion

IA078E

Message Format

IA078E: The CSV format or header format is not correct: 'error string'.

Message Cause

The input CSV header or value record structure contains an error. The input format might not correspond to the specified PDU type structure. 'error string' shows the place in the input buffer where the error occurred.


IA079E

Message Format

IA079E: An incorrect name is found inside the CSV header: 'error string'.

Message Cause

The CSV header contains a name that does not conform to the PDU type structure. 'error string' shows the place in the input buffer where the error occurred.


IA080E

Message Format

IA080E: The column separator does not match the specified or the determined one: 'error string'.

Message Cause

A character specified where the column separator is expected is different from the previously detected separator. 'error string' shows the place in the input buffer where the error occurred.


IA081E

Message Format

IA081E: The CSV structure is not correct: 'error string'.

Message Cause

The input CSV is structurally incorrect per the specified PDU type structure. 'error string' shows the place in the input buffer where the error occurred.


IA082E

Message Format

Unexpected end of the CSV buffer encountered: 'error string'.

Message Cause

The end of the CSV buffer was reached, but more values are expected per the specified PDU type structure. 'error string' shows the place in the input buffer where the error occurred.


IA083E

Message Format

IA083E: Values of circular types are not supported without a structured CSV header.

Message Cause

The input PDU type is recursively defined and is instantiated more than once. In this case, the full CSV header should be present to identify duplicate fields of multiple recursions.


IA084E

Message Format

IA084E: Unsupported CSV column separator: 'separator'.

Message Cause

The specified column separator is not supported. The following column separators are currently supported: ',', ';', ':', '='.


IA085E

Message Format

IA085E: Unsupported CSV header separator: 'separator'.

Message Cause

The specified header separator is not supported. The following header separators are currently supported: '-', '_', '.', '/', '\\'.


IA086E

Message Format

IA086E: Values of open types are not supported without a structured CSV header.

Message Cause

The specified PDU type includes an open type, but the input CSV does not include the full CSV header with special syntax for open types (the nested PDU type names or numbers are enclosed in parentheses). In this case, the decoder cannot determine the CSV structure.


IA087E

Message Format

IA087E: Failed to convert OCTET STRING value to/from BCD: 'error string'.

Message Cause

The –csv bcd option is specified or the OSS.PrintFunctionName directive with "ossPrintOctetAsBCDString" is applied to one or more OCTET STRING types, but one or more OCTET STRING values could not be converted to or from BCD. 'error string' shows the place in the input buffer where the error occurred.


IA088E

Message Format

IA088E: Failed to convert OCTET STRING value to/from TBCD: 'error string'.

Message Cause

The –csv tbcd option is specified or the OSS.PrintFunctionName directive with "ossPrintOctetAsTBCDString" is applied to one or more OCTET STRING types, but one or more OCTET STRING values could not be converted to or from TBCD. 'error string' shows the place in the input buffer where the error occurred.


IA089E

Message Format

IA089E: Failed to convert OCTET STRING value to/from ASCII: 'error string'.

Message Cause

The –csv ascii option is specified or the OSS.PrintFunctionName directive with "ossPrintOctetAsASCII" is applied to one or more OCTET STRING types, but one or more OCTET STRING values could not be converted to or from ASCII. 'error string' shows the place in the input buffer where the error occurred.


IA090E

Message Format

IA090E: Failed to convert OCTET STRING value to/from IP address: 'error string'.

Message Cause

The OSS.PrintFunctionName directive with "ossPrintOctetAsIPAddress" is applied to one or more OCTET STRING types, but one or more OCTET STRING values could not be converted to or from an IP address. 'error string' shows the place in the input buffer where the error occurred.


IA091E

Message Format

IA091E: Failed to convert OCTET STRING value to/from time stamp string: 'error string'.

Message Cause

The OSS.PrintFunctionName directive with "ossPrintOctetAsTimeStamp" is applied to one or more OCTET STRING types, but one or more OCTET STRING values could not be converted to or from time stamp. 'error string' shows the place in the input buffer where the error occurred.



This documentation applies to release 8.2 and later of ASN-1Step®. For earlier versions, consult the PDF manual available in your product installation.

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 ASN-1Step is associated with a specific license and related unique license number. That license determines, among other things, what functions of ASN-1Step are available to you.