XSLT Messages

XSLT-ANAMESPACELEX

Message Text

Invalid lexical form for namespace attribute: variable1

XSLT-ANONAMESPACEBIND

Message Text

No namespace binding for prefix: No namespace bound to prefix 'variable1' at variable2

XSLT-APPTEMPCTXNOTNODE

Message Text

Cannot call xsl:apply-templates with no select attribute when context item is not a node

XSLT-APPTEMPNOTNODE

Message Text

Select expression of xsl:apply-templates has an item that is not a node: variable1

XSLT-ASETNSRES

Message Text

Attribute set name may not be in a reserved namespace

XSLT-ATTRBODY

Message Text

Invalid xsl:attribute element: xsl:attribute element variable1 with select attribute and non-empty content

XSLT-ATTRQNAME

Message Text

Unparented attribute cannot be validated as xs:QName or xs:NOTATION: for node variable1 using schema variable2

XSLT-ATTRREQ

Message Text

Missing required attribute: variable1 required at variable2

XSLT-ATTRSETCYCLE

Message Text

Attribute set cycle detected

XSLT-ATTRSETNAME

Message Text

Attribute set not found: variable1

XSLT-ATTRVALTEMPL

Message Text

Invalid value for attribute: variable1

XSLT-BADANALSTR

Message Text

Invalid xsl:analyze-string element: variable1

XSLT-BADATTRSET

Message Text

Invalid attribute set name: variable1

XSLT-BADATTRTYPE

Message Text

Attribute type cannot be complex type: variable1

XSLT-BADATTRVAL

Message Text

Invalid attribute value: 'variable1' is not a valid attribute value at variable2

XSLT-BADAVP

Message Text

Invalid attribute value template: variable1 (variable2)

XSLT-BADCDATAELEMSTR

Message Text

Invalid cdata-section-element: variable1

XSLT-BADCOLLATION

Message Text

Unrecognized or invalid collation URI in xsl:sort: variable1

XSLT-BADCOLLATION2

Message Text

Unrecognized or invalid collation URI in xsl:for-each-group: variable1

XSLT-BADCURRGROUP

Message Text

current-group() disallowed in patterns

XSLT-BADCURRGROUPKEY

Message Text

current-grouping-key() disallowed in patterns

XSLT-BADDECIMALFORMAT

Message Text

Decimal format does not exist: variable1

Cause

The decimal format specified for a format-number function uses a QName and one of the following is true:

• the decimal format is not defined in the stylesheet
• the QName is not a valid QName
• the namespace prefix of the QName is not associated with an in-scope namespace.

Response

Either the QName is not valid or its prefix is not associated with any in-scope namespace or the decimal format does not exist in the stylesheet.

XSLT-BADELEMTYPE

Message Text

Invalid type attribute for xsl:element: variable1

XSLT-BADFRAGID

Message Text

Invalid fragment identifier in fn:document: variable1

XSLT-BADGROUPSPEC

Message Text

Invalid xsl:for-each-group element: xsl:for-each-group element variable1 has multiple group specifiers

XSLT-BADHREFSTR

Message Text

Invalid href: variable1

XSLT-BADIMPORT

Message Text

xsl:import must be at top level: variable1

XSLT-BADINCLUDE

Message Text

xsl:include must be at top level: variable1

XSLT-BADKEYCOLLATION

Message Text

Unrecognized or invalid collation URI in xsl:key: variable1

XSLT-BADMETHODSTR

Message Text

Invalid method: variable1

XSLT-BADMODE

Message Text

Invalid mode specified in template declaration

XSLT-BADNUMVALUE

Message Text

Value attribute of xsl:number cannot be converted to an integer

XSLT-BADPARAM

Message Text

Required parameter has default (select or content): variable1

XSLT-BADPATTERN

Message Text

Invalid pattern: variable1 (variable2)

XSLT-BADPRIORITY

Message Text

Invalid priority attribute: 'variable1' is not a valid number at variable2

XSLT-BADQNAME

Message Text

Invalid QName: variable1

XSLT-BADSEQTYPE

Message Text

Invalid sequence type: variable1 (variable2)

XSLT-BADUSERELT

Message Text

Bad user element: User element before xsl:import at variable1

XSLT-BADVERSION

Message Text

Invalid version attribute: 'variable1' is not a valid number at variable2

XSLT-BADXPATH

Message Text

Invalid XPath expression: variable1

Cause

Incorrect XPath expression syntax.

Response

Fix the XPath expression syntax.

