FIX: Errors when you run a query that uses the FOR XML clause in the PATH mode in SQL Server 2008 R2 or in SQL Server 2012

Article translations Article translations
Article ID: 2715312
Expand all | Collapse all

On This Page

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) update release.

Symptoms

Consider the following scenario:
  • You have a client application that runs a query in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012.
  • The query uses the FOR XML clause in the PATH mode.
  • The query runs the SET NO_BROWSETABLE ON command to enable the NO_BROWSETABLE setting.
In this scenario, the query does not run. Additionally, you receive the following error message on the client application, and a minidump file is generated in the SQL error log.

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

Notes
  • A query plan that is used to run the query is not compiled.
  • There are no profiler events for the failed query when you start the SQL Server profile.
  • When this issue occurs, the SQL Server service shuts down intermittently.

Cause

This issue occurs because of an internal failure in the SQL Server algebrizer. This issue occurs when SQL Server tries to add columns that are pulled from one side of a join operator node to the other side of the join operator node. Therefore, an invalid algebrizer tree is created because the columns defined in one side of the join operator node are not visible on the other side of the join operator node.

Resolution

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2723749 Cumulative update package 3 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2720425 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Cumulative update package 7 for SQL Server 2008 R2 SP1

The fix for this issue was first released in Cumulative Update 7 for SQL Server 2008 R2 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703282 Cumulative update package 6 for SQL Server 2008 R2 SP1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was released
Microsoft SQL Server 2008 R2 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 R2 Service Pack 1 hotfix to an installation of SQL Server 2008 R2 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Workaround

To work around this issue, use one of the following methods.

Method 1

Do not use the FOR XML clause in the PATH mode.

Method 2

Run the following command to disable the NO_BROWSETABLE setting:

SET NO_BROWSETABLE OFF

References

For more information about the Browse mode, go to the following MSDN website:
General information about the Browse mode
For more information about how to use the PATH mode with the FOR XML clause, go to the following MSDN website:
How to use the PATH mode with the FOR XML clause

Properties

Article ID: 2715312 - Last Review: November 21, 2012 - Revision: 6.1
Keywords: 
kbtshoot kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2715312

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com