You are currently offline, waiting for your internet to reconnect

FIX: "Invalid column name '<ColumnName>'" error when you run some MDX queries that you could previously run successfully in SQL Server 2008 R2 or in SQL Server 2012

Symptoms
Assume that you apply one of the following cumulative update packages to Microsoft SQL Server 2008 R2:
  • Cumulative update package 3 for SQL Server 2008 R2 Service Pack 2 (SP2) or a later version
  • Cumulative update package 8 for SQL Server 2008 R2 Service Pack 1 (SP1) or a later version
When you try to run some Multidimensional Expressions (MDX) queries that you could previously run successfully, you receive the following error message:
OLE DB error: OLE DB or ODBC error: Invalid column name '<ColumnName>'.; 42S22; Invalid column name '<ColumnName>'.; 42S22.
Cause
This issue occurs because the fix for the issue that is described in Microsoft Knowledge Base article 2741143 contains a regression.
Resolution
The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 11 for SQL Server 2012

Cumulative Update 9 for SQL Server 2008 R2 SP2

About cumulative updates for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 2889987 - Last Review: 12/16/2013 18:18:00 - Revision: 2.0

Microsoft SQL Server 2008 R2 Service Pack 2, Microsoft SQL Server 2012 Developer, Microsoft SQL Server 2012 Enterprise, Microsoft SQL Server 2012 Standard

  • kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2889987
Feedback
'" error message when you run some MDX queries that you could previously run successfully in SQL Server 2008 R2 or in SQL Server 2012. This issue occurs after you apply certain CUs..." />
'" error message when you run some MDX queries that you could previously run successfully in SQL Server 2008 R2 or in SQL Server 2012. This issue occurs after you apply certain CUs..." />
/html>