XSLT-BADZERODIGIT

Message Text

Invalid zero digit specified: variable1

Cause

This error occurs when a zero digit specified in a Decimal Format is either not a digit or if it is a digit its value is not zero.

Response

Illegal zero digit specified. The zero digit specified in a Decimal format must be a digit whose numeric value is zero.

XSLT-CHARMAPCYCLE

Message Text

Character map cycle detected

XSLT-CHARMAPNAME

Message Text

Character map not found: variable1

XSLT-CIRCKEY

Message Text

Circularly defined key: variable1

XSLT-CIRCVAR

Message Text

Circularly defined variable or parameter: variable1

XSLT-CMAPNSRES

Message Text

Character map may not be in a reserved namespace

XSLT-COMMENTBODY

Message Text

Invalid xsl:comment element: xsl:comment element variable1 with select attribute and non-empty content

XSLT-COMPARE

Message Text

Items not comparable: variable1 variable2 variable3

XSLT-DECFORMATUNIQ

Message Text

Non-unique picture string characters in xsl:decimal-format

Cause

The values of variables decimal-separator-sign, grouping-sign, percent-sign, per-mille-sign, digit-zero-sign, digit-sign, and pattern-separator-sign must be unique for a given decimal format. User has specified a decimal format in which two or more of these variables have the same value.

Response

Use distinct values for variables decimal-separator-sign, grouping-sign, percent-sign, per-mille-sign, digit-zero-sign, digit-sign, and pattern-separator-sign in the decimal format.

XSLT-DECFORMCONFLICT

Message Text

xsl:decimal-format conflict: for parameter variable1 in variable2 and variable3

Cause

Two decimal formats with same import precedence have conflicting values for the same attribute(s).

Response

Conflicting decimal formats: either make the import precedence of one higher than the other or make sure to have same values for all corresponding attributes.

XSLT-DEFAULTAS

Message Text

Invalid default value coercion for variable or parameter: variable1 as variable2

XSLT-DEFAULTCOLL

Message Text

No collations recognized in default-collation attribute: variable1

XSLT-DEFAULTESAS

Message Text

Invalid empty-sequence() default value coercion for variable or parameter: variable1 as variable2

XSLT-DEFFUNPARM

Message Text

xsl:function parameters may not have default value: variable1

XSLT-DEFNS

Message Text

Cannot construct default namespace on element with no namespace: prefix variable1: namespace URI: variable2

XSLT-DOCNOTFOUND

Message Text

Text document not found

XSLT-DUPCHARMAP

Message Text

Conflicting character map name

XSLT-DUPEMPTYURIS

Message Text

Two final trees cannot have the empty string as their URI

XSLT-DUPFUNCTION

Message Text

Conflicting function name

XSLT-DUPNAMEDTEMPLATE

Message Text

Conflicting named template: variable1 and variable2

XSLT-DUPNSALIAS

Message Text

Conflicting namespace alias

XSLT-DUPPARAM

Message Text

Conflicting parameter name

XSLT-DUPRESULTURIS

Message Text

Two final trees cannot have the same URI: variable1

XSLT-DUPVAR

Message Text

Conflicting variable name

XSLT-EABADQNAME

Message Text

fn:element-available(): argument isn't a valid QName

XSLT-ELTREQ

Message Text

Missing required element child: variable1 required at variable2

XSLT-EMPTYNSURI

Message Text

Empty namespace URI for prefix: variable1

XSLT-ENTITYURICTX

Message Text

unparsed-entity-uri called with no context node

XSLT-ENTITYURIDOC

Message Text

unparsed-entity-uri called with non-document root node

XSLT-FNBADARITY

Message Text

fn:function-available() invoked with bad arity

Cause

A user has invoked function-available with a negative arity value.

Response

The <code xmlns="http://www.w3.org/1999/xhtml">function-available</code>
    <code xmlns="http://www.w3.org/1999/xhtml">arity</code> argument
    must be a non-negative number.

XSLT-FNBADDOCTYPE

Message Text

Bad document argument to function unparsed-text

XSLT-FNBADENCODING

Message Text

Error decoding document using specified encoding to function unparsed-text or unparsed-text-available

XSLT-FNBADQNAME

Message Text

fn:function-available(): first argument isn't a valid QName

XSLT-FNBADURI

Message Text

Bad URI argument to function unparsed-text

XSLT-FNILLEGALENCODING

Message Text

Encoding not supported

XSLT-FNNOENCODING

Message Text

