Skip navigation.

GP Messages 1500-1599

  Previous

1500

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error when getting the character code of the token. The token conversion failed for token, token.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1501

ERROR: Document is not well-formed, value not nicely quoted.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The XML document is not well-formed because the value is not nicely quoted.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1502

ERROR: Internal error in the XML parser, insufficient memory (realloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

1503

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1504

ERROR: Token not found in the document, begin token val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error when getting the character code of the token. The beginning token, token, is not found in the XML document.

Action

Check your XML document and system configuration.

1505

ERROR: Token not found in the document, end token val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error when getting the character code of the token. The ending token, token, is not found in the XML document.

Action

Check your XML document and system configuration.

1506

ERROR: Internal error in the XML parser, insufficient memory (realloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1507

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1508

ERROR: Document is not well-formed, region begins with val and ends with val not located.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The XML document is not well-formed because region begins with token and ends with token not located.

Action

Check your XML document and system configuration.

1509

ERROR: XML operation itself was successful, but there is a logical problem: Element is empty.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered a logical problem even though the XML operation itself was successful. The element requested is empty in the XML document.

Action

Check your XML document and system configuration.

1510

ERROR: Internal error in the XML parser, insufficient memory (realloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1511

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1512

ERROR: Element type not found in the document, check your XML document and system configuration.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. Element type is not found in the XML document.

Action

Check your XML document and system configuration.

1513

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1514

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1515

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1516

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1517

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1518

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1519

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1520

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1521

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1522

ERROR: Internal error in the XML parser, insufficient memory (malloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1523

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1524

ERROR: Internal error in the XML parser, insufficient memory (malloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1525

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1526

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing, encoding (val) not supported.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme, encoding_string, in the XML document is not supported.

Action

Check your XML document and system configuration.

See Also

ubbconfig(5), typesw(5)

1527

ERROR: XML operation itself was successful, but there is a logical problem.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered a logical problem even though the XML operation itself was successful. The XML declaration () is missing from the XML document.

Action

Check your XML document and system configuration.

1528

INFO: XML declaration () is missing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered a logical problem even though the XML operation itself was successful. The XML declaration () is missing from the XML document.

Action

Check your XML document and system configuration.

1529

ERROR: Internal error in the XML parser, insufficient memory (malloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1530

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1531

ERROR: XML operation itself was successful, but there is a logical problem.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered a logical problem even though the XML operation itself was successful. The XML version declaration () is missing from the XML document.

Action

Check your XML document and system configuration.

1532

INFO: XML version declaration () is missing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered a logical problem even though the XML operation itself was successful. The XML version declaration () is missing from the XML document.

Action

Check your XML document and system configuration.

1533

ERROR: Internal error in the XML parser, insufficient memory (realloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1534

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1535

ERROR: Root element type not found in the document, check your XML document and system configuration.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The root element type is not found in the XML document.

Action

Check your XML document and system configuration.

1536

ERROR: XML operation itself was successful, but there is a logical problem: Element is empty.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered a logical problem even though the XML operation itself was successful. The element is empty in the XML document.

Action

Check your XML document and system configuration.

1537

ERROR: Element type not found in the document, check your XML document and system configuration.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The element type is not found in the XML document.

Action

Check your XML document and system configuration.

1538

ERROR: Child element type not found in the document, child element type val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The child element type, child_element_type, is not found in the XML document.

Action

Check your XML document and system configuration.

1539

ERROR: Child element type not found in the document, child element type val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The child element type, child_element_type, is not found in the XML document.

Action

Check your XML document and system configuration.

1540

ERROR: Internal error in the XML parser, insufficient memory (realloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1541

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1542

ERROR: Root element type not found in the document, document element type val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The root element type is not found in the XML document.

Action

Check your XML document and system configuration.

1543

ERROR: Internal error in the XML parser, insufficient memory (malloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1544

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using realloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1545

ERROR: No such attribute defined for the element, element type val, attribute name val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The specified attribute, attribute_name, is not defined for element type, element_type, in the XML document.

Action

Check your XML document and system configuration.

1546

ERROR: Child element type not found in the document.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The child element type is not found in the XML document.

Action

Check your XML document and system configuration.

1547

ERROR: Internal error in the XML parser.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character code not found for specified character, character, with document encoding scheme (val) and machine encoding scheme (val) in the XML document.

Action

Check your XML document and system configuration.

1548

INFO: Character code not found for character val, document encoding (val), machine encoding (val).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character code not found for specified character, character, with document encoding scheme (val) and machine encoding scheme (val) in the XML document.

Action

Check your XML document and system configuration.

1549

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

1550

ERROR: Internal error in the XML parser.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character code not found for specified character, character, with document encoding scheme (val) and machine encoding scheme (val) in the XML document.

Action

Check your XML document and system configuration.

1551

INFO: Character code not found for character val, document encoding (val), machine encoding (val).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character code not found for specified character, character, with document encoding scheme (val) and machine encoding scheme (val) in the XML document.

Action

Check your XML document and system configuration.

1552

ERROR: Character encoding scheme not supported by the TUXEDO data dependent routing.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The character encoding scheme in the XML document is not supported.

Action

Check your XML document and system configuration.

1553

ERROR: Content or value not valid for data dependent routing criteria.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The content or value retrieved from the XML document is not valid for data dependent routing criteria.

Action

Check your XML document and system configuration.

1554

ERROR: Content or value not valid for data dependent routing criteria.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The content or value retrieved from the XML document is not valid for data dependent routing criteria.

Action

Check your XML document and system configuration.

1555

ERROR: Content or value not valid for data dependent routing criteria.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The content or value retrieved from the XML document is not valid for data dependent routing criteria.

Action

Check your XML document and system configuration.

1556

ERROR: Content or value not valid for data dependent routing criteria.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. The content or value retrieved from the XML document is not valid for data dependent routing criteria.

Action

Check your XML document and system configuration.

1557

ERROR: Internal error in the XML parser, unknown flag value val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. A invalid flag value was passed to the parser routine. This should not occur during normal system operation.

Action

Contact BEA Customer Support.

1558

ERROR: Internal error in the XML parser, insufficient memory (malloc).

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1559

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error. An attempt to dynamically allocate memory from the operating system using malloc() failed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1560

ERROR: tmroute failed, cannot allocate data buffer.

Description

During data-dependent routing of a XML typed buffer, an attempt to dynamically allocate memory from the operating system using malloc() failed for initializing the character code table.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. Contact BEA Customer Support.

1561

ERROR: Problem with license file filename

Description

The system could open the file filename.

Action

Ensure that filename exists, and is a valid license file.

1562

ERROR: Environment variable TUXDIR must be set in order to verify license

Description

The environment variable TUXDIR is used to determine the location of the license file.

Action

Set the TUXDIR environment variable. There should be a file named lic.txt in the directory udataobj. If the environment variable is set, and the file exists, contact BEA Customer Support.

1563

ERROR: Memory allocation error

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while getting the name of the license file.

Action

Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1564

ERROR: Memory allocation error

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while getting the name of the license file.

Action

Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1565

ERROR: Unable to bind local address address starting from port low-port to port high-port

Description

Before making a connection, the system was attempting to bind a local port from which to connect. The attempted address was address. The attempted ports ranged from low-port to high-port. All of the ports in the range were tried.

Action

Using a network management tool such as netstat, determine the state of the ports within the range low-port to high-port. Ensure that the IP address described in address can be bound on this local machine. Ensure that your DNS server is configured properly. If all else fails, contact BEA Customer Support.

See Also

ubbconfig

1566

ERROR: Unable to bind local address address

Description

Before making a connection, the system was attempting to bind a local port from which to connect. The attempted address was address.

Action

Using a network management tool such as netstat, determine the state of the address address. Ensure that the IP address described in address can be bound on this local machine. Ensure that your DNS server is configured properly. If all else fails, contact BEA Customer Support.

See Also

ubbconfig

1567

ERROR: Unable to DES encrypt data (var1/var2)

Description

The system was unable to use a password to encrypt data.

Action

Contact BEA Customer Support. Make sure to have the values of var1 and var2 for the support person.

1568

ERROR: Unable to DES decrypt data (val/val)

Description

The system was unable to use a password to decrypt data. The most likely cause of this error is corruption of the buffer, and it may indicate that a security attack was attempted.

Action

Contact BEA Customer Support. Make sure to have the values of var1 and var2 for the support person.

1569

ERROR: Unable to lock network mutex mutex at lineno

Description

An attempt was made to lock the network mutex while processing a network message has failed.

Action

Contact BEA Customer Support. Make sure to have the values of mutex and lineno for the support person.

1570

ERROR: Unable to unlock network mutex mutex at lineno

Description

An attempt was made to unlock the network mutex while processing a network message has failed.

Action

Contact BEA Customer Support. Make sure to have the values of mutex and lineno for the support person.

1571

ERROR: TPMBENC is undefined

Description

Missing codeset encoding name from TPMBENC so could not initialize MBSTRING buffer.

Action

Check to make sure TPMBENC is correctly defined in the process environment.

1572

ERROR: Failed to add tcm for codeset encoding encoding_name

Description

Was not able to initialize codeset encoding name on MBSTRING buffer.

Action

Review other messages earlier in the log that indicate what may have caused the failure.

1573

ERROR: Input codeset encoding argument not defined

Description

Target encoding argument is missing and is required for codeset encoding conversion.

Action

If using automatic converion, check to make sure TPMBENC is correctly defined in the process environment otherwise if using tpconvmb() make sure the target encoding argument is properly set.

1574

ERROR: Unable to get message buffer from input provided

Description

The MBSTRING conversion functions received a message that does not contain necessary information.

Action

Contact BEA Customer Support

1575

ERROR: Conversion open failure error for source encoding_name and target encoding_name

Description

The codeset conversion library did not know how to convert using the source and target encoding names given.

Action

Check that the conversion library can handle the conversion desired.Check that the encoding names being used are supported and the ones desired.

1576

ERROR: Failed to allocate space for temporary buffer

Description

An attempt dynamically to allocate memory from the operating system failed during an MBSTRING codeset encoding conversion attempt.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

1577

ERROR: encoding_name not found in list of valid encoding names

Description

The encoding contained in TPMBENC is not a valid name.

Action

Check that the TPMBENC is set to the codeset encoding name desired. If necessary create a chareset.alias file in the APPDIR and add this TPMBENC as an alias to a valid encoding name.

1578

ERROR: Codeset conversion failed. Incomplete char/shift sequence.

Description

The conversion library was not able to understand the character combination that was passed in.

Action

Verify that the sequence of bytes to be converted makes sense for the encodings that are defined.

1579

ERROR: Codeset conversion failed. Illegal character or sequence

Description

The coversion library determined that a character, or a sequence of character, was not valid for one of the codeset encodings defined for conversions.

Action

Verify that the character, or sequence of characters, to be converted makes sense for the encodings that are defined.

1580

ERROR: Codeset conversion failed. Invalid conversion descriptor

Description

The combination of encoding names for source and target was not acceptable to the conversion library being used.

Action

Check that the conversion library can handle the conversion desired.Check that the encoding names being used are supported and the ones desired.

1581

ERROR: Codeset conversion failed. Undefined error error

Description

An error occured that the typed buffer conversion function is not prepared for.

Action

Checked the error values returned by the conversion library being used.

1582

ERROR: Input codeset encoding argument not defined

Description

Source encoding argument is missing and is required for codeset encoding conversion.

Action

If using automatic converion, check to make sure TPMBENC is correctly defined in the process environment otherwise if using tpconvfmb32() make sure the source encoding argument is properly set.

1583

ERROR: TPMBENC is undefined

Description

Missing codeset encoding name from TPMBENC so can not convert FLD_MBSTRING field

Action

Check to make sure TPMBENC is correctly defined in the target process environment.

1584

ERROR: encoding_name not found in list of valid encoding names

Description

The encoding contained in TPMBENC is not a valid name.

Action

Check that the TPMBENC is set to the codeset encoding name desired. If necessary create a chareset.alias file in the APPDIR and add this TPMBENC as an alias to a valid encoding name.

1585

ERROR: Conversion open failure error for source encoding_name and target encoding_name

Description

The codeset conversion library did not know how to convert using the source and target encoding names given.

Action

Check that the conversion library can handle the conversion desired.Check that the encoding names being used are supported and the ones desired.

1586

ERROR: Failed to allocate space for temporary buffer

Description

An attempt dynamically to allocate memory from the operating system failed during an FLD_MBSTRING codeset encoding conversion attempt.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

1587

ERROR: Codeset conversion failed. Incomplete char/shift sequence.

Description

The conversion library was not able to understand the character combination that was passed in.

Action

Verify that the sequence of bytes to be converted makes sense for the encodings that are defined.

1588

ERROR: Codeset conversion failed. Illegal character or sequence

Description

The coversion library determined that a character, or a sequence of character, was not valid for one of the codeset encodings defined for conversions.

Action

Verify that the character, or sequence of characters, to be converted makes sense for the encodings that are defined.

1589

ERROR: Codeset conversion failed. Invalid conversion descriptor

Description

The combination of encoding names for source and target was not acceptable to the conversion library being used.

Action

Check that the conversion library can handle the conversion desired.Check that the encoding names being used are supported and the ones desired.

1590

ERROR: Codeset conversion failed. Undefined error error

Description

An error occured that the typed buffer conversion function is not prepared for.

Action

Checked the error values returned by the conversion library being used.

1591

INFO: License file filename not found

Description

The system could open the file filename.

Action

For /WS only installation, you can ignore this message if you don't use LLE. Otherwise please make sure the license file filename is available.

1592

ERROR: getaddrinfo error: Error message

Description

System API getaddrinfo fail to get IPv6 socket address.

Action

Check and correct the IPv6 address configuration.

1593

ERROR: scope id is 0.

Description

v6 socket address set sin6_scope_id field failure.

Action

This error message printed on Linux and Windows only, please check and correct IPv6 related configuration items such as IPv6 network interface and IPv6 routing table.

1596

ERROR: Failed to reset access log prefix, memory allocation failure

Description

The program failed to reset the prefix for the accesslog file because dynamic space allocation failed. The accesslog file prefix is not reset, and this message will be written to the accesslog using the current prefix value.

Action

No action required.

See Also

accesslog(3c)

 

Skip footer navigation  Back to Top Previous