FOR XML Syntax Errors Reference

These provider specific errors are typically thrown when preparing a SQL command for execution. With FOR XML, this becomes more interesting. Some errors, such as those triggered by NULL columns, occur only at execution time.

Possible errors include:

• Statement Explicit not supported (OPL7606)

  This error occurs if the EXPLICIT mode of the FOR XML clause is used.

• XML services not licensed (OPL7643)

  This error occurs when you attempt to execute a SQL FOR XML statement

  Correct as follows:

  If you have purchased an XML services license, make sure you have specified it within the connection string for the Scantron data provider when explicitly using the data provider. If you are scanning, specify the ScanningManager.License property.

• FOR XML query could not be executed. See http://support.microsoft.com/kb/915865

  When the XmlLite DLL is not present, data services reports the following error for any query that uses the FOR XML clause:

  Correct as follows:

  1. Install Windows XP SP3 (strongly recommended)
  2. Install IE 7.0
  3. Install the hot-fix as described in KB 915865

   

• select * from 2 FOR XML RAW('')

  Row tag omission (empty row tag name) cannot be used with attribute-centric FOR XML serialization.

  Correct as follows:

  select * from 2 FOR XML RAW('') , ELEMENTS (element centric)

  select * from 2 FOR XML RAW (defaults to generic row tag ‘row’)

  select * from 2 FOR XML RAW('MyRowTag') (overrides row tag)

   

• select * from 2 FOR XML RAW, ROOT('')

  Empty root tag name can't be specified with FOR XML.

• select * from 2 for xml raw, xmlschema('')

  Empty FOR XML target inline schema URI is not allowed.

• with xmlnamespaces ('' as ns1,'uri1' as ns2,default 'uri') select * from 2 for xml raw

  Empty URI is not allowed in WITH XMLNAMESPACES clause.

• with xmlnamespaces ('uri1' as ns2,'uri1' as ns2,default 'uri') select * from 2 for xml raw

  Attempt to redefine namespace prefix 'ns2'

• with xmlnamespaces ('uri1' as xsi,'uri1' as ns2) select Name from 2 for xml raw, xmldata

  The following FOR XML features are not supported with WITH XMLNAMESPACES list:

  • EXPLICIT mode
  • XMLSCHEMA
  • XMLDATA directives

   

• select Name as "ns1:Name", Gender as "ns1:Gender" from 2 for xml raw ('ns1:GPAS'), elements

  XML name space prefix 'ns1' declaration is missing for FOR XML row name 'ns1:GPAS'. (OPL7642)

  Correct as follows:

  with xmlnamespaces ('uri' as ns1) select Name as "ns1:Name", Gender as "ns1:Gender" from 2 for xml raw ('ns1:GPAS'), elements

• select Name as "ns1:Name", Gender as "ns1:Gender" from 2 for xml raw , elements

  0xC00CEF03 writer: It is not allowed to declare a namespace prefix with empty URI (for example xmlns:p=””)

  Note: SQL Server 2005 does not report an error; it generates XML that cannot be parsed! However the XML parser actually reports a more meaningful error: ‘ns1’ is an undeclared namespace

  Correct as follows:

  with xmlnamespaces ('uri' as ns1) select Name as "ns1:Name", Gender as "ns1:Gender" from 2 for xml raw ('ns1:GPAS'), elements

  select Name from 2 FOR XML RAW(''),XMLDATA

  select Name from 2 FOR XML ROOT(''),XMLDATA

  select Name from 2 FOR XML RAW('MyRow'),XMLDATA

  select Name from 2 FOR XML ROOT('MyRoot'),XMLDATA

  select Name from 2 FOR XML PATH(''),XMLDATA

  FOR XML directive XMLDATA is not allowed with ROOT directive or row tag name specified.

  select Name from 2 FOR XML PATH,XMLDATA

  select Name from 2 FOR XML PATH(‘’),XMLDATA

  select Name from 2 FOR XML PATH(‘MyRow’),XMLDATA

  select Name from 2 FOR XML PATH,XMLSCHEMA

  select Name from 2 FOR XML PATH(‘’),XMLSCHEMA

  select Name from 2 FOR XML PATH(‘MyRow’),XMLSCHEMA

   

• Inline schema is not supported with FOR XML PATH.

  Error text contains the error part and an optional context part with any additional data that qualifies the context.

  Following is a list of strings that provide contextual information within the error text. They may be further qualified with names within the application definition and/or query.

  • creating xml writer
  • setting indent property in writer
  • setting output stream for writer
  • setting conformance level to fragment
  • setting conformance to document
  • setting omit xml decln to false
  • writing start of document
  • writing end element
  • writing content
  • flushing
  • writing comment
  • encoding name

  For example, run this query against z802.sds.StxAppDef and 802.dat

  select * from 1 for xml auto

  This is the error that results:

  Start character is not a letter, underscore or colon, encoding name '100 Item GPAS - MM223022'

  Description:

  In the above query, the data provider first resolves the table ordinal reference ‘1’ to the document name '100 Item GPAS - MM223022’. This is the first document in the 802 application definition. When you specify “auto”, the data for each row is wrapped in an XML node named after the table name, which for us is the document name. Data services always escapes special characters such as embedded spaces within names in the SQL statement so as to produce names that can be safely packaged in XML documents. The receiver transforms the name back to its original un-escaped form. In the above example, the name 100 Item GPAS - MM223022 does not satisfy the rules for a valid XML name even after escaping because it starts with a digit.

The following errors are caused by bad names within the application definition or column/table aliases in the query.

The following errors may occur as the XML is being generated.

The following errors are triggered by bugs within the data provider itself.

See also

SQL Statements Accepted by the Data Provider

SQL Best Practices