Function unparsed-text was unable to determine correct encoding or decode with UTF-8

XSLT-FORMATNAME

Message Text

Named output definition not found: variable1

XSLT-FORMATNUMPICT1

Message Text

Invalid picture string in format-number: variable1

Cause

REVIEW: Unused message. Removed from code bug: 16214.

Response

REVIEW: Unused message. Removed from code bug: 16214.

XSLT-FORMATNUMPICT10

Message Text

The fractional part of a sub-picture for format-number cannot contain a digit-sign followed by a zero-digit-sign: variable1

Cause

The fractional part of the specified picture string contains one or more of optional digits followed by a mandatory digit.

Response

Remove digit signs that follow the zero-digit signs in the fractional part of the sub-picture. Alternatively change all the zero-digit signs preceding digit-signs to digit-signs.

XSLT-FORMATNUMPICT11

Message Text

A sub-picture for format-number cannot contain a passive character that is preceded by an active character and followed by another active character: variable1

Cause

User has specified a illegal sub-picture string that contains a passive character between two active characters.

Response

Change the picture string such that a passive character is not between active characters.

XSLT-FORMATNUMPICT12

Message Text

A picture string in format-number cannot end in a decimal separator.: variable1

Cause

Illegal picture string causes this error. User has supplied a picture string to format-number that contains a decimal separator at the end.

Response

Change the picture string either by removing the trailing decimal separator or by adding a digit-sign after it.

XSLT-FORMATNUMPICT2

Message Text

Two pattern separators are not allowed in picture string for format-number: variable1

Cause

A picture string in format-number can have two separate patterns for positive and negative numbers. These two are separated in the picture string by a pattern separator. This error occurs when user specifies a picture string that has more than one pattern separators.

Response

Remove the extra pattern separator from picture string.

XSLT-FORMATNUMPICT3

Message Text

A sub-picture for format-number cannot contain two percent signs: variable1

Cause

A picture string used by format-number contains more than one decimal separators.

Response

Remove the extra decimal separators from the picture string.

XSLT-FORMATNUMPICT4

Message Text

A sub-picture for format-number cannot contain both percent and per-mille sign. : variable1

Cause

Illegal picture string causes this error. User has included both percent and per-mille signs in the picture string to format-number.

Response

Remove either percent or the per-mille sign from picture string of format-number.

XSLT-FORMATNUMPICT5

Message Text

A sub-picture for format-number cannot contain two per-mille signs: variable1

Cause

An illegal picture string causes this error. A user has supplied a picture string to format-number that has two per-mille signs.

Response

Remove the extra per-mille sign.

XSLT-FORMATNUMPICT6

Message Text

A sub-picture for format-number cannot contain two decimal-separator signs: variable1

Cause

You supplied an illegal picture string that contains two decimal separator signs.

Response

Remove the extra decimal-separator.

XSLT-FORMATNUMPICT7

Message Text

A sub-picture for format-number cannot contain a decimal-separator sign adjacent to a grouping-separator-sign: variable1

Cause

An illegal picture string causes this error. It contains a decimal-separator sign adjacent to a grouping-separator sign.

Response

Remove one of the adjacent decimal-separator and grouping-separator signs in the picture sting to format-number.

XSLT-FORMATNUMPICT8

Message Text

A sub-picture for format-number must contain one zero-digit or digit sign: variable1

Cause

Illegal picture string to format-number. A user has supplied a picture string that doesn't contain any zero-digit or digit sign.

Response

Add at least one digit or zero-digit sign to the picture string of format-number.

XSLT-FORMATNUMPICT9

Message Text

The integer part of a sub-picture for format-number cannot contain a zero-digit-sign followed by a digit-sign: variable1

Cause

Illegal picture string is the cause of this error. A user has specified a picture string in which the integer part contains a (optional) zero-digit sign followed by a (mandatory) digit-sign.

Response

Remove the zero-digit sign(s) following a digit-sign in the integer part of the picture-sting of format-number.

XSLT-FORMATSTR

Message Text

Invalid lexical form for format attribute: variable1

Cause

The format attribute of result-document instruction cannot be converted to a valid QName. As a result, the output-definition for generating results cannot be retrieved.

Response

Use an output definition's valid name as a value of the "format" attribute in the xsl:result-document instruction.

XSLT-FUNCTIONAS

Message Text

Invalid coercion for return value of function: variable1 as variable2

XSLT-FUNCTUNPAR

Message Text

Tunnel parameters not allowed in functions: parameter variable1 in function variable2

