Error building asn 1 representation can t build oid for variable

blog.simpnet.org

Блог компании Симпнет

Архив рубрики: Debian

Proxmox VE: восстановление кластера после смены ip-адресов

Если по какой-то причине пришлось сменить ip-адреса у серверов кластере и кластер не поднялся, то делаем следующие: Читать далее →

Установка YouTrack для java 7 в Linux Ubuntu (Debian)

В связи с тем, что описание установки на официальном сайте у меня не заработало, решил записать как я его запустил, может кому пригодиться. Читать далее →

Zabbix SNMP — Error building asn.1 representation

При установке Zabbix на Debian 6, может возникнуть следующая ошибка SNMP:

Error building asn.1 representation Читать далее →

Установка Zabbix-agent 2.0 в Debian 7 и Ubuntu 12.04

Установка пакета конфигурации репозитария

Установите пакет конфигурации репозитария. Этот пакет содержит apt файлы конфигурации. Читать далее →

Установка Oracle Java 7 в Ubuntu 11.10/12.04/12.10 и Debian 7

Если вам действительно нужно использовать Oracle Java вместо OpenJDK в Ubuntu, то вот простой способ сделать это: Читать далее →

Установка sun-java6-jdk и sun-java6-jre на Ubuntu 12.04

Установка sun-java6-jdk и sun-java6-jre на Ubuntu 12.04 Читать далее →

Настройка USBIP

1. Установка и компиляция
Устанавливаем необходимые пакеты Читать далее →

Источник

Tag Archives: zabbix

После установки zabbix-proxy на CentOS 6, все icmpping / icmppingsec элементы возвращали нулевые зеачения.

После включения DEBUG режма, лог Zabbix показал следующее:

31790:20140611:073610.004 In process_ping() hosts_count:1
31790:20140611:073610.004 /tmp/zabbix_proxy_31790.pinger
31790:20140611:073610.004 10.20.2.20
31790:20140611:073610.004 /usr/sbin/fping -C5 -p200 -b1024 -t1000 2>&1 Tags: zabbix Posted by BackTrack in Линукс on 11 июня, 2014

Компиляция PHP для интерфейса Zabbix 2.2

Для компиляции PHP для интерфейся Zabbix 2.2+ необходимо использовать следующие параметры:

Минимальные параметры в файле php.ini :

Сохранение базы конфигурации Zabbix

Ниже приведен скрипт для бэкапа конфигурации Zabbix 2 (содержит данны о хостах, элементах, шаблонах итд). Данные мониторинга (история, тренды, события) не включены в архив, что делает его размер относительно небольшим.

Просто замените ZBX_DB и ZBX_USER на свои параметры базы данных:

Zabbix SNMP — Error building asn.1 representation

При установке Zabbix на Debian 6, может возникнуть следующая ошибка SNMP:

Error building asn.1 representation

Для выяяснени причины запустите snmpget

Если вы получили такую же ошибку, в системе не установлен пакет snmp-mibs-downloader.

Для его установки используйте менеджер пакетов apt:

После этого перезапустите zabbix-server

Темплейт Zabbix2 для мониторинга CheckPoint по SNMP

Я создал шаблон Zabbix 2.x для мониторинга CheckPoint продуктов через SNMP.

Этот шаблон использует CheckPoint MIB, который находятся на SecurePlatform OS в папке $CPDIR/lib/SNMP/

Вы должны скопировать этот файл на сервер Zabbix, в каталог /usr/share/snmp/mibs
Для проверки новых MIB-ов, можно запустить команду snmpget следующим образом:

Эта команда должна вернуть версию продукта: iso.org.dod.internet.private.enterprises.checkpoint.products.svn.svnInfo.svnVersion.0 = STRING: «. R75.40»

Вот ссылки для загрузки шаблонов:

Темплейт SNMPv2 связан со стандартными Zabbix шаблонами: Template SNMP Device и Template SNMP Disks .

Темплейт SNMPv3 связан с Zabbix SNMPv3 Темплейтами : Template SNMPv3 Device и Template SNMPv3 Disks.

Источник

Several issues encountered during building an application #254

Thanks for adding OER encoding/decoding to your ASN.1 C compiler. I am trying to compile and use the following ASN.1 code: https://github.com/certificationoperatingcouncil/TCI_ASN1/tree/master/TCI%20Interface/ASN1 .

I compiled the ASN.1 code with the following switches: asn1c -no-gen-example -fincludes-quoted -no-gen-PER -fcompound-names -gen-OER , I encountered a few problems, I am trying to summarize below:

1- The includes-quoted switch was not honored, the header files were included using brackets which caused compile errors, I had to manually edit them;

2- I tried to compile the generated C files, all the files compiled except for 1, I got an error when compiling the Extensions.c file. I think the correct definition for the RepeateRate should be asn_DEF_IEEE_1609_3_WEE_RepeatRate not asn_DEF_RepeatRate. I see that RepeatRate is defined in 2 different ASN.1 files and that was probably the source of confusion. I edited the file and it compiles now. You can find the generated code here: https://drive.google.com/drive/folders/1plZNimFkQyV4rsibpgM9-6I8GROCmOLz ;

3- Now to building an application, I was using CodeBlocks with WxWidgets to write a Linux application similar to this Windows application (I am the author of this application): https://github.com/certificationoperatingcouncil/TCI_Tools/tree/master/TCI_Msg_Generator_Portable/V1.14. Using g++ created so many errors, I resorted to building a static library of the generated code and linking with it, that worked;

4- I encountered A problem with the CodeBlocks, so I switched to creating a Visual Studio 2015 C project to utilize its excellent debugging capabilities. I selected a very simple command to test the application and try to understand how to use the generated C code, this command is RequestSutInfo which includes a Boolean value, here is the code:

// SUT Control
#include «SutInfo.h»
#include «RequestSutAvailability.h»
#include «RequestSutInfo.h»
#include «Restart.h»
#include «Shutdown.h»
#include «TCIMsg.h»
#include «NativeInteger.h»
#include «Time64.h»
#include «Frame.h»
#include «constr_SEQUENCE.h»
#include «TCISutControl.h»
#include

int main (int argc, const char* argv[])
<
OnRequestSutInfoBClick();
>

void OnRequestSutInfoBClick()
<
TCIMsg_t pdu;
Frame_t frame;
TCISutControl_t sutControl;
TCI_SutControl_Request_t request;
RequestSutInfo_t requestSutInfo;
asn_struct_ctx_t asn_ctx;
Time64_t timeNow;

