Message Class 2000 - XML/SOAP Runtime

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

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

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

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

The external parser throws an exception.

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

• Check if the incoming document is well-formed.

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

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

XML RPC server: Check the URI of the Web server. If it is correct, contact Software AG support.

Internal error.

Contact Software AG support.

The incoming XML document is invalid.

Check the incoming document.

The incoming XML document is invalid.

Check the incoming document.

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

Correct CLASSPATH specifications.

Internal error.

Contact Software AG support.

Internal error.

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

Internal error.

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

The document contains a value that cannot be mapped.

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

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

Correct the configuration file.

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.

Check the application of the sender.

The XMLRuntime cannot find the factory class of XML parser.

Check JAXP setting and classpath.

An array contains more elements than the maximum definition.

Check your IDL-XML mapping and the documents used.

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

• Check the XMM file(s).

• Check if you are using the XML/SOAP RPC Server configuration file.

An EntireX server does not understand the required protocol version.

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

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

Check your application.

The incoming document was not found in the internal repository.

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.

The XMM file has an error.

Save the XMM file again. If the problem is permanent, contact Software AG support.

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

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 XML/SOAP RPC Server with enabled trace.

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

Verify the encoding used and/or contact Software AG support.

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

Check your configuration file.

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

Check your configuration file for missing or conflicting definitions.

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

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

An XML client sent a faulty document.

Check your application.

The internal processing terminates abnormally with an error.

Check the details of error information. If this information does not help you resolve the problem, contact Software AG support.

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.

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

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

Check IDL-XML mapping and the documents used.

The IDL-XML mapping file contains an unexpected tag.

Contact Software AG support.

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

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

A name clash of library/program is found.

Check your IDL-XML mapping files.

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

Remove the program listed in the error message from the mapping file.

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.

Check configuration file and CLASSPATH.

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

Check the document for compliance with the SOAP 1.1 specification.

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

Check document for compliance with the SOAP 1.2 specification.

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

Read fault document and check the application.

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

Read fault document and check the application.

An asynchronous call with INOUT or OUT parameter was made.

Check application and IDL definition.