XSLT-FUNNSRES

Message Text

Functions may not be declared in a reserved namespace

XSLT-GRCOLLATION

Message Text

Invalid xsl:for-each-group element: xsl:for-each-group element variable1 with collation and no group-by or group-adjacent specifier

XSLT-GRNOTPATTERN

Message Text

Invalid xsl:for-each-group element: group specifier is not a pattern

XSLT-GROUPADJKEY

Message Text

Grouping key not a singleton with group-adjacent: variable1

XSLT-GROUPITEMTYPE

Message Text

Item in select expression of xsl:for-each-group is not a node: variable1

XSLT-IMPORTCYCLE

Message Text

Import cycle found in stylesheet: variable1

XSLT-IMPORTNOTFIRST

Message Text

Bad xsl:import: Element before xsl:import at variable1

XSLT-IMPORTNOTFOUND

Message Text

Imported stylesheet not found: variable1

XSLT-IMPORTPATH

Message Text

Invalid stylesheet import path: variable1

XSLT-INCLUDECYCLE

Message Text

Include cycle found in stylesheet: variable1

XSLT-INITMODE

Message Text

Invalid initial mode: variable1

XSLT-INITPARAM

Message Text

Missing required parameter for stylesheet: variable1

XSLT-INITTEMPLATE

Message Text

Starting template name not found: variable1

XSLT-INVCHOOSE

Message Text

xsl:choose requires xsl:when+,xsl:otherwise: variable1

XSLT-INVMETHOD

Message Text

xsl:output invalid method: 'variable1' is not valid in variable2

XSLT-INVSORTSTABLE

Message Text

Invalid xsl:sort element: stable attribute on xsl:sort variable1 invalid

XSLT-INVXSLATTR

Message Text

Unknown attribute in XSLT namespace: Unknown attribute variable1 in XSLT namespace on literal result element

XSLT-KEYCOLLCONF

Message Text

Conflicting collation in key declaration

XSLT-KEYLEXVAL

Message Text

Key name is not a valid QName

XSLT-KEYNOTDOC

Message Text

Context item does not have a document node root

XSLT-KEYNSRES

Message Text

Key name may not be in a reserved namespace

XSLT-LEVELATTR

Message Text

Invalid xsl:number element: xsl:number element variable1 with value and level attributes

XSLT-MATCHORNAMEREQ

Message Text

Template requires match or name attribute: variable1

XSLT-MATCHZERO

Message Text

Pattern matches zero-length string

XSLT-MISSINGCONTEXT

Message Text

Missing context item

XSLT-MISSINGPARAM

Message Text

Missing template parameter in xsl:call-template: variable1

XSLT-MISSINGPARAM2

Message Text

Missing template parameter: variable1

XSLT-MODEANDTEMPLATE

Message Text

Cannot start a transform with both an initial mode and template

XSLT-MODENSRES

Message Text

Mode may not be in a reserved namespace

XSLT-MSGTERMINATE

Message Text

xsl:message instruction called with terminate

XSLT-NAMEDTEMPATTRS

Message Text

Named template has mode or priority attribute: variable1

XSLT-NAMESPACELEX

Message Text

Invalid lexical form for namespace attribute: variable1

XSLT-NEGNUMVALUE

Message Text

Value attribute of xsl:number evaluates to a negative integer: variable1

XSLT-NOCURRTEMPLATE

Message Text

No current template for xsl:apply-imports

XSLT-NOCURRTEMPLATE2

Message Text

No current template for xsl:next-match

XSLT-NOEXCLNSBIND

Message Text

No namespace binding for exclude result prefix: No namespace bound to prefix 'variable1' at variable2

XSLT-NOEXCLNSBIND2

Message Text

No default namespace for exclude result prefix: No namespace bound to prefix 'variable1' at variable2

XSLT-NOEXTNSBIND

Message Text

No namespace binding for extension element prefix: No namespace bound to prefix 'variable1' at variable2

XSLT-NOFALLBACK

Message Text

No xsl:fallback: Required fallback but none found at variable1

XSLT-NOFALLBACK2

Message Text

No xsl:fallback: Required fallback but none found

XSLT-NOGROUPSPEC

Message Text

Invalid xsl:for-each-group element: xsl:for-each-group element variable1 with no group specifier

XSLT-NONAMESPACEBIND

Message Text

No namespace binding for prefix

XSLT-NOSUCHKEY

Message Text

Key declaration not found: variable1

XSLT-NOSUCHPARAM

Message Text

