Message Class 2000 - XML/SOAP Runtime

The messages have the format:

2000nnnn

where 2000 is the message class, and
nnnn is the message number in the range 0000 - 9999

Overview of Messages

20000001 | 20000002 | 20000003 | 20000004 | 20000005 | 20000006 | 20000007 | 20000021 | 20000025 | 20000026 | 20000027 | 20000031 | 20000043 | 20000060 | 20000062 | 20000064 | 20000070 | 20000072 | 20000075 | 20000077 | 20000078 | 20000079 | 20000080 | 20000081 | 20000082 | 20000084 | 20000086 | 20000087 | 20000088 | 20000089 | 20000100 | 20000101 | 20000103 | 20000104 | 20000110 | 20000120 | 20000130 | 20000140 | 20000141 | 20000250
20000001 Broker Exception: :1:
Explanation

Information on the BrokerException is contained in the error message (ErrorClass, ErrorNumber and ErrorText).

Action

Look up the error class/number for the BrokerException and follow the instructions.

20000002 Server Exception: :1:
Explanation

Information on the ServerException is contained in the error message (ErrorClass, ErrorNumber and ErrorText).

Action

Look up the error class/number for the ServerException and follow the instructions.

20000003 External Parser Exception
Explanation

The external parser throws an exception.
Action

  • Check if the JAR files of the parser are located in CLASSPATH.

  • Check if the incoming document is well-formed.
20000004 Internal Error: Java IO Exception
Explanation

Either the XML/SOAP Wrapper cannot find a file or the RPC Server for XML/SOAP does not connect to the Web server.
Action

  • XML/SOAP Wrapper:
    Check your path settings. If they are correct, contact Software AG Support.

  • RPC Server for XML/SOAP:
    Check the URI of the Web server. If it is correct, contact Software AG Support.

20000005 Internal Error: Java Exception
Explanation

Internal error.
Action

Contact Software AG Support.
20000006 Incoming SOAP document is invalid
Explanation

The incoming XML document is invalid.
Action

Check the incoming document.
20000007 Incoming XML document is invalid
Explanation

The incoming XML document is invalid.
Action

Check the incoming document.
20000021 XML Parser not found
Explanation

The XML parser could not be found because the JAR files of the parser were not found in CLASSPATH.

Action

Correct CLASSPATH specifications.

20000025 Mapping Error: Path cannot be resolved
Explanation

Internal error.
Action

Contact Software AG Support.
20000026 Mapping Error: Mapping of one item fails
Explanation

Internal error.
Action

Contact Software AG Support. Required information: the IDL-XML mapping file (XMM).

20000027 Mapping Error: Invalid mapping path
Explanation

Internal error.
Action

Contact Software AG Support. Required information: the IDL-XML mapping file (XMM).

20000031 Mapping Error: Value cannot be mapped
Explanation

The document contains a value that cannot be mapped.
Action

Contact Software AG Support. Required information: the IDL-XML mapping file (XMM).

20000043 Invalid Configuration File
Explanation

The configuration file contains an invalid definition. See details of error message for more information.

Action

Correct the configuration file.
20000060 Incoming Document: Invalid base64 format
Explanation

The binary data has an invalid base64 format.

The incoming document contains binary data in base64 format. For at least one data item the base64 format is invalid.

Action

Check the application of the sender.
20000062 Problem with JAXP: ParserFactory not found
Explanation

The XMLRuntime cannot find the factory class of XML parser.

Action

Check JAXP setting and classpath.
20000064 Marshalling failed: Unexpected number of array elements
Explanation

An array contains more elements than the maximum definition.
Action

Check your IDL-XML mapping and the documents used.
20000070 Repository Error: Inconsistent data loaded
Explanation

At least one loaded XMM file contains corrupt or conflicting data.
Action

  • Check the XMM file(s).

  • Check if you are using the RPC Server for XML/SOAP configuration file.
20000072 Version mismatch
Explanation

An EntireX server does not understand the required protocol version.
Action

Check IDL definition. It must be suitable for client and server applications.

20000075 Parameter not set
Explanation

A data stream for reading or writing is null (using Java API).
Action