sutControl.present = TCISutControl_PR_request;
sutControl.choice.request = request;
sutControl._asn_ctx = asn_ctx;

// Frame
frame.present = Frame_PR_sutCtrl;
frame.choice.sutCtrl = sutControl;
frame._asn_ctx = asn_ctx;

/*
boost::asio::io_service io_service;
UDPClient client(io_service, «localhost», «13001»);
client.send(message, er.encoded);
*/
>

5- When I run this code, the asn_check_constraints function returns an error “value too large” for the time value which is a 64bit value. I traced this error to the fact that the code in function asn_INTEGER2long in INTEGER.c file does not take the integer size in its consideration and assumes that it is 4 bytes only (it is checking against LONG_MIN and LONG_MAX and it should be checking against LLONG_MIN and LLONG_MAX);

6- I also get an error when encoding the pdu and it doesn’t matter if I use asn_encode_to_buffer or oer_encode_to_buffer, the error relates to Request, this one I couldn’t determine what was wrong.

The text was updated successfully, but these errors were encountered:

Источник

Runtime Error Reference

D0001S

Message Format

D0001S: Output buffer too small; total bytes requested:

Message Cause

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

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

Possible Solution

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

E0001S

Message Format

E0001S: Output buffer too small; total bytes requested:

Message Cause

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

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

Possible Solution

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

D0002S

Message Format

Message Cause

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

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

Possible Solution

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

E0002S

Message Format

Message Cause

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

Possible Solution

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

D0003S | E0003S

Message Format

Message Cause

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

Possible solutions

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

D0004S | E0004S

Message Format

Message Cause

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

Possible Solution

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

D0005S | E0005S

Message Format

Message Cause

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

Possible Solution

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

D0006S | E0006S

Message Format

Message Cause

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

Possible Solutions

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

D0007S | E0007S

Message Format

Message Cause

This error can occur in any of these situations:

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

Possible Solutions

• 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.
• Make sure you link your application with either the SOED or TOED library, but not both.

D0008S | E0008S

Message Format

Message Cause

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

Possible Solution

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

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

E0009S

Message Format

Message Cause

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

Possible Solutions

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

D0009S

Message Format

Message Cause

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

Possible Solution

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

D0010S | E0010S

Message Format

Message Cause

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

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

Possible Solution

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

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

E0011S

Message Format

Message Cause

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

Possible Solutions

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

This error can also occur when

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

D0012S | E0012S

Message Format

Issued By

All encoders and decoders.

Message Cause

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

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

Possible Solution

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

D0013S | E0013S

Message Format

Message Cause

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

Possible Solution

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

D0014S | E0014S

Message Format

Message Cause

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

Possible Solutions

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

D0015E

Message Format

Message Cause

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

Possible Solution

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

D0016S | E0016S

Message Format

Message Cause

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

Example

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

Possible Solutions

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

D0017E | E0017E

Message Format

Message Cause

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

Possible Solution

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

D0018E

Message Format

Message Cause

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

Possible Solution

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

D0019E

Message Format

Message Cause

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

Possible Solution

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

D0020E

Message Format

Message Cause

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

Possible Solution

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

D0021E

Message Format

Message Cause

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

Possible Solution

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

D0022E

Message Format

Message Cause

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

Possible Solutions

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

D0023E

Message Format

Message Cause

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

Possible Solution

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

D0024E

Message Format

Message Cause

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

Possible Solution

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

D0025E

Message Format

Message Cause

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

Possible Solution

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

D0026S | E0026S

Message Format

Message Cause

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

Possible Solutions

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

D0027S

Message Format

Message Cause

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

Possible Solution

Change the representation of the size field.

D0028E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0029E | E0029E

Message Format

Message Cause

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

Possible Solutions

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

D0030S | E0030S

Message Format

Message Cause

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

Possible Solution

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

D0031S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0032E

Message Format

Message Cause

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

Possible Solution

Reduce the number of extension additions.

D0033E

Message Format

Message Cause

This error has three common causes:

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

Possible Solution

Check the encoding application for errors.

D0034E

Message Format

Message Cause

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

Possible Solution

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

D0035E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0036E | E0036E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0037E | E0037E

Message Format

Message Cause

The encoder/decoder found one of the following abnormalities:

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

Possible Solutions

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

D0038E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0039E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0040E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0041E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0042E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0043E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0044E

Message Format

Message Cause

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

Possible Solution

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

D0045E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0046E

Message Format

Message Cause

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

Possible Solution

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

Example

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

D0047E

Message Format

Message Cause

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

Possible Solutions

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

D0048E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0049E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0050S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0051S

Message Format

Message Cause

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

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

Possible Solution

Check the encoding application for errors.

D0052S

Message Format

Message Cause

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

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

Possible Solution

Check the encoding application for errors.

D0053S

Message Format

Message Cause

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

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

Possible Solution

Check the encoding application for errors.

D0054S

Message Format

Message Cause

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

Possible Solutions

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

x0055E

This error code is currently not in use.

D0056S

Message Format

Message Cause

The decoder encountered an unknown exception error.

Possible Solution

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

D0057S

Message Format

Message Cause

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

Possible Solutions

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

D0058E

Message Format

Message Cause

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

Possible Solution

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

D0059E

Message Format

Message Cause

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

Possible Solution

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

D0060S | V0060S

Message Format

Message Cause

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

Possible Solutions

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

D0061S | V0061S

Message Format

Message Cause

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

Possible Solutions

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

D0062S | V0062S

Message Format

Message Cause

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

Possible Solutions

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

D0063S | E0063S | V0063S

Message Format

Message Cause

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

Possible Solutions

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

D0064S | E0064S | V0064S

Message Format

Message Cause

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

Possible Solutions

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

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

D0065S | E0065S | V0065S

Message Format

Message Cause

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

Possible Solutions

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

D0066S | E0066S | V0066S

Message Format

Message Cause

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

Possible Solutions

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

D0067S | E0067S

Message Format

Message Cause

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

Possible Solution

Make sure that the open type was decoded correctly.

D0068S | E0068S | V0068S

Message Format

Message Cause

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

Possible Solution

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

D0069S | E0069S | V0069S

Message Format

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

Message Cause

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

Possible Solution

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

D0071S | E0071S

Message Format

Message Cause

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

Possible Solution

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

E0072E

Message Format

Message Cause

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

Possible Solution

Specify a non-zero length for the problematic field.

D0073S | E0073S

Message Format

Message Cause

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

Possible Solutions

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