Template parameter not found in xsl:call-template: variable1

XSLT-NOSUCHTEMPLATE

Message Text

Template name not found: variable1

XSLT-NOVERSION

Message Text

Simplified stylesheet must contain valid xsl:version attribute: variable1

XSLT-NSALIASPREFIX

Message Text

Unbound namespace alias stylesheet-prefix: variable1 in variable2

XSLT-NSALIASPREFIX2

Message Text

Unbound namespace alias result-prefix: variable1 in variable2

XSLT-NSBODY

Message Text

Invalid xsl:namespace element: xsl:namespace element variable1 with select attribute and non-empty content

XSLT-NSLEX

Message Text

Invalid lexical form for namespace URI: variable1

XSLT-NSPREFIX

Message Text

Invalid namespace prefix: variable1

XSLT-NUMCTXNOTNODE

Message Text

Context item is not a node for xsl:number

XSLT-NUMSELECTVAL

Message Text

Select attribute of xsl:number does not evaluate to a node

XSLT-NUMVALUEATTR

Message Text

Invalid xsl:number element: xsl:number element variable1 with value attribute and select, count or from attribute

XSLT-OUTPUTCONFLICT

Message Text

xsl:output conflict: for parameter variable1 in variable2 and variable3

XSLT-OUTPUTDECLNSRES

Message Text

Output definition may not be in a reserved namespace

XSLT-PARAMAS

Message Text

Invalid parameter coercion: variable1 as variable2

XSLT-PARAMBODY

Message Text

Variable or parameter cannot contain both a select attribute and non-empty content

XSLT-PARAMNSRES

Message Text

Parameter name may not be in a reserved namespace

XSLT-PERFORMSORTBODY

Message Text

Invalid xsl:perform-sort element: xsl:perform-sort element with select attribute and non-empty content

XSLT-PIBODY

Message Text

Invalid xsl:processing-instruction element: xsl:processing-instruction element variable1 with select attribute and non-empty content

XSLT-PUBLICIDCTX

Message Text

unparsed-entity-public-id called with no context node

XSLT-PUBLICIDDOC

Message Text

unparsed-entity-public-id called with non-document root node

XSLT-QNAMELEXFORM

Message Text

Invalid lexical form for QName

XSLT-QNAMELEXFORM1

Message Text

Invalid lexical form for name attribute

XSLT-QNAMELEXFORM2

Message Text

Invalid lexical form for name attribute: variable1

XSLT-REGEX

Message Text

Invalid regular expression

Cause

A user has specified a regular expression with incorrect syntax.

Response

Fix the regular expression's incorrect syntax.

XSLT-REGEXFLAGS

Message Text

Invalid regular expression flags

Cause

User has specified illegal flags for analyze-string instruction.

Response

Provide flags that the XSLT specification allows or remove them from the analyze-string instruction.

XSLT-REGEXINTERNAL

Message Text

Internal error in fn/xsl analyze-string

Cause

xsl:analyze-string encountered an illegal element when it was expecting xsl:matching-substring or xsl:non-matching-substring instructions.

Response

Correct the syntax for the xsl:analyze-string instruction.

XSLT-RESDOCTEMP

Message Text

xsl:result-document not allowed in temporary output state

XSLT-SORTBODY

Message Text

Invalid xsl:sort element: xsl:sort element variable1 with select attribute and non-empty content

XSLT-SORTKEYTYPE

Message Text

Sort key value is a sequence with more than one item: variable1

XSLT-SPACECONFLICT

Message Text

Conflicting strip/preserve-space declarations found for node: variable1

XSLT-SSNULLNSCHILD

Message Text

Stylesheet cannot contain child elements with no namespace: variable1

XSLT-SSPARAMAS

Message Text

Invalid value coercion for stylesheet parameter: variable1 as variable2

XSLT-SSTEXTNODE

Message Text

Stylesheet may not contain text nodes: variable1

XSLT-TABADQNAME

Message Text

fn:type-available(): first argument isn't a valid QName

XSLT-TEMPINITPARAM

Message Text

Starting template has required parameter: variable1

XSLT-TEMPLATEAS

Message Text

Invalid template coercion: variable1 as variable2

XSLT-TEMPLATENSRES

Message Text

Template names may not be in a reserved namespace

XSLT-TEMPLCONFLICT

Message Text

Conflicting templates found for node: variable1

XSLT-TYPEANDVALIDATE

Message Text

Conflicting validation attributes: both type and validate attributes specified at variable1

XSLT-UNBPRFX

