The messages have the format:
2000nnnn
| where | 2000 | is the error class, and |
| nnnn | is the error number in the range 0000 - 9999 |
20000001 | 20000002 | 20000003 | 20000004 | 20000005 | 20000006 | 20000007 | 20000008 | 20000010 | 20000011 | 20000012 | 20000013 | 20000014 | 20000015 | 20000016 | 20000017 | 20000018 | 20000019 | 20000020 | 20000021 | 20000022 | 20000023 | 20000024 | 20000025 | 20000026 | 20000027 | 20000028 | 20000029 | 20000030 | 20000031 | 20000032 | 20000034 | 20000035 | 20000038 | 20000040 | 20000041 | 20000042 | 20000043 | 20000045 | 20000046 | 20000047 | 20000048 | 20000050 | 20000051 | 20000052 | 20000053 | 20000054 | 20000055 | 20000060 | 20000061 | 20000062 | 20000064 | 20000070 | 20000071 | 20000072 | 20000073 | 20000074 | 20000075 | 20000076 | 20000077 | 20000078 | 20000079 | 20000080 | 20000081 | 20000082 | 20000084 | 20000085 | 20000086 | 20000087 | 20000088 | 20000089| 20000001 | Broker Exception: {0} |
| Explanation |
Read the BrokerException text. |
| Action |
Follow the explanation of the BrokerException. |
| 20000002 | Server Exception: {0} |
| Explanation |
Read the Server Exception text. |
| Action |
Follow the explanation of the ServerException. |
| 20000003 | External Parser Exception |
| Explanation |
The external parser throws an exception. |
| Action |
Check parser setting and incoming document. |
| 20000004 | Internal Error: Java IO Exception |
| Explanation |
Either the XML/SOAP Wrapper cannot find a file or the XML RPCServer does not connect to the web server. |
| Action |
XML/SOAP Wrapper: Check your path settings, if they are correct contact support. XML RPCServer: Check the URI of the web server, if it is correct contact support. |
| 20000005 | Internal Error: Java Exception |
| Explanation |
Internal error. |
| Action |
Contact 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. |
| 20000008 | Internal Error: No runtime object is set |
| Explanation |
No runtime object is set. |
| Action |
Contact Software AG support. |
| 20000010 | SOAP format error: Document has two <Envelope>-tags |
| Explanation |
The SOAP document has two <Envelope>-tags. |
| Action |
Correct your SOAP document. |
| 20000011 | SOAP format error: <Header>-tag without <Envelope>-tags |
| Explanation |
The SOAP document has a <Header>-tag without <Envelope>-tags. |
| Action |
Correct your SOAP document. |
| 20000012 | SOAP format error: Document has two <Header>-tags |
| Explanation |
The SOAP document has two <Header>-tags. |
| Action |
Correct your SOAP document. |
| 20000013 | SOAP format error: <Body>-tag without <Envelope>-tags |
| Explanation |
The SOAP document has a <Body>-tag without <Envelope>-tags. |
| Action |
Correct your SOAP document. |
| 20000014 | SOAP format error: Document has two <Body>-tags |
| Explanation |
The SOAP document has two <Body>-tags. |
| Action |
Correct your SOAP document. |
| 20000015 | SOAP format error: <Header> or <Body>-tag expected |
| Explanation |
The SOAP document is invalid. There is no <Header> or <Body>-tag. |
| Action |
Correct your SOAP document. |
| 20000016 | SOAP format error: <Body>-tag expected |
| Explanation |
The SOAP document is invalid. There is no <Body>-tag. |
| Action |
Correct your SOAP document. |
| 20000017 | SOAP format error: Unknown program |
| Explanation |
The SOAP document is using an unknown program name. |
| Action |
Correct your SOAP document or modify your XMLAdapter. |
| 20000018 | SOAP format error: <Envelope>-tag expected |
| Explanation |
The SOAP document is invalid. There is no <Envelope>-tag. |
| Action |
Correct your SOAP document. |
| 20000019 | SOAP format error: Unresolved reference |
| Explanation |
The SOAP document contains an href-identifier without id-identifier. |
| Action |
Correct your SOAP document. |
| 20000020 | SOAP format error: Reference identifier always exists |
| Explanation |
The SOAP document contains a redefinition of id-identifier. |
| Action |
Correct your SOAP document. |
| 20000021 | XML Parser not found |
| Explanation |
The XML Parser could not be found because the 'xerces.jar' was not found in classpath. |
| Action |
Set your classpath to the 'xerces.jar' file. |
| 20000022 | XML/SOAP Runtime cannot load additional adapters |
| Explanation |
The adapter is still loaded. |
| Action |
Correct your invoke with unique adapters. |
| 20000023 | Invalid input document: No such program found |
| Explanation |
The incoming document has no valid or unknown program. |
| Action |
Check your incoming document or adjust XML adapter. |
| 20000024 | Mapping Error: No target found |
| Explanation |
Internal error. |
| Action |
Contact support. |
| 20000025 | Mapping Error: Path cannot be resolved |
| Explanation |
Internal error. |
| Action |
Contact support. |
| 20000026 | Mapping Error: Mapping of one item fails |
| Explanation |
Internal error. |
| Action |
Contact support. |
| 20000027 | Mapping Error: Invalid mapping path |
| Explanation |
Internal error. |
| Action |
Contact support. |
| 20000028 | Specified XMLAdapter not found |
| Explanation |
The XMLAdapter could not be found in the current environment. |
| Action |
Check your environment. |
| 20000029 | Specified XMLAdapter is invalid |
| Explanation |
The specified XMLAdapter is invalid. |
| Action |
Regenerate the XMLAdapter and make it accessible. |
| 20000030 | No XMLAdapter is specified |
| Explanation |
There is no XMLAdapter specified. |
| Action |
Specify an XMLAdapter. |
| 20000031 | Mapping Error: Value cannot be mapped |
| Explanation |
The document contains a value that cannot be mapped. |
| Action |
Check your document and your XML adapter. |
| 20000032 | Incoming Document: Required attribute missing |
| Explanation |
The incoming document is missing a required attribute. |
| Action |
Check your incoming document and add the missing attribute. |
| 20000034 | Incoming Document: Number of array elements is too low |
| Explanation |
The number of the array elements is too low. |
| Action |
Check your incoming document for the right number of array elements. |
| 20000035 | Incoming Document: Number of array elements is too high |
| Explanation |
The number of the array elements is too high. |
| Action |
Check your incoming document for the right number of array elements. |
| 20000038 | Incoming Document: Required element missing |
| Explanation |
The incoming document is missing a required element. |
| Action |
Check your incoming document and add the missing element. |
| 20000040 | Servlet: Adapter not found |
| Explanation |
The specified XMLAdapter could not be found. |
| Action |
Check your servlet header, your servlet parameter or whether the web server can reach the XMLAdapter. |
| 20000041 | Servlet: No server address is specified |
| Explanation |
There is no server address specified. |
| Action |
Check your servlet header or servlet parameter. |
| 20000042 | Servlet: No Broker ID is specified |
| Explanation |
There is no Broker ID specified. |
| Action |
Check your servlet header or servlet parameter. |
| 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. |
| 20000045 | Servlet: SAX Parser cannot be loaded |
| Explanation |
The SAX Parser cannot be loaded. |
| Action |
Check your environment and provide the 'xerces.jar' in your classpath. |
| 20000046 | Servlet: Initfile not found |
| Explanation |
The specified Initfile could not be found. |
| Action |
Copy and edit the 'xml-init.xml' file in the web server directory and specify the name in the 'exx-xml-init' parameter. |
| 20000047 | Servlet: Error while reading initfile |
| Explanation |
There is an error in the initfile. |
| Action |
Check your 'xml-init.xml' file. |
| 20000048 | Servlet: Error while processing initfile |
| Explanation |
When processing the initfile, an error occurs. |
| Action |
Check and correct your 'xml-init.xml' file. |
| 20000050 | Servlet: Invalid initfile document |
| Explanation |
The initfile document is invalid. |
| Action |
Correct your 'xml-init.xml' file. |
| 20000051 | Servlet: BrokerException |
| Explanation |
Read the BrokerException text of the servlet. |
| Action |
Follow the explanation of the servlet BrokerException. |
| 20000052 | Servlet: Bad HTTP request: Invalid header or parameter |
| Explanation |
The header or parameter properties are invalid or incomplete. |
| Action |
Check your header or parameters. |
| 20000053 | Servlet: Location Transparency init file not found |
| Explanation |
The location transparency settings could not be found. |
| Action |
Check the values of the two Java properties
|
| 20000054 | Servlet: Bad HTTP request; Incoming document is empty |
| Explanation |
The received HTTP request contains no data. |
| Action |
Check the application. |
| 20000055 | Servlet: DataStream has not been read completely |
| Explanation |
This error occurs if the data stream reaches the end before reading all the bytes. |
| Action |
Contact Software AG support. |
| 20000060 | Incoming Document: Invalid base64 - format |
| Explanation |
The binary data has an invalid base64-format. |
| Action |
Check the incoming document. |
| 20000061 | Unsupported method or feature |
| Explanation |
An unsupported feature was called. |
| Action |
Check your application. |
| 20000062 | Problem with JAXP: ParserFactory not found |
| Explanation |
The XMLRuntime cannot find the SAXParserFactory 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 |
The loaded XMM file(s) or XMLAdapter(s) contain corrupt or conflicting data. |
| Action |
Check XMM file or XMLAdapter and whether you are using XMLRPCServer configuration file. |
| 20000071 | Fatal error |
| Explanation |
Internal error. |
| Action |
Contact support. |
| 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. |
| 20000073 | Problem with JAXP: DocumentBuilderFactory not found |
| Explanation |
The XMLRuntime cannot find the DocumentBuilderFactory class of XML parser. |
| Action |
Check JAXP setting and classpath. |
| 20000074 | Problem with JAXP: DocumentBuilder not found |
| Explanation |
The XMLRuntime cannot find the DocumentBuilder class of XML parser. |
| Action |
Check JAXP setting and classpath. |
| 20000075 | Parameter not set |
| Explanation |
A data stream for reading or writing is null (using Java API). |
| Action |
Check your application. |
| 20000076 | Invalid RPC message |
| Explanation |
A corrupt message or an error message was received from participant. |
| Action |
See detail information of error message. |
| 20000077 | Unknown document, XML/SOAP Runtime cannot interpret the incoming document |
| Explanation |
The incoming document was not found in the internal repository. |
| Action |
Check configuration. |
| 20000078 | Invalid XMM file |
| Explanation |
The XMM file has an error. |
| Action |
Save the XMM file again. If problem is permanent contact support. |
| 20000079 | Transport error |
| Explanation |
The HTTP transport of data failed. |
| Action |
Check your application. |
| 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 support. |
| 20000081 | Unsupported transport medium |
| Explanation |
The configuration file of XMLRPCServer contains a transport medium which is not supported by XML/SOAP Runtime. |
| Action |
Check your configuration file. |
| 20000082 | Unknown RPC program |
| Explanation |
The XMLRuntime 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. |
| 20000085 | Required document format is not supported |
| Explanation |
The required document format is not supported by XML/SOAP Runtime. |
| Action |
Check IDL-XML-mapping and the documents used. |
| 20000086 | Received unexpected document (faulty document) |
| Explanation |
An XML client sent a faulty document. |
| Action |
Check your application. |
| 20000087 | Internal error |
| Explanation |
Internal error. |
| Action |
Contact support. |
| 20000088 | Wrong data value |
| Explanation |
A data value does not match definition, e.g. the length of a value exceeds the length definition of parameter. |
| Action |
Check your IDL-XML-Mapping and the documents used. |
| 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. |