D0074S | E0074S

Message Format

Message Cause

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

Possible Solutions

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

D0075S | E0075S

Message Format

Message Cause

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

Possible Solution

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

D0076S

Message Format

Message Cause

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

Possible Solutions

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

D0077S | E0077S

Message Format

Message Cause

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

Possible Solutions

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

D0078S | E0078S

Message Format

Message Cause

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

Possible Solution

Provide constraint-compliant input to the encoder/decoder.

D0079S | E0079S

Message Format

Message Cause

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

Possible Solution

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

D0080E

Message Format

Message Cause

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

Possible Solution

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

D0081S

Message Format

Message Cause

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

Possible Solution

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

D0083S | E0083S

Message Format

Message Cause

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

Possible Solution

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

D0084S | E0084S

Message Format

Message Cause

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

Possible Solution

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

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

D0085S | E0085S

Message Format

Message Cause

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

Possible Solution

Increase your application stack size.

D0086S | E0086S

Message Format

Message Cause

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

Possible Solutions

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

D0087S | E0087S

Message Format

Message Cause

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

Possible Solutions

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

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

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

D0089E | E0089E

Message Format

Message Cause

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

Possible Solutions

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

D0090E | E0090E

Message Format

Message Cause

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

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

Possible Solutions

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

D0091E | E0091E

Message Format

Message Cause

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

Possible Solution

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

D0092E | E0092E

Message Format

Message Cause

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

Possible Solution

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

D0093E | E0093E

Message Format

Message Cause

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

Possible Solution

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

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

x0094E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

x0095S

Message Format

Message Cause

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

Possible Solution

Increase your application stack size.

x0096S

This error code is currently not in use.

D0097S | E0097S

Message Format

Message Cause

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

Possible Solution

Increase your application stack size.

D0098S | E0098S

Message Format

Message Cause

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

Possible Solution

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

D0099E

Message Format

Message Causes

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

Possible Solutions

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

D0100S | E0100S

Message Format

Message Cause

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

Possible Solution

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

x0101x

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

x0102x

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

D0103S | E0103S

Message Format

Message Cause

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

Possible Solutions

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

D0104S | E0104S

Message Format

Message Cause

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

Possible Solution

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

D0105S | E0105S

This error code is currently not in use.

D0106S | E0106S

This error code is currently not in use.

D0107S | E0107S

Message Format

Message Cause

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

Possible Solution

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

D0109S | E0109S

Message Format

Message Cause

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

Possible Solution

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

D0110S | E0110S

Message Format

Message Cause

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

Possible Solution

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

D0111S | E0111S

Message Format

Message Cause

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

Possible Solution

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

D0112S | E0112S

Message Format

Message Cause

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

Possible Solution

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

D0113S | E0113S

Message Format

Message Cause

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

Possible Solution

Increase your application stack size.

D0114S | E0114S

This message number is currently not in use.

D0115S | E0115S

Message Format

Message Cause

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

Possible Solution

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

D0116S | E0116S

Message Format

Message Cause

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

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

D0117S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0118S | E0118S

Message Format

Message Cause

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

Possible Solution

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

D0119S | E0119S

Message Format

Message Cause

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

Possible Solutions

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

D0120S | E0120S

Message Format

Message Cause

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

Possible Solution

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

D0121E | D0121S | E0121E | E0121S

Message Format

Message Cause

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

Possible Solution

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

D0122S | E0122S

Message Format

Message Cause

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

Possible Solution

Check the encoding application or the transmission method for errors.

D0123S | E0123S

Message Format

Message Cause

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

Possible Solution

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

E0124S

Message Format

Message Cause

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

Possible Solution

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

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0125I

Message Format

Message Cause

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

Possible Solution

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

D0126S | E0126S | V0126S

Message Format

Message Cause

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

Possible Solution

Correct the value to comply with the subtype constraint.

D0127S | E0127S

Message Format

Message Cause

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

Possible Solution

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

D0128S | E0128S | V0128S

Message Format

Message Cause

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

Possible Solution

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

D0129S | E0129S

Message Format

Message Cause

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

Possible Solution

Store only numerical data in a REAL type representation.

D0130S | E0130S

Message Format

Message Cause

The Java Tools encoder/decoder encountered an internal error.

Possible Solution

D0131S | E0131S

Message Format

Message Cause

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

Possible Solution

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

D0132S

Message Format

Message Cause

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

Possible Solution

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

D0133S

Message Format

Message Cause

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

Possible Solution

D0134S | E0134S

Message Format

Message Cause

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

Possible Solution

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

D0135S | E0135S

Message Format

x0135S: Unrecoverable error

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

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

Message Cause

The runtime failed to validate your license.

Possible Solution

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

D0136E

Message Format

Message Cause

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

Possible Solutions

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

D0137E

Message Format

Message Cause

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

Possible Solutions

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

P0138S

Message Format

Message Cause

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

Possible Solution

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

x0139S

Message Format

Message Cause

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

Possible Solution

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

x0140S

Message Format

Message Cause

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

Possible Solution

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

E0141E

Message Format

Message Cause

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

Possible Solution

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

E0142E

Message Format

Message Cause

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

Possible Solution

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

E0143E

Message Format

Message Cause

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

Possible Solution

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

D0144E | E0144E

Message Format

Message Causes

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

Possible Solution

Check the encoding application for errors.

E0145E

Message Format

Message Cause

Possible Solution

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

E0146E

This error code is currently not in use.

D0147E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0148E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0149E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0150E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0151E

Message Format

Message Cause

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

Possible Solution

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

D0152E

Message Format

Message Cause

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

Possible Solution

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

D0153E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0154E

Message Format

Message Cause

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

Possible Solutions

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

D0155E

Message Format

Message Cause

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

Possible Solution

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

D0156E

Message Format

Message Cause

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

Possible Solutions

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

D0157E

Message Format

Message Cause

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

Possible Solutions

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

D0158E

Message Format

Message Cause

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

Possible Solutions

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

D0159E

Message Format

Message Cause

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

Possible Solutions

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

D0160E | E0160

Message Format

Message Cause

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

Possible Solution

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

D0161E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0162S | E0162S | V0162S

Message Format

Message Cause

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

Possible Solution

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

D0163S | E0163S

Message Format

Message Cause

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

Possible Solution

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

D0164S | E0164S

Message Format

Message Cause

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

Possible Solution

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

D0165S | E0165S

Message Format

Message Cause

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

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

Possible Solution

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

D0166E

Message Format

Message Cause