Check your application.
20000077 Unknown document, XML/SOAP Runtime cannot interpret the incoming document
Explanation

The incoming document was not found in the internal repository.
Action

No suitable mapping was found. Check if

  1. the XMM file is contained in the configuration.

  2. the namespaces in the document and the XMM file match.
20000078 Invalid XMM file
Explanation

The XMM file has an error.
Action

Save the XMM file again. If the problem is permanent, contact Software AG Support.
20000079 Transport error
Explanation

The HTTP transport of data failed, for example because the proxy setting is missing or the target service is not available.

Action

  1. Check proxy settings.

    • If a firewall is in use, define the required proxy settings.

    • If you are using a proxy setting and connecting to localhost, add the following definition:

      -Dhttp.nonProxyHosts=localhost

  2. Check the URL of the target service. To get more information, start the RPC Server for XML/SOAP with enabled trace.

20000080 Writing document failed
Explanation

Writing an outgoing XML document failed, caused by unsupported encoding or an internal error.

Action

Verify the encoding used and/or contact Software AG Support.
20000081 Unsupported transport medium
Explanation

The configuration file of the RPC Server for XML/SOAP contains a transport medium that is not supported by the XML/SOAP Runtime.

Action

Check your configuration file.
20000082 Unknown RPC program
Explanation

The XML Runtime did not find a description for the RPC program called.
Action

Check your configuration file for missing or conflicting definitions.
20000084 Unknown data type
Explanation

The required data type cannot be marshalled with the protocol used, or the XMM file used has a corrupt entry.

Action

Check IDL-XML mapping and check application for any server that does not support the data type used.

20000086 Received unexpected document (faulty document)
Explanation

An XML client sent a faulty document.
Action

Check your application.
20000087 Internal error
Explanation

The internal processing terminates abnormally with an error.
Action

Check the details of error information. If this information does not help you resolve the problem, contact Software AG Support.
20000088 Value does not match type definition
Explanation

The value of the parameter does not match the type definition. For example, a parameter for a numeric field does not contain a numeric value.

Action

The error message contains the name and value of invalid parameter. Correct the inconsistency in your application, that is, check the data type.

20000089 Format exception: Date or time parameter does not match format definition
Explanation

The format definition of a date or time parameter does not match format set by user or default format.

Action

Check IDL-XML mapping and the documents used.
20000100 Syntax error in IDL-XML mapping file
Explanation

The IDL-XML mapping file contains an unexpected tag.
Action

Contact Software AG Support.
20000101 Invalid IDL-XML mapping File
Explanation

The IDL-XML mapping file is not well-formed or is unreadable.
Action

If using FTP to move mapping file, check that binary mode is set. Otherwise contact Software AG Support.

20000103 Configuration error: IDL-XML mapping file conflict in library/program name
Explanation

A name clash of library/program is found.
Action

Check your IDL-XML mapping files.
20000104 IDL-XML Mapping File contains non-supported Natural/COBOL redefine settings in library/program
Explanation

The specified XMM contains Natural/COBOL redefine information, which is not supported.
Action

Remove the program listed in the error message from the mapping file.
20000110 Configuration Error
Explanation

Reading the configuration terminates with an error message probably because of an invalid classpath, an invalid configuration or an inconsistent value assignment within the configuration.

Action

Check configuration file and CLASSPATH.

20000120 Document does not fulfill SOAP 1.1 specification
Explanation

The document contains a description not compliant with the SOAP 1.1 specification.

Action

Check the document for compliance with the SOAP 1.1 specification.
20000130 Document does not fulfill SOAP 1.2 specification
Explanation

The document contains a description not compliant with the SOAP 1.2 specification.

Action

Check document for compliance with the SOAP 1.2 specification.
20000140 HTTP header contains invalid value
Explanation

The HTTP header contains an invalid value for the session ID or the conversation.

Action

Read fault document and check the application.
20000141 HTTP message contains invalid value
Explanation

The HTTP message (header or payload) contains an invalid value.
Action

Read fault document and check the application.
20000250 Program should have INPUT parameters only
Explanation

An asynchronous call with INOUT or OUT parameter was made.

Action

Check application and IDL definition.