Ukraine We stand with Ukraine

TOP
home | Overview | Classes and Methods | Return Codes | Runtime Errors | Advanced Topics | Program Examples

ASN.1/C++ Runtime Errors

Applies to: ASN.1/C++ v7.3

The ASN.1/C++ Compiler and runtime routines can both generate error and informatory messages. Use these error messages to help pinpoint problems in your ASN.1 syntax or application code.

Go directly to the Runtime Error Reference to look up OSS ASN.1 Runtime error messages by message number.

Format

Each message has a unique code. This message code consists of six characters: the first identifies the OSS ASN.1 Tools component that issued the message, next is a four-digit message number, and the last indicates the severity level of the message. See the following table for more details:

Character Position
in Message Code		 Purpose Possible Characters Description
First Component Identifier 
D

E

R
 
Decoder routines

Encoder routines

Messages relating to trial versions and license restrictions.
Second through Fifth Message Number 0001 to 9999 Unique, four-digit message ID number
Sixth Error Severity 
I




E



S
 
Informatory message (Level 0)
Level 0 messages provide additional information; 
no error is indicated.


Regular error message (Level 2)
A Level 2 message indicates that an error occurred; 
however, the current process continues.

Severe error message (Level 3)
A Level 3 message indicates that an error occurred; 
processing stops immediately.

Example

The D0263E error code contains the following information:

  • The letter D states that the message is issued by the ASN.1 decoder.
  • 0263 is the message number. Use this number to look up the message details.
  • The letter E indicates that this message is a Level 2 error, which refers to regular or common errors.

Format of Runtime Function Signal Messages

Error message format

Typical runtime function signal message

A typical XER encoding error message also contains the line number and position of the error occurrence, as shown in the following example:

D0174E: Canonical XER restrictions are violated: 'XML encoding for contained types should have 
been used'; check field 'content' (type: BIT STRING) of PDU #1 'DataPacket' at line 1 position 4.

A runtime function message can also have fewer details, depending on the encoder/decoder and the debug options used.

Runtime Error Reference

Go to the Runtime Error Reference to look up OSS ASN.1 runtime error messages by message number. You can also call the getErrorMsg() method of the OssControl class to retrieve a detailed error message after an error code is returned by the encoder, decoder, or other API method.

This documentation applies to release 7.3 and later of the OSS® ASN.1 Tools for C++.

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 for C++ 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 for C++ are available to you.