The decoder found an XER message containing an opening bracket (e.g., » D0167E: Invalid syntax for XML tag

Message Cause

The decoder found an XER message that has a tag with a syntax error, such as multiple front slashes in a closing tag (e.g., » «) or a missing closing angle bracket (e.g., » D0168E: Invalid XML tag name ‘name’

Message Cause

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

Possible Solution

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

D0169E

Message Format

Message Cause

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

Possible Solution

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

D0170E

Message Format

Message Cause

The XER decoder found an XML comment start token (» D0171E: Illegal XML escape sequence found

Message Cause

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

Possible Solution

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

D0172E

Message Format

Message Cause

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

Possible Solution

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

D0173E

Message Format

Message Cause

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

D0174E

Message Format

Message Cause

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

Example Messages

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) is not allowed at the beginning of the encoded data.

‘whitespace not allowed’

(9.1.2) No unnecessary white space characters are allowed.

‘invalid characters sequence’

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

’empty-element tag expected’

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

‘REAL zero must consist of single digit 0’

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

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

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

‘REAL value must contain capital E followed by exponent’

Clause 9.2.4 is violated.

‘REAL value may not contain plus sign(s)’

Clause 9.2.5 is violated.

‘no trailing zeroes allowed for this BIT STRING type’

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

‘default value encoding should have been present’

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

‘number form of OBJECT IDENTIFIER should have been used’

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

‘time type value must end with Z’

Clause 9.10.1 or 9.11.1 is violated.

‘seconds should have been present’

Clause 9.10.2 or 9.11.2 is violated.

‘invalid midnight representation’

Clause 9.10.5 or 9.11.3 is violated.

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

Clause 9.10.4 is violated.

‘seconds fraction should not contain trailing zeroes’

Clause 9.10.3 is violated.

‘XML encoding for contained types should have been used’

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

Possible Solutions

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

D0175E

Message Format

Message Cause

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

Possible Solution

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

D0176E

Message Format

Message Cause

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

Example

Incorrect XER encoding for this type:

Message for Example

Possible Solution

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

D0177E

Message Format

Message Cause

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

Possible Solution

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

E0178E

Message Format

Message Cause

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

Possible Solution

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

D0179E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0180E

Message Format

Message Cause

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

Possible Solution

Check encoding applications for errors.

D0181E

Message Format

Message Cause

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

Possible Solution

Check encoding applications for errors.

D0182E

Message Format

Message Cause

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

Possible Solution

Check encoding applications for errors.

E0183E

Message Format

Message Cause

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

Possible Solution

Contact OSS Nokalva Support to explain your requirements.

D0184E

Message Format

Message Cause

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

Possible Solution

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

D0185E

Message Format

Message Cause

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

Possible Solution

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

E0186S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported constraint.

D0187E

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0188E

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0189S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0190S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0191S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0192S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0193S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0194S

Message Format

Message Cause

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

Possible Solutions

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

D0195S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0196S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0197S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0198S

Message Format

Message Cause

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

Example

Message for Example

Possible Solutions

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

D0199S

Message Format

Message Cause

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

Possible Solutions

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

D0200S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0202S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0203S

Message Format

Message Cause

The EXTENDED-XER decoder encountered an incorrect DTD construct.

Possible Solution

Check the encoding application for errors.

D0204S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0205S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0206S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0207S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0208S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0209S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0210S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0211S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0212S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0213S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0214S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0215S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0216S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0217S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0218S

Message Format

Message Cause

The attribute was defined more than once.

Possible Solution

Check the encoding application for errors.

D0219S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0220S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0221S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0222S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0223S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0224S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0225S

Message Format

Message Cause

An unexpected character was encountered in the attribute encoding.

Possible Solution

Check the encoding application for errors.

D0227S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0228S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0229S

Message Format

Message Cause

An unknown attribute was encountered.

Possible Solution

Check the encoding application for errors.

D0230S

Message Format

Message Cause

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

Possible Solution

Check and correct the encoded value.

D0231S

Message Format

Message Cause

A syntactically incorrect URI value was encountered.

Possible Solution

Check and correct the encoded value.

D0232S

Message Format

Message Cause

A syntactically incorrect prefix value was encountered.

Possible Solution

Check the encoding application for errors.

D0233S

Message Format

Message Cause

A syntactically incorrect unprefixed name was encountered.

Possible Solution

Check and correct the encoded value.

D0234S

Message Format

Message Cause

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

Possible Solution

Check and correct the encoded value.

D0235S

Message Format

Message Cause

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

Example

Message(s) for Example

Possible Solution

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

D0236S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

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

D0237S

Message Format

Message Cause

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

Possible Solution

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

D0238S

Message Format

Message Cause

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

Possible Solution

Check and correct the encoded value.

D0239S

Message Format

Message Cause

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

Possible Solution

Check and correct the encoded value.

D0240S

Message Format

Message Cause

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

Possible Solution

Check and correct the encoded value.

D0241S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0242S | E0242S

Message Format

Message Cause

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

Possible Solution

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

D0243S

Message Format

Message Cause

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

Possible Solution

Check and correct the encoded value.

D0244S | E0244S

Message Format

Message Cause

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

Possible Solution

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

D0245E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0246S

Message Format

Message Cause

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

Possible Solution

Check and correct the encoded value.

D0247S

Message Format

Message Cause

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

• Absent attribute name
• Absent «=» sign
• Absent opening quote
• Absent matching closing quote
• Presence of non-whitespace characters after the closing quote

Possible Solution

Check and correct the encoded value.

D0248S

Message Format

Message Cause

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

Example

Message for Example

Possible Solution

Check the encoding application for errors.

D0249S

Message Format

Message Cause

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

Possible Solution

Check and correct the pre-encoded value.

D0250S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0251S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0252S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0253S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0254S | E0254S

Message Format

Message Cause

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

Possible Solution

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

D0255S | E0255S

Message Format

Message Cause

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

Possible Solution

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

D0256S

Message Format

Message Cause

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

Possible Solution

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

R0257E | R0257W

Message Format

Message Cause

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

Possible Solution

Execute your application on the same machine on which you ran the ASN.1 Compiler. 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.

Message Format

Message Cause

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

D0258E

Message Format

Message Cause

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

Possible solutions

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

D0259S

Message Format

Message Cause

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

Possible solution

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

D0260S / E0260E

Message Format

Message Cause

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.

Possible Solution

Check the encoding application for errors.

D0261S

Message Format

Message Cause

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

Possible Solutions

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

D0262S

Message Format

Message Cause

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

Possible Solution

Turn off the STRICT_ENCODING_DECODING runtime flag to suppress this error.

D0263E

Message Format

Message Cause

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

Possible Solutions

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

Example

With an incorrect encoding for the I PDU: 48FDE8

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

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

S PDU Message

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

D0325E

Message Format

Message Cause

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

Example

With an incorrect encoding for the U PDU:

Message for Example

Possible Solution

Check the encoding application for errors.

E0326S | D0326S | V0326S

Message Format

Message Cause

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

Possible Solution

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

E0327S | D0327S | V0327S

Message Format

Message Cause

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

Possible Solution

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

E0328S | D0328S | V0328S

Message Format

Message Cause

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

Possible Solution

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

E0329S | D0329S | V0329S

Message Format

Message Cause

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

Possible Solution

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

E0330E | D0330E | V0330S

Message Format

Message Cause

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

Messages for Example

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

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

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

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

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

Possible Solutions

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

D0331E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D0333E

Message Format

Message Cause

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

Possible Solution

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

D0334E | E0334E

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

V0334E

Message Format

Message Cause

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

Message for Example

Possible Solution

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

D0335E | E0335E

Message Format

Message Cause

The encoder/decoder detected one of the following problems:

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

Possible Solution

Check the encoding application for errors.

V0335E

Message Format

Message Cause

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

Message for Example

Possible Solution

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

D0336S

Message Format

Message Cause

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

Possible Solution

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

R0337S

Message Format

Message Cause

The check on your license failed.

Possible Solution

Contact info@oss.com for detailed information.

D0338S | E0338S

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0339S | E0339S

Message Format

Message Cause

The OSS memory manager cannot close the input file.

Example Message

Possible Solution

Check the permissions on the work and temporary directories.

D0340S | E0340S

Message Format

Message Cause

The OSS memory manager cannot open the output file.

Example Message

Possible Solution

Check the permissions on the work and temporary directories.

D0341S | E0341S

Message Format

Message Cause

The OSS memory manager cannot close the output file.

Example Message

Possible Solution

Check the permissions on the work and temporary directories.

D0342S | E0342S

Message Format

Message Cause

The OSS memory manager detected a file write error.

Example Message

Possible Solution

Check the permissions on the work and temporary directories.

D0342S | E0343S

Message Format

Message Cause

The OSS memory manager detected a file read error.

Example Message

Possible Solution

Check the permissions on the work and temporary directories.

D0344S | E0344S

Message Format

Message Cause

The OSS memory manager cannot open a temporary file.

Example Message

Possible Solution

Check the permissions on the work and temporary directories.

D0345S | E0345S

Message Format

Message Cause

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

Example Message

Possible Solution

Check the application for errors.

D0346S | E0346S

Message Format

Message Cause

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

Example Message

Possible Solution

Check the application for errors.

D0347S | E0347S

Message Format

Message Cause

The OSS memory manager detected a socket write error.

Example Message

Possible Solution

Check the application for errors.

D0348S | E0348S

Message Format

Message Cause

The OSS memory manager detected a socket read error.

Example Message

Possible Solution

Check the application for errors.

D0349S | E0349S

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0350S | E0350S

Message Format

Message Cause

The socket DLL does not provide the required functions.

Example Message

Possible Solution

Check that the correct socket DLL is used.

D0351S | E0351S

Message Format

Message Cause

The OSS memory manager detected an invalid socket handle.

Example Message

Possible Solution

Check the application for errors.

D0352S | E0352S

Message Format

Message Cause

The timeout expired while writing to the socket.

Example Message

Possible Solution

Check the application for errors.

D0353S | E0353S

Message Format

Message Cause

The timeout expired while reading from the socket.

Example Message

Possible Solution

Check the application for errors.

D0354S | E0354S

Message Format

Message Cause

The OSS memory manager detected an unknown marked memory object.

Example Message

Possible Solution

Check the application for errors.

D0355S

Message Format

Message Cause

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

Example Message

Possible Solution

Check the encoding application for errors.

D0356S

Message Format

Message Cause

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

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

Example Message

Possible Solution

Check the encoding application for errors.

D0357S

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0358S

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0359S

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0360S | E0360S

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0361S

Message Format

Message Cause

An unexpected token was encountered.

Example Message

D0361S: Unknown token found, expecting’>’ or ‘»‘.

D0361S: Unknown token found, expecting ‘<‘.

Possible Solution

Check the JSON encoding and add the expected token.

D0362S

Message Format

Message Cause

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

Example Message

Possible Solution

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

D0363S

Message Format

Message Cause

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

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

Example Message

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

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

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

Possible Solution

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

D0364S

Message Format

Message Cause

The JSON decoder encountered an invalid encoding of ‘item’.

Example Message

D03654S: Invalid encoding of hexadecimal string.

D03645S: Invalid encoding of JSON number.

D03645S: Invalid encoding of BIT STRING.

Possible Solution

Check the encoding application for errors.

D0365S

Message Format

Message Cause

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

Example Message

Possible Solution

Check the encoding application for errors.

D0366S

Message Format

Message Cause

The decoder encountered some inconsistency in the input JSON encoding.

Example Message

D0366S: Unknown token.

D0366S: Illegal surrogate pair.

D0366S: Illegal escape sequence.

Possible Solution

Check the encoding application for errors.

D0367S

Message Format

Message Cause

The JSON encoder encountered an invalid Unicode character value.

Example Message

Possible Solution

Check the input value.

D0368S

Message Format

Message Cause

The PDU could not be decoded because the -encodeOnly compiler option is specified or the OSS.ENCODEONLY directive is applied to the PDU.

Example Message

Possible Solution

Make sure that the -encodeOnly compiler option is not specified and the OSS.ENCODEONLY directive is not applied to the PDU.

E0369S

Message Format

Message Cause

The PDU could not be encoded because the -decodeOnly compiler option is specified or the OSS.DECODEONLY directive is applied to the PDU.

Example Message

Possible Solution

Make sure that the -decodeOnly compiler option is not specified and the OSS.DECODEONLY directive is not applied to the PDU.

D0370S / E0370S

Message Format

Message Cause

The Canonical PER encoder/decoder detected that the SET OF ASN.1 type is used. However, this type is currently not supported.

Possible Solution

Don’t use the SET OF type with Canonical PER. Consider using SEQUENCE OF instead of SET OF.

D0371S

Message Format

Message Cause

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.

Possible Solution

Check the encoding application for errors, remove the OSS.NODECODE directive, or ASN.1 recompile without the -compactNoDecode option.

D0372S

Message Format

Message Cause

The CHOICE value to be encoded contains an alternative marked with the OSS.NOENCODE directive.

Possible Solution

Check the encoding application for errors or remove the OSS.NOENCODE directive.

D0373S

Message Format

Message Cause

The ossBinary2XML() , ossXML2Binary() , ossBinary2JSON() , and ossJSON2Binary() OSS API functions perform the conversion by decoding and then re-encoding the input message. If, at decoding stage, an open type or contents constrained type is left undecoded, the conversion cannot be performed, for instance, when component relation constraints cannot be resolved for an extensible open type, when the OSS.NoConstrain compiler directive is applied to an open type or contents constrained type, or when you use the TOED library without specifying the -autoencdec and -constraints options at ASN.1 compile time.

Possible Solution

Make sure that the input message can be fully decoded.

D0375E

Message Format

The ossPrintPDU() function encountered an inconsistency in the input PDU value.

Example Message

Possible Solution

Check the input PDU value for errors.

E0376S

Message Format

Message Cause

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.

Possible Solution

Make sure that the input message is fully decoded.

Lean Runtime-Specific Messages

D1001S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

E1002S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

D1003S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

E1004S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

D1005S

Message Format

Message Cause

The requested BER decoder is not linked or initialized.

Possible Solution

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

E1006S

Message Format

Message Cause

The requested BER encoder is not linked or initialized.

Possible Solution

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

D1007S

Message Format

Message Cause

The requested PER decoder is not linked or initialized.

Possible Solution

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

E1008S

Message Format

Message Cause

The requested PER encoder is not linked or initialized.

Possible Solution

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

D1009S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

E1010S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

D1011S

Message Format

Message Cause

The requested XER decoder is not linked or initialized.

Possible Solution

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

E1012S

Message Format

Message Cause

The requested XER encoder is not linked or initialized.

Possible Solution

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

D1013S

Message Format

Message Cause

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

Possible Solution

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

E1014S

Message Format

Message Cause

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

Possible Solution

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

D1015S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

E1016S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

D1017S | E1017S

Message Format

Message Cause

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

Possible Solution

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

D1018S | E1018S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D1019S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

E1020S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

D1021S

Message Format

Message Cause

The requested OER decoder is not linked or initialized.

Possible Solution

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

E1022S

Message Format

Message Cause

The requested OER encoder is not linked or initialized.

Possible Solution

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

D1023S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

E1024S

Message Format

Message Cause

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

Possible Solution

Remove the unsupported representation from the ASN.1 input.

D1025S

Message Format

Message Cause

The requested JSON decoder is not linked or initialized.

Possible Solution

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

E1026S

Message Format

Message Cause

The requested JSON encoder is not linked or initialized.

Possible Solution

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

D1027S

Message Format

Message Cause

An unexpected token was encountered.

Possible Solution

Check the JSON encoding and add the expected token.

D1028S

Message Format

Message Cause

The decoder encountered an escape sequence that is not valid.

Possible Solution

Check the encoding application for errors.

D1029S

Message Format

Message Cause

The decoder encountered a surrogate pair that is not valid.

Possible Solution

Check the encoding application for errors.

D1030S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D1031S

Message Format

Message Cause

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

Possible Solution

Check the encoding application for errors.

D1032S | E1032S

Message Format

Message Cause

The Lean encoder/decoder found that the requested canonical encoding rule is not available.

Possible Solution

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 © 2022 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.

Источник

Hi,=20

I'm working on Project where we use Net-SNMP, we've wrotten a small
Subagent which informs about our Server status. Some time ago we did
switch from ucd-snmp to Net-SNMP.=20
We use our Subagent to send traps througth Net-SNMP. The problem is, at
some time (unknow) wan't the Net-SNMP send no traps more, in logs look
it different somteimes send 300 Traps sometime just 100. In our Agent I
did't found any problem, in log of net-snmp can i see this messages (see
below).
I have no idea what ca it be. Please help, I'm using Net-SNMP 5.2.4 and
5.4 on Linux and Net-SNMP is started with following parameters:

	./sbin/snmpd -d -LF d /var/log/net-snmpd.log -p
/var/run/snmpd.pid -x /var/agentx/master=20

Error which can I see in log of net-snmp:

snmp_build: unknown failuresnmpd: send_trap: Error building ASN.1
representation (Can't build OID for variable)

Sending 300 bytes to Local IPC: /var/agentx/master
0000: 01 12 00 00  06 00 00 00  00 00 00 00  59 3A B5 05
............Y:..
0016: 18 01 00 00  7D B8 0B 00  00 00 00 00  43 00 00 00
....}.......C...
0032: 04 02 00 00  01 00 00 00  01 00 00 00  03 00 00 00
................
0048: 00 00 00 00  7C B8 0B 00  06 00 00 00  06 06 00 00
....|...........
0064: 03 00 00 00  01 00 00 00  01 00 00 00  04 00 00 00
................
0080: 01 00 00 00  00 00 00 00  05 04 01 00  01 00 00 00
................
0096: 88 1F 00 00  04 00 00 00  00 00 00 00  AA 3A 0C 00
.............:..
0112: 04 00 00 00  03 00 00 00  03 00 00 00  01 00 00 00
................
0128: 00 00 00 00  05 00 00 00  4F 35 30 30  41 00 00 00
........O500A...
0144: 04 00 00 00  03 00 00 00  03 00 00 00  02 00 00 00
................
0160: 00 00 00 00  15 00 00 00  4F 35 30 30  41 2E 30 30
........O500A.00
0176: 32 32 2E 30  30 30 31 31  36 30 35 30  33 00 00 00
22.0001160503...
0192: 04 00 00 00  03 00 00 00  03 00 00 00  03 00 00 00
................
0208: 00 00 00 00  0E 00 00 00  43 41 4C 4C  2E 53 4E 4D
........CALL.SNM
0224: 50 2E 54 45  53 54 00 00  04 00 00 00  03 00 00 00
P.TEST..........
0240: 03 00 00 00  04 00 00 00  00 00 00 00  11 00 00 00
................
0256: 45 69 6E 20  53 4E 4D 50  20 54 65 73  74 20 2E 2E    Ein SNMP
Test ..
0272: 2E 00 00 00  02 00 00 00  03 00 00 00  03 00 00 00
................
0288: 08 00 00 00  00 00 00 00  6C 07 00 00                 ........l...

For generating the Trap i'm using following steps (found in some
example):=20

	struct variable_list *list=3DNULL;
