Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| WX006 | Error | 2564 | -898L | "Unknown FOR XML EXPLICIT directive: '%1'" | Legal FOR XML EXPLICIT directives are: id, idref, idrefs, hide, element, xml, cdata. Click here for a list of possible parameters and odbc states. |
| WX007 | Error | 2565 | -899L | "Illegal column name: '%1'" | FOR XML EXPLICIT column names can consist of up to four fields separated by exclamation marks. The first two columns must be named Tag and Parent. Click here for a list of possible parameters and odbc states. |
| WX008 | Error | 2566 | -900L | "Parent not open: '%1'" | FOR XML EXPLICIT requires the parent tag for a row to be opened when that row is read. Check the order of the rows returned by the query with the FOR XML EXPLICIT clause removed. Click here for a list of possible parameters and odbc states. |
| WX009 | Error | 2567 | -901L | "Undeclared tag ID: '%1'" | Every value appearing in the Tag column of the table must be declared in the TagNumber field of at least one column name. Click here for a list of possible parameters and odbc states. |
| WX010 | Error | 2568 | -902L | "Too few columns" | FOR XML EXPLICIT requires at least three columns: the tag column, the parent column, and one or more data columns. Click here for a list of possible parameters and odbc states. |
| WX011 | Error | 2569 | -903L | "CDATA has a name" | A CDATA directive in a FOR XML EXPLICIT query must not be given a name. Click here for a list of possible parameters and odbc states. |
| WX012 | Error | 2571 | -905L | "Invalid XQuery constructor" | The XQuery constructor passed as the first argument to XMLGEN was not valid. Click here for a list of possible parameters and odbc states. |
| WX013 | Error | 2572 | -906L | "XMLGEN evaluation failure" | One of the variables referenced in the XQuery constructor was not found in the list of arguments. Click here for a list of possible parameters and odbc states. |
| WX014 | Error | 2573 | -907L | "No name for argument" | Unnamed arguments cannot be used as XML element or attribute names. Name unnamed items in the argument list using AS. Click here for a list of possible parameters and odbc states. |
| WX015 | Error | 2576 | -911L | "Control character in XML output" | A non-space character less than hex 20 was encountered while generating XML content. Consider base64 encoding strings that contain control characters before using them as XML content. This can be accomplished in a FOR XML query or SQLX function by casting the string to a type such as LONG BINARY. Click here for a list of possible parameters and odbc states. |
| WX016 | Error | 2577 | -912L | "Insufficient memory for OPENXML query" | The memory used by an OPENXML query may be proportional to the maximum distance between elements or attributes returned by a single row. For example, a query where some row uses the value from both the first and last element in the document may use memory proportional to the size of the document. One solution is to increase the cache size. Another is to break a query that refers to distant elements into several queries that refer to nearby elements and join the results. Click here for a list of possible parameters and odbc states. |