Message Text

Prefix variable1 has no namespace binding

XSLT-UNDFUN

Message Text

Undefined function variable1

XSLT-UNDVAR

Message Text

Undefined variable: variable1

XSLT-UNEXPECTED

Message Text

Unexpected content in stylesheet: variable1

XSLT-UNEXPECTEDATTR

Message Text

Unexpected attribute: unexpected attribute variable1 in XSLT or null namespace

XSLT-UNEXPECTEDTEXT

Message Text

Unexpected content in stylesheet: variable1

XSLT-UNPRFXFUN

Message Text

Stylesheet function names must have a prefix: variable1

XSLT-UNSUPPORTED

Message Text

Unsupported or unexpected instruction or declaration: variable1

XSLT-USEANDCONTENT

Message Text

Key has both use attribute and non-empty content: variable1

XSLT-USEORCONTENTREQ

Message Text

Key requires use attribute or non-empty content: variable1

XSLT-VALIDATEBADDOCNODE

Message Text

A validated document node must contain exactly one root element

Cause

An attempt was made to validate a document node that had more than one root element. Such a document is invalid.

Response

Fix the document so that it only has one root element.

XSLT-VALIDATEBADTYPE1

Message Text

Invalid node type: variable1 lexical value variable2 invalid for expected type variable3 at variable4 using schema variable5

Cause

Validation of an element failed in strict mode because the lexical value of the element was not permitted per the type definition.

Response

Fix the element to have valid content.

XSLT-VALIDATEBADTYPE3

Message Text

Invalid node type: variable1 lexical value variable2 invalid for expected type variable3 at variable4 using schema variable5

Cause

Validation of an element failed in lax mode because the lexical value of the element was not permitted per the type definition.

Response

Fix the element to have valid content.

XSLT-VALIDATEBADTYPE4

Message Text

Invalid node type: variable1 lexical value variable2 invalid for expected type variable3 at variable4 using schema variable5

Cause

Validation of an element failed when validating against a named type. This was because the element's lexical value was not permitted per the type definition.

Response

Fix the element to have valid content.

XSLT-VALIDATEMISSINGATTR

Message Text

Missing required attribute: Found variable1 but required variable2 at variable3 using schema variable4

Cause

Validation detected an element that was missing a required attribute.

Response

The instance is invalid. Add the required attribute to the element.

XSLT-VALIDATENODECL

Message Text

Missing element declaration: Expected declaration for node variable1 in non-lax mode using schema variable2

Cause

Validation failed because an element or attribute was found without a corresponding declaration. In some cases this can occur because an element somewhere within the subtree of the element was missing a declaration. This can be either because the schema is missing the declaration, the proper schema could not be located, or the element or attribute is incorrect (misspelled, for example).

Response

Fix the schema, the content, or the schema location as appropriate.

XSLT-VALIDATEUNEXPECTED1

Message Text

Invalid node: Found variable1 but expected variable2 at variable3 using schema variable4

Cause

Unexpected content (element, attribute, or text) was seen when validating an element in strict mode.

Response

Fix the content to be valid. Check the name of the element or attribute reported as unexpected, or remove the unexpected text.

XSLT-VALIDATEUNEXPECTED3

Message Text

Invalid node: Found variable1 but expected variable2 at variable3 using schema variable4

Cause

Unexpected content (element, attribute, or text) was seen in validating an element in lax mode.

Response

Fix the content to be valid. Check the name of the element or attribute reported as unexpected, or remove the unexpected text.

XSLT-VALIDATEUNEXPECTED4

Message Text

Invalid node: Found variable1 but expected variable2 at variable3 using schema variable4

Cause

Unexpected content (element, attribute, or text) was seen in validating an element against a named type.

Response

Fix the content to be valid. Check the name of the element or attribute reported as unexpected, or remove the unexpected text.

XSLT-VALUEOFBODY

Message Text

Invalid xsl:value-of element: xsl:value-of element variable1 with select attribute and non-empty content

XSLT-VARAS

Message Text

Invalid variable coercion: variable1 as variable2

XSLT-VARSRES

Message Text

Variable name may not be in a reserved namespace

XSLT-XMLNODE

Message Text

Server unable to build stylesheet from non-XML document

XSLT-XMLNS

Message Text

Cannot redefine xml namespace: prefix variable1: namespace URI: variable2

XSLT-XMLNSATTR

Message Text

Cannot redefine xml namespace

XSLT-XMLPI

Message Text

Processing instructions may not have the target 'XML'