=09
	...
	snmp_varlist_add_variable(&list, (oid*)id, oid_length,
ASN_(depends, INTEGER or STRING), (unsigned char*)var.value, var.len);
	...=20
=09
	send_trap_vars(SNMP_TRAP_ENTERPRISESPECIFIC, code, list);

	snmp_free_varbind(list);

Thanks, peter

PS: any input is welcome


UC4 Software GmbH, Hauptstrasse 3C, 3012 Wolfsgraben =
Firmenbuchnummer/Commercial Register No. 63566f =
Firmenbuchgericht/Commercial Register Court: Landesgericht St. Poelten
This email (including any attachments) may contain information which is =
privileged, confidential, or protected. If you are not the intended =
recipient, note that any disclosure, copying, distribution, or use of =
the contents of this message and attached files is prohibited. If you =
have received this email in error, please notify the sender and delete =
this email and any attached files.

Trying to query a ton of devices with a simple output (in this test case; model identification)

Script file named «get«:

#!/bin/bash

model="$(snmpbulkget -r1 -t1 -v2c -c test_comm $1 1.3.6.1.2.1.47.1.1.1.1.13 | grep -m1 STRING | sed 's/.*://' | sed 's/ "//' | sed 's/"//')" &&
echo "$1,$model"

Using a single test; works with no issue:

