62 LPX-00000 to LPX-00690

Cause: Normal exit

Cause: A NULL pointer was detected as an internal error condition.

Cause: The operating system has run out of memory.

Cause: An internal error has occurred (a key was requested to be placed in a hash table but was already there).

Cause: An internal error has occurred.

Cause: A name, quoted string, URL, or other document component was too long.

Cause: An attempt was made to add an invalid node-type to a parent node.

Cause: The documented ended unexpectedly, perhaps due to truncation.

Cause: The memory callback structure passed to xmlinit was missing the allocate or free functions (or both).

Cause: Error message prefixes, not errors themselves. These are the possible banner messages which appear before an XML error to describe the position (line#) and source (buffer or URI) in which the error occurred, as well as the entity's name (if the source is an entity). Parameter entity banner must be at +1 to non-entity banner, general entity at +2 (see lpxerr.c).

Cause: An input Unicode (UCS2) datum was not aligned properly.

Cause: The wrong node type was given as argument to a DOM call.

Cause: An operation was performed on a context that has already been used (so is not "clean").

Cause: More error message boilerplate.

Cause: An internal error has occurred.

Cause: The named initialization property was unknown

Cause: Validity Constraint 2.8 failed: "The Name in the document type declaration must match the element type of the root element." *Example: <?xml version="1.0"?> <!DOCTYPE greeting [ <!ELEMENT greeting (#PCDATA)> ]> <salutation>Hello!</salutation> *Explanation: The document's root element, salutation, does not match the root element declared in the DTD (greeting).

Cause: Validity Constraint 2.8 failed: "Parameter-entity replacement text must be properly nested with markup declarations." *Example: <?xml version="1.0"?> <!DOCTYPE greeting [ <!ENTITY % e "<!ELEMENT "> %e; greeting (#PCDATA)> ]> <greeting>Hello!</greeting> *Explanation: The parameter entity 'e' contains markup which may not be split up; the entire ELEMENT (or ATTLIST or ENTITY) definition must be present in one piece.

Cause: Validity Constraint 2.9 failed: "Standalone document declaration must have the value 'no' if any external markup declarations contain declarations of:

* attributes with default values - or -

* entities - or -

* attributes with values subject to normalization - or -

* element types with element content"

Cause: Validity Constraint 3 failed: "An element is valid if there is a declaration matching elementdecl where the Name matches the element type, and one of the following holds:

* The declaration matches EMPTY and the element has no content

* The declaration matches children and the sequence of child elements belongs to the language generated by the regular expression in the content model, with optional white space (characters matching the nonterminal S) between each pair of child elements.

* The declaration matches Mixed and the content consists of character data and child elements whose types match names in the content model.

* The declaration matches ANY, and the types of any child elements have been declared."

Cause: Validity Constraint 3 failed: The named element has no matching elementdecl in the DTD

Cause: Validity Constraint 3 failed: The named element is declared as EMPTY in the DTD but contains sub-elements in the document.

Cause: Validity Constraint 3.1 failed:

Cause: Validity Constraint 3.2 failed: "No element type may be declared more than once."

Cause: Validity Constraint 3.2.1 failed: "Parameter-entity replacement text must be properly nested with parenthesized groups. For interoperability, if a parameter-entity reference appears in a choice, seq, or Mixed construct, its replacement text should not be empty, and neither the first nor last non-blank character of the replacement text should be a connector (| or ,). *Example: <?xml version="1.0"?> <!DOCTYPE foo [ <!ELEMENT greeting (#PCDATA)> <!ENTITY % e "(#PCDATA|"> <!ELEMENT foo %e; greeting)> ]> <greeting>Hello!</greeting> *Explanation: The parenthetical content of the 'e' entity may not be split up into sections: both open and close parentheses must be in the same declaration.

Cause: Validity Constraint 3.2.2 failed: "The same name must not appear more than once in a single mixed-content declaration." *Example: <!ELEMENT p (#PCDATA|a|b|c|d|a)> *Explanation: 'a' occurs more than once in the mixed-content declaration.

Cause: Validity Constraint 3.3.1 failed: Given thing is not a Name

Cause: Validity Constraint 3.3.1 failed: Given thing is not a Nmtoken

Cause: Validity Constraint 3.3.1 failed: "No element type may have more than one ID attribute specified."

Cause: Validity Constraint 3.3.1 failed: "An ID attribute must have a declared default of #IMPLIED or #REQUIRED."

Cause: Validity Constraint 3.3.1 failed: "Values of this type must match one of the Nmtoken tokens in the declaration."

Cause: Validity Constraint 3.3.2 failed: "If the default declaration is the keyword #REQUIRED, then the attribute must be specified for all elements of the type in the attribute-list declaration."

Cause: Validity Constraint 3.3.2 failed: "If an attribute has a default value declared with the #FIXED keyword, instances of that attribute must match the default value."

Cause: Validity Constraint 4.1 failed: "In a document with an external subset or external parameter entities with "standalone='no'", the Name given in the entity reference must match that in an entity declaration."

Cause: The attribute value must be an unparsed entity.

Cause: Entity's NDATA (notation) is undefined

Cause: Notation is not known.

Cause: Validity Constraint 3.3.1 failed: "A name must not appear more than once in an XML document as a value of this type; i.e., ID values must uniquely identify the elements which bear them."

Cause: An ID was used twice, they must be unique.

Cause: An attribute with tokenized type (IDREFS, ENTITIES, NMTOKENS) did not contain any tokens.

Cause: Warning returned by XmlDomGetDecl when original document did not contain an XMLDecl

Cause: The conversion cannot be made between the specified encodings.

Cause: The specified encoding was not known. It should be an IANA or Oracle encoding name.

Cause: The named input (file, URL, etc) does not exist.

Cause: Data could not be read from the named input.

Cause: A syntax error was found.

Cause: Bad syntax detected when processing a comment.

Cause: Bad syntax detected when processing CDATA. Proper format is '<![CDATA[' data ']]>'.

Cause: Bad syntax detected when processing a conditional section.

Cause: An unknown keyword was found in the DTD.

Cause: Processing instruction starting with XML was found.

Cause: A syntax error was detected.

Cause: Attribute default was invalid.

Cause: A syntax error was detected in the comment.

Cause: A syntax error was detected in the comment.

Cause: A syntax error was detected in the CDATA section.

Cause: A syntax error was detected in the PI section.

Cause: An invalid multibyte character was found.

Cause: An invalid Unicode character was found.

Cause: An invalid native (ASCII/EBCDIC) character was found.

Cause: An invalid digit was found in a character reference.

Cause: Found ']]>' in character data.

Cause: Found '<' in an attribute value.

Cause: An error was received from the SAX callback function.

Cause: An external entity reference was found in an attribute value.

Cause: An attribute occurred multiple times in the same start-tag or empty-element tag.

Cause: An element tag was not ended properly.

Cause: An entity is not declared.

Cause: An entity reference contained the name of an unparsed entity.

Cause: An entity reference contains a recursive reference to itself.

Cause: An XML input file has no contents.

Cause: An invalid character was found in a NAME or NMTOKEN.

Cause: An invalid character was found in a NAME or NMTOKEN.

Cause: A parameter entity reference was found in an improper location in the internal DTD subset.

Cause: Namespace prefix starting with XML was found.

Cause: Namespace prefix is not declared.

Cause: Only versions 1.0 and 2.0 of the XML specification are supported.

Cause: An invalid character was found in a public identifier.

Cause: A conditional section <![ keyword [ markup ]]> had invalid keyword, must be either "IGNORE" or "INCLUDE"

Cause: A conditional section was not properly terminated with ]]>.

Cause: The attribute type is not valid. Options are CDATA, ID, IDREF, IDREFS, ENTITY, ENTITIES, NMTOKEN, or NMTOKENS.

Cause: A start-element tag was improperly formed.

Cause: An entity reference (general or parameter) was not formed properly.

Cause: The ampersand character is used only to start entity or character references.

Cause: An attribute defined in an element's start-tag must be enclosed in single ('') or double ("") quotes.

Cause: The less-than character ('<') is not permitted as data.

Cause: After the close of the top-level element, more data was found.

Cause: In an external ID declaration, the public ID literal was not followed by the system ID literal as required.

Cause: Problems were encountered in the DTD declaration.

Cause: Problems were encountered parsing an entity declaration.

Cause: Problems were encountered parsing an external ID declaration.

Cause: Problems were encountered parsing an attribute declaration.

Cause: A condition section is not permitted in internal DTDs.

Cause: Markup included from an entity must nest/group properly. That is, open/close markup must occur within the same entity. For example, <!DOCTYPE doc [ <!ENTITY e "</foo><foo>"> ]> <doc><foo>&e;</foo></doc> Is invalid since foo's start-tag occurs in the top-level

Cause: An XML declaration was missing the required version#.

Cause: Problems were encountered parsing an XML declaration.

Cause: The "standalone" parameter in the XML declaration had an invalid value.

Cause: Problems were encountered parsing an element declaration.

Cause: The 'children' specification in an element declaration was invalid.

Cause: The 'Mixed' specification in an element declaration was invalid.

Cause: Problems were encountered parsing a notation declaration.

Cause: The xml:space attribute must be declared as an enumeration with choices "default" and "preserve". For example, <!ATTLIST foo xml:space (default|preserve) 'preserve').

Cause: The specified URL was invalid and could not be parsed.

Cause: An URL was encountered which requested a protocol not supported by the XML parser. Only HTTP and file are currently allowed.

Cause: A TCP connection couldn't be opened to the named host.

Cause: An error occurred trying to send data over a TCP connection.

Cause: An error occurred trying to read data from a TCP connection.

Cause: The given language specification was invalid.

Cause: The named relative URL couldn't be resolved against its parent.

Cause: The provided access code was not in the valid range.

Cause: An attempt was made to set the access method callbacks, but all three functions were not provided.

Cause: An error was returned from the FTP server while trying to retrieve a file. See the specific message for details.

Cause: The username/password combination was invalid for FTP login.

Cause: The FTP server is unavailable for use.

Cause: The TCP/IP package could not be initialized.

Cause: Some node types (DOCUMENT_NODE & DOCUMENT_TYPE_NODE) cannot be imported with importNode().

Cause: Output/data encoding must be set after initialization but BEFORE any parsing has taken place.

Cause: An HTTP reply contained an invalid Mime header.

Cause: A quoted string was started but not finished.

Cause: The proxy specification for the given protocol was invalid.

Cause: The no_proxy specification was invalid.

Cause: An HTTP protocol error occurred.

Cause: The specified encoding is known but not supported by the parser.

Cause: A parser context which had a shared DTD set was used to parse a document which also contained a DTD. You cannot use both a shared DTD and and internal/external one.

Cause: The input document was detected to be ASCII (or EBCDIC) based, but no encoding was specified in the XMLDecl and the default input coding was not ASCII (or EBCDIC) based, so could not be applied.

Cause: An element's namespace prefix declarations was for a NULL URI, e.g. <foo xmlns:bar=""/> This is illegal presently in XML 1.0, but will be legal in XML 1.1

Cause: A Unicode document contained an invalid surrogate. If the first (high) surrogate is in the correct range 0xD800 to 0xDBFF, then the second (low) surrogate must be in the range 0xDC00 to 0xDFFF.

Cause: The name attribute was not found in the attribute-set element.

Cause: The XPATH evaluation returns an error.

Cause: The child node is of invalid type or has invalid name for this particular location in stylesheet, rendering the stylesheet as invalid XSLT.

Cause: Attribute is found but its value is not the expected value.

Cause: An input parameter passed into this function is null when it is not supposed to.

Cause: An expected token is not found.

Cause: A closing '}' is expected.

Cause: Namespace prefix is used but not declared.

Cause: The expected attribute for this node is not found.

Cause: XPATH context could not be initialized.

Cause: The expected element is not found.

Cause: This feature is not supported.

Cause: The content of XML PI node might be invalid.

Cause: The content of XML comment node might be invalid.

Cause: An internal error occurred in the code.

Cause: This extension function is not supported.

Cause: The value for the specified attribute is invalid.

Cause: The named decimal-format is undefined (the name "#default" means the default format).

Cause: The named decimal-format was declared more than once.

Cause: The node specified is not of expected type.

Cause: The element to which an attribute was being added is non empty and hence can not add anymore attributes to it.

Cause: User is trying to process an XML file with out selecting any mechanism for output.

Cause: Either an import,include or document() function tried to open a document and failed.

Cause: apply-imports was used even when there was no current template possibly with in for-each.

Cause: An invalid language name was specified for sorting.

Cause: An internal error has occurred in XPATH.

Cause: An invalid QName was passed to the XPATH parser.

Cause: An invalid axis name was passed to the XPATH parser.

Cause: An unmatched quote was found in the XSL file.

Cause: The namespace URI may not be valid.

Cause: May be out of memory.

Cause: An object of incorrect type was passed to the XPATH/XSL function.

Cause: Right square bracket missing in the XSL file.

Cause: Right parenthesis missing in the XSL file.

Cause: An unexpected token encountered while parsing the expression/ pattern.

Cause: Variable reference may not be valid.

Cause: The function is not supported at this time or the name is invalid.

Cause: The numerical constant in the XPath expression is too big.

Cause: Invalid token in XPath expression.

Cause: Invalid child element in this stylesheet context.

Cause: Invalid attribute value in this stylesheet context.

Cause: Invalid attribute value for this attribute.

Cause: Invalid attribute for this element.

Cause: Missing attribute for this element.

Cause: Invalid variable or parameter or template reference.

Cause: Only one declaration is allowed at this level.

Cause: Invalid number of arguments.

Cause: The XML data is too large.

Cause: SAX callback returns an error.

Cause: Attribute is generated in a wrong context.

Cause: Attribute generated in the wrong context.

Cause: Invalid comment node.

Cause: VM terminates.

Cause: Invalid PI node.

Cause: Invalid object type in XPath evaluation.

Cause: Write operation failed.

Cause: The generated document is not well-formed.

Cause: Failed to load a document.

Cause: Invalid encoding specified.

Cause: The string data is too large.

Cause: Too many XML nodes.

Cause: Invalid or missing argument.