./get 10.23.50.117
10.23.50.117,N9K-C93108TC-EX

Trying to parallelize (even with just 10 processes):

xargs -d " " -P 10 --arg-file=check ./get
snmp_build: unknown failure
snmpbulkget: Error building ASN.1 representation (Can't build OID for variable)

Using the -L arg flag in xargs causes each IP in the list to be hit 10x instead of 10 IPs once each.

cat check_out | sort
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1

#!/bin/bash

model="$(snmpbulkget -r1 -t1 -v2c -c test_comm $1 1.3.6.1.2.1.47.1.1.1.1.13 | grep -m1 STRING | sed 's/.*://' | sed 's/ "//' | sed 's/"//')" &&
echo "$1,$model"

./get 10.23.50.117
10.23.50.117,N9K-C93108TC-EX

xargs -d " " -P 10 --arg-file=check ./get
snmp_build: unknown failure
snmpbulkget: Error building ASN.1 representation (Can't build OID for variable)

cat check_out | sort
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.1,NY-SW1
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.12.0.4,NY-SW2
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1
10.14.14.8,CY-WAN-SW1

1 ответ

Лучший ответ

% ./get 10.201.0.110
10.201.0.110,..System Bootstrap, Version 11.0(10c), SOFTWARE..Copyright (c) 1986-1996 by cisco Systems..

% ./get 10.1.120.142
10.1.120.142,BOOT_NORMAL

% cat check
10.201.0.110
10.1.120.142 

% xargs -L 1 -P 10 --arg-file=check ./get
10.201.0.110,..System Bootstrap, Version 11.0(10c), SOFTWARE..Copyright (c) 1986-1996 by cisco Systems..
10.1.120.142,BOOT_NORMAL

Moderators: Developers, Moderators

Data Source Path: <path_rra>/bigip_a6_vsconnections_385.rrd
Index Value:     7.117.97.116.95.119.119.119

 snmpwalk -v 2c -c public 172.17.1.12 7.117.97.116.95.119.119.119
netsnmp_assert pss->s_snmp_errno != (-11) failed snmp_api.c:3124 snmp_build()
snmpwalk: Error building ASN.1 representation (Can't build OID for variable)

[[email protected]:/var/www/cacti/log]# snmpwalk -v 2c -c public 172.17.1.12 .1.3.6.1.4.1.3375.2.2.10.2.3.1.12.18.119.119.119.46.103.115.45.119.97.114.114.97.110.116.115.46.100.101
SNMPv2-SMI::enterprises.3375.2.2.10.2.3.1.12.18.119.119.119.46.103.115.45.119.97.114.114.97.110.116.115.46.100.101 = No Such Object available on this agent at this OID
[[email protected]:/var/www/cacti/log]# snmpwalk -v 2c -c public 172.17.1.11 .1.3.6.1.4.1.3375.2.2.10.2.3.1.12.18.119.119.119.46.103.115.45.119.97.114.114.97.110.116.115.46.100.101
SNMPv2-SMI::enterprises.3375.2.2.10.2.3.1.12.18.119.119.119.46.103.115.45.119.97.114.114.97.110.116.115.46.100.101 = Counter64: 0

Hi, I have a Problem with my nagios 4.3.4 (Raspbian)

I want to check for example the WAN-IP of My Router. Its an Lancom 1781AW

I have configured the Switch.cfg File as follows:

Code: Select all

define service{
use generic-service ; Inherit values from a template
host_name GM-PS
service_description WAN IP
check_command check_snmp!-C public -o .1.3.6.1.4.1.2356.11.1.4.13.1.1.3 -m all

}

The MIB File is located : /usr/share/snmp/mibs

the nagios web interface service shows:

CRITICAL — Plugin timed out while executing system call

I have check_snmp Plugin in /usr/local/nagioslibexec

The SNMP Service is enabled in the Router . The Community names public

I have checked SNMP manually and I get response and Lots of Oids are shown:

Command: snmpwalk -v2c 192.168.172.1 -c public

Part of what Snmpwalk shows:

Code: Select all

iso.3.6.1.2.1.1.1.0 = STRING: "LANCOM 1781AW 10.12.0084 / 19.10.2017 4002851518100372"
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.2356.11.8.607
iso.3.6.1.2.1.1.3.0 = Timeticks: (32504991) 3 days, 18:17:29.91
iso.3.6.1.2.1.1.4.0 = ""
iso.3.6.1.2.1.1.5.0 = STRING: "GM-PS"
iso.3.6.1.2.1.1.6.0 = ""
iso.3.6.1.2.1.1.7.0 = INTEGER: 14
iso.3.6.1.2.1.1.8.0 = Timeticks: (0) 0:00:00.00


When I run ./check_snmp -H 192.168.172.1 -C public -o .1.3.6.1.4.1.2356.11.1.4.13.1 -m allfor example

I get an Timeout

CRITICAL — Plugin timed out while executing system call

Part of my MIB file:

Code: Select all

-- {ROW} 1.3.6.1.4.1.2356.11.1.4.13.1.1
lcsStatusWanIpAddressesIpv4Entry OBJECT-TYPE
SYNTAX LcsStatusWanIpAddressesIpv4Entry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
""
INDEX {
lcsStatusWanIpAddressesIpv4EntryPeer
}
::= { lcsStatusWanIpAddressesIpv4Table 1 }

LcsStatusWanIpAddressesIpv4Entry ::= SEQUENCE {
lcsStatusWanIpAddressesIpv4EntryPeer DisplayString,
lcsStatusWanIpAddressesIpv4EntryType INTEGER,
lcsStatusWanIpAddressesIpv4EntryIpAddress IpAddress,
lcsStatusWanIpAddressesIpv4EntryIpNetmask IpAddress,
lcsStatusWanIpAddressesIpv4EntryGateway IpAddress,
lcsStatusWanIpAddressesIpv4EntryDnsDefault IpAddress,
lcsStatusWanIpAddressesIpv4EntryDnsBackup IpAddress,
lcsStatusWanIpAddressesIpv4EntryNbnsDefault IpAddress,
lcsStatusWanIpAddressesIpv4EntryNbnsBackup IpAddress,
lcsStatusWanIpAddressesIpv4EntryDomain DisplayString
}

-- {COLUMN} 1.3.6.1.4.1.2356.11.1.4.13.1.1.1
lcsStatusWanIpAddressesIpv4EntryPeer OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..16))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"-- empty --"
::= { lcsStatusWanIpAddressesIpv4Entry 1 }

-- {COLUMN} 1.3.6.1.4.1.2356.11.1.4.13.1.1.2
lcsStatusWanIpAddressesIpv4EntryType OBJECT-TYPE
SYNTAX INTEGER {
eStatic (1),
eDhcp (2),
ePpp (3),
eAutoconfig (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"-- empty --"
::= { lcsStatusWanIpAddressesIpv4Entry 2 }

-- {COLUMN} 1.3.6.1.4.1.2356.11.1.4.13.1.1.3
lcsStatusWanIpAddressesIpv4EntryIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"-- empty --"
::= { lcsStatusWanIpAddressesIpv4Entry 3 }

-- {COLUMN} 1.3.6.1.4.1.2356.11.1.4.13.1.1.4
lcsStatusWanIpAddressesIpv4EntryIpNetmask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"-- empty --"
::= { lcsStatusWanIpAddressesIpv4Entry 4 }

-- {COLUMN} 1.3.6.1.4.1.2356.11.1.4.13.1.1.5
lcsStatusWanIpAddressesIpv4EntryGateway OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"-- empty --"
::= { lcsStatusWanIpAddressesIpv4Entry 5 }
-----------------------------------------------------------------------------------------------------------------------------------------------

Part of my Logfile:

Code: Select all

[1517695043] HOST ALERT: GM-PS;DOWN;SOFT;1;CRITICAL - Network Unreachable (192.168.172.1)
[1517739798] Warning: A system time change of 44732 seconds (0d 12h 25m 32s forwards in time) has been detected. Compensating...
[1517739839] HOST ALERT: GM-PS;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 1.21 ms
[1517739842] SERVICE NOTIFICATION: nagiosadmin;GM-PS;HostName;CRITICAL;notify-service-by-email;CRITICAL - Plugin timed out while executing system call
[1517739842] wproc: NOTIFY job 0 from worker Core Worker 650 is a non-check helper but exited with return code 127
[1517739842] wproc: host=GM-PS; service=HostName; contact=nagiosadmin
[1517739842] wproc: early_timeout=0; exited_ok=1; wait_status=32512; error_code=0;
[1517739842] wproc: stderr line 01: /bin/sh: 1: /bin/mail: not found
[1517739842] wproc: stderr line 02: /usr/bin/printf: write error: Broken pipe
[1517739898] SERVICE NOTIFICATION: nagiosadmin;GM-PS;Name;CRITICAL;notify-service-by-email;CRITICAL - Plugin timed out while executing system call
[1517739898] wproc: NOTIFY job 1 from worker Core Worker 651 is a non-check helper but exited with return code 127
[1517739898] wproc: host=GM-PS; service=Name; contact=nagiosadmin
[1517739898] wproc: early_timeout=0; exited_ok=1; wait_status=32512; error_code=0;
[1517739898] wproc: stderr line 01: /bin/sh: 1: /bin/mail: not found
[1517739898] wproc: stderr line 02: /usr/bin/printf: write error: Broken pipe
[1517739999] SERVICE NOTIFICATION: nagiosadmin;GM-PS;Port 1 Bandwidth Usage;UNKNOWN;notify-service-by-email;check_mrtgtraf: Unable to open MRTG log file
[1517739999] wproc: NOTIFY job 2 from worker Core Worker 650 is a non-check helper but exited with return code 127
[1517739999] wproc: host=GM-PS; service=Port 1 Bandwidth Usage; contact=nagiosadmin
[1517739999] wproc: early_timeout=0; exited_ok=1; wait_status=32512; error_code=0;
[1517739999] wproc: stderr line 01: /bin/sh: 1: /bin/mail: not found
[1517739999] wproc: stderr line 02: /usr/bin/printf: write error: Broken pipe
[1517740122] SERVICE NOTIFICATION: nagiosadmin;GM-PS;Uptime;CRITICAL;notify-service-by-email;CRITICAL - Plugin timed out while executing system call
[1517740122] wproc: NOTIFY job 3 from worker Core Worker 651 is a non-check helper but exited with return code 127
[1517740122] wproc: host=GM-PS; service=Uptime; contact=nagiosadmin
[1517740122] wproc: early_timeout=0; exited_ok=1; wait_status=32512; error_code=0;
[1517740122] wproc: stderr line 01: /bin/sh: 1: /bin/mail: not found
[1517740122] wproc: stderr line 02: /usr/bin/printf: write error: Broken pipe
[1517740178] SERVICE NOTIFICATION: nagiosadmin;GM-PS;WAN IP;CRITICAL;notify-service-by-email;CRITICAL - Plugin timed out while executing system call
[1517740178] wproc: NOTIFY job 4 from worker Core Worker 654 is a non-check helper but exited with return code 127
[1517740178] wproc: host=GM-PS; service=WAN IP; contact=nagiosadmin
[1517740178] wproc: early_timeout=0; exited_ok=1; wait_status=32512; error_code=0;
[1517740178] wproc: stderr line 01: /bin/sh: 1: /bin/mail: not found
[1517740178] wproc: stderr line 02: /usr/bin/printf: write error: Broken pipe

